Dan C

When the Snapping Candidates is set to "All layers" (but not neccesserily), the Snapping happens across Artboards, which might be causing significant performance drops (especially when working with Text, for some reason).

 
As an App UI designer, I currently have around 50 artboards (both vertically and horizontally aligned) and the Snapping would sometimes choose to snap to some object very far away crossing multiple Artboards. 
I think Snapping options should include "Ignore other Artboards" toggle, because I would keep it ON most of the time. 
This could solve a lot of problems/confusions for the users.
 
Thanks for consideration 😊

Dan, Walt, Seneca et al,
Thanks for your patience.
I FINALLY GOT IT TO WORK!!!   OMG!
The problem appears to have been my not understanding that it is necessary to hold down "shift" while clicking the "place" tool. Thank you for clarifying that. I've tried it multiple times now and both pages flow in as desired! Such a tiny thing turned out to be the linchpin of the entire operation.
Thanks again to everyone.
Until next time...
lettergothic
 

Appreciate you've taken the time to look into it and to elaborate.

Hi @MKap and welcome to the forums,
This is a known bug in v2.2.0 (AF-295) which has been reported and is awaiting a fix. It is referenced in the Known Issues section of the Frequently Asked Questions about V2 software here...

Maybe due to possible light UI usage here?
Photo v2 under Sonoma also has certain issues, do a forum search after that topic.

Hi @dtpunger,
This bug has been fixed in the 2.2.1.2052 Beta. The current Beta is 2.2.1.2075.
If you're not part of the Beta Program and would like to sign up to join the Beta Program you can do so by following the link here... You can install the Beta alongside the retail version and run the two side by side.

Light to mid colour hair such as Blonde to lightish browns can be coloured with a pixel layer and the colour of choice painted onto it and the blend mode changed to overlay.
Darker hair colours probably need to be lightened first, so, black hair can be changed to grey using the brightness and contrast adjustment layer, then a recolour adjustment layer used atop of it.
 

Hi @Mariusz go,
Thanks for your report!
I can confirm our team are aware of this issue and we're working to resolve it as soon as possible, I'll be sure to 'bump' the development log with this thread to bring it to our teams attention once again.
I hope this helps

Unfortunately there's no setting to change the default behaviour of Groups currently - as Walt mentions this is expected to use the 'Passthrough' blend mode, though can then be manually changed by the user as required.
There is an internal improvement request to allow the user to change the default blend mode used when Grouping, so I'll be sure to add your 'vote' to this now.
I hope this helps

There is no issue with the contents of thomasos post above.
They are simply another user of the Affinity forums and have as much as right as anyone, including yourself, to post here.
If you don't wish to see replies from specific users, please use the Ignore function. As I understand this should mean the replies from this user are hidden to you. It does not 'block' their ability to post within your thread (nor should it).
Please do not '@' tag myself or other forum moderators like this publicly if you have an issue with a post or a user, use the built-in report function of the Forums and this will be dealt with as required.
 
I am locking this thread from further replies. I hope you all enjoy your weekend.

There is no issue with the contents of thomasos post above.
They are simply another user of the Affinity forums and have as much as right as anyone, including yourself, to post here.
If you don't wish to see replies from specific users, please use the Ignore function. As I understand this should mean the replies from this user are hidden to you. It does not 'block' their ability to post within your thread (nor should it).
Please do not '@' tag myself or other forum moderators like this publicly if you have an issue with a post or a user, use the built-in report function of the Forums and this will be dealt with as required.
 
I am locking this thread from further replies. I hope you all enjoy your weekend.

There is no issue with the contents of thomasos post above.
They are simply another user of the Affinity forums and have as much as right as anyone, including yourself, to post here.
If you don't wish to see replies from specific users, please use the Ignore function. As I understand this should mean the replies from this user are hidden to you. It does not 'block' their ability to post within your thread (nor should it).
Please do not '@' tag myself or other forum moderators like this publicly if you have an issue with a post or a user, use the built-in report function of the Forums and this will be dealt with as required.
 
I am locking this thread from further replies. I hope you all enjoy your weekend.

There is no issue with the contents of thomasos post above.
They are simply another user of the Affinity forums and have as much as right as anyone, including yourself, to post here.
If you don't wish to see replies from specific users, please use the Ignore function. As I understand this should mean the replies from this user are hidden to you. It does not 'block' their ability to post within your thread (nor should it).
Please do not '@' tag myself or other forum moderators like this publicly if you have an issue with a post or a user, use the built-in report function of the Forums and this will be dealt with as required.
 
I am locking this thread from further replies. I hope you all enjoy your weekend.

The V2 apps all came from the Affinity Store. AD & AP V1 came from the MAS. APub V1 came from the Affinity Store. I just checked again & all 3 V1 apps generate a PDFLib.log file, but the V2 apps still do not for me, so I'm still mystified by why it isn't working.
The only thing I have not yet tried is quitting & restarting any of the V2 apps on my Mac. I would prefer not to try that because of the still very annoying bug that clears the recently opened items on the Dock popup, but I will give that a try for one of the V2 apps if you think that would make any difference.
EDIT: AHA!!! I quit AD V2 & restarted it after using the Terminal command & now the PDFLib.log is created for that app but not for the other two V2 apps.
So it seems that enabling logging won't 'take' if the app is already running, but quitting & relaunching them will.
Mystery solved ... I think. 😃
EDIT 2: It's the same for the launchctl unsetenv PDFLIBLOGGING command: If I use it when the app is still open, it has no effect & the log file is still created or appended to. Very annoying that I have to do that because of the Dock clearing bug, but at least I now know the cause & cure for the logging issue.

If this thread goes down that road, I’m out after this final post.

if you want to ignore someone, go ahead - silent. No need to publicly attack anybody.
 
There is a „report“ button on every post if you think it is against the guidelines. 

Thanks all, my apologies as I've found the PDF liblogging file was outdated - due to the Affinity apps updating PDFlib (the Library used to write PDF files) in v2.2, the logging file also needed updating, hence the reason a log was not being written.
I've since updated this file in the FAQ to support the new PDFLib version, though I don't require this to be used in this case as I now have a copy of the file in question
____
In regards to the issue being reported here, it appears to be errors caused from certain BMP files in the document, though this isn't an issue I've come across previously and therefore have escalated this issue with our team internally. I'll be sure to respond here ASAP with any further information I'm provided.
Thanks for your continued patience and understanding!

Thak you so much!

Thank you for trying that for me and the additional screenshots provided above - our team are yet to replicate this behaviour here or understand the exact cause of this on your machine, as there is no clear indicator for this to occur.
Firstly, we'd like to see if the same issue happens in the 2.1.1 MSIX versions of the Affinity apps to see if this is related to the latest update or simply is coincidental timing. Currently I believe you have the 2.2 EXE versions installed, which can be left as-is, as you should be able to install the MSIX versions simultaneously, provided they are not the same version number.
Please visit the below link and select the 2.1.1 download option for MSIX then install as normal - 
https://store.serif.com/update/windows/photo/2/
Once installed, please launch this app - you should know you've launched the correct version as you'll be prompted to update to 2.2 upon launch, please simply close this dialog without updating.
Does the 2.1.1 MSIX version of the app crash in the same way as 2.2 please?
If so, our team recommend creating a new user account on your PC and installing the latest version (2.2, either MSIX or EXE) on this new user account, then repeat your testing. Does the app crash on this new user from the same workflow as before, or does this work as expected?

Normally I run my Screen at 100%. I did try with 125%. It helped, the crash occured a little later. But it did crash after several attempts. Not immediately though.
At 150% I could'nt reproduce the error at all. Everything was fine.
 
 

Hi @MarcPradel and welcome to the forums,
If this is happening after using the scrollbars to navigate through your document then this is a known bug in v2.2.

Much appreciated, Dan and v_kyr. Perhaps it would be a good idea for the future to always convert .PSD files before placing them.
Thank you for your help with this.

Hi, this is a known issue with this new 2.2 feature so it's on Serif's list already.
 

Ah okay, that makes more sense now, for some odd reason I was expecting to still get an error message regardless, no idea why...

Thanks for your file provided @jackamus!
The issue in your file is due to the Compound object - you have a very strange layer setup for this object, which includes multiple compounds within the same compound shape, some of which are simply empty compounds within a compound group.

It appears as though this is causing a recurring mathematics error for the Compound shape, setting the X& Y location, as well as the Height & Width of the object to;
15220468541834272403530696713984091417512736516259435112031139106814910766953401025357054709781589502319562428582293058800246641899534378429240315730800057085531258937648020520853768518830879150395566171888181809594625546509775424923231356337594894783572486312364486501173963294843541702712847289214866292736 mm 
As you can imagine, when the app tries to copy an object that is impossibly large, it simply crashes.
Although Compounds are compatible to be nested within other Compounds, there is clearly an issue caused from to your layer setup in this file. I've been able to replicate this by creating a Subtract Compound, then adding an Add Compound within this and deleting the object within the Add Compound. The app then cannot calculate Subtracting an infinite Addition and the above issue occurs. I'll be logging this with our devs now.
As this is a relatively simple shape, you can create this using a single Compound and it will work as expected, retaining the correct H&W values and the ability to be copied, etc - 

Please find a copy of your file with these fixes applied below: 
Spring winder 1_F.afdesign
I hope this helps!

Thanks all, my apologies as I've found the PDF liblogging file was outdated - due to the Affinity apps updating PDFlib (the Library used to write PDF files) in v2.2, the logging file also needed updating, hence the reason a log was not being written.
I've since updated this file in the FAQ to support the new PDFLib version, though I don't require this to be used in this case as I now have a copy of the file in question
____
In regards to the issue being reported here, it appears to be errors caused from certain BMP files in the document, though this isn't an issue I've come across previously and therefore have escalated this issue with our team internally. I'll be sure to respond here ASAP with any further information I'm provided.
Thanks for your continued patience and understanding!