SPaceBar

Hi @ricecrispies Are these crashes all on different documents or the same one? I am trying to find to steps to attempt to reproduce your issue. Could you also tell me if you have any created any Print Profiles?

Hi @footeg Would you be able to upload your image here please so I can take a closer look at it?

HI @Paul Cuffo If you want to upload your crash report privately you can add it here.

I think the colour variance was more to do with the issue I mentioned above.

The issue is with the folder associated with the man. You can group the adjustments together as long as there isn't a pixel layer inside the group. You had 3 adjustment layers in a group with a Pixel layer called skin. This then means that all of those adjustments are applied to whatever is on the pixel layer hence the marks on his face. I moved the layer called skin (Pixel) out of the group and it now looks ok.

Hi @digitalvt I have reproduced the issue on iMac with Big Sur on both 1.10.4 and 1.10.3 Designer. I have managed to open it on 1.10.4 Designer on Windows and can see that there is a mask containing 14000 clipped objects that were slowing it down considerably. I will get this issue logged.

Hi @digitalvt Welcome to the Affinity forums! I'm sorry to hear you are experiencing issues with your file. Would you be able to upload it here so I can take a closer look?

That's ok, I was going to send you a link to a Dropbox folder but you beat me to it. I can access the files from there but it is better to discuss it here in case other customers have similar issues. I have done some basic file comparisons which I won't share here. The image with 2 people in is very close here on a side-by-side comparison on my iMac. I can see the issue you mention about the green colour being visible on Photoshop but not on Affinity Photo. I've looked through the layers to see which Photoshop edit created the green as it's not part of the original photo. It's a layer mask that is named colour background that created it. When comparing it to Photo we could see that there is a slider called Constant that isn't being reproduced. If you edit the Offset in Photo to match the Photoshop version you will see the green. I will get this logged. As PSD's are Adobe's proprietary file format, we can only interpret them. The feature sets aren't 1:1 so you can't always map them easily from one application to the other.

Yes, I realised it was Photo but mistyped. I've just corrected it. Can I ask if you are using a Mac or a Windows machine?

No problem, I will add your post link to the issue.

Hi @Benjamin Kanarek Welcome to the Affinity forums. Could you check to see if the option to Import PSD Smart Objects Where Possible is ticked? One Mac: Affinity Photo > Preferences > General On Windows: Edit > Preferences > General

Hi @Alex M Could you tell me which macOS you are using please? I've just tried this on Big Sur on both Designer 1.10.3 and 1.10.4 and can not see any noticeable difference.

Hi @Fordtman Sorry to hear you are having issues with saving and exporting files. So that we can see what is happening I have a few questions for you. 1. Is this happening will all files or just specific files? If it happening on specific files could you upload them here please? 2. Did you purchase Photo from the Affinity Store or the Windows Store? 3. Do you have a crash log that you could upload here please? 4. Have you installed any new software from this list recently? https://forum.affinity.serif.com/index.php?/topic/44770-issues-caused-by-third-party-software/

Hi @norbinw As I mentioned above, I'd need some additional information to look into this for you: What Mac & macOS are you using? Is this happening with specific files or on new document as well? If it affects specific files could you upload them here so we can take a look please? Did you get a crash log when the app closed? If so, could you attach it here or upload it to the link above?

Hi @asherdub Welcome to the Affinity forums! Sorry to hear you are unable to open your project. Could you upload it here so we can take a look please?

HI @Taivi Sorry to hear you experiencing crashes and loss of work. Saving in multiple locations is a very good habit to get into regardless of the software that you use. So that I can look into your specific issue can you give me some more information? What Mac & macOS are you using? Is this happening with specific files or on new document as well? If it affects specific files could you upload them here so we can take a look please? Did you get a crash log when the app closed? If so, could you attach it here or upload it to the link above?

@Vince B. That's what I did, the only difference was that my rectangles had a fill applied. I removed that and it still didn't crash. I will log the issue with your file and pass the information on to the development team. Just out of interest, can you tell me where you store the file? Is it on a local drive / network drive / cloud storage?

A lot of the rectangles in your design won't select when I click them. I haven't been able to recreate this state so when I try to divide the shapes in my document it seems to work. Try this one. Highlight everything and click Divide on this file. Divide-test-file.afdesign

Hi @Vince B. Welcome to the Affinity forums. Sorry to hear you are experiencing crashing. I've been able to recreate the issue on your document by selecting everything and clicking Divide, but I haven't been able to recreate the issue from scratch. Can you tell me anything about how you created the document? I agree with @Hangman that the best way to achieve the results you were after is to use a clipping mask. It's a less destructive way of doing things and you can remove the mask if you need to or change your mind.

No problem, good news that you can't recreate it. Get back to me if you do find it. 👍

@WaveF Sorry for the delay in replying. Could you upload your document here please so I could take a look? Then I can try and recreate the issue from scratch.

@kwaku & @Hangman That second document was definitely slow to render for me and when viewing the resource manager it became unresponsive. This looks to be down to the amount of layers using the layer effect. The Smart Object option in Preferences is disabled by default and once I enabled that and the option to "Import PSD text as text rather than bitmap" it improved. It also allowed the PSD to function as intended and update the drop shadow. I then modified it to add my own text as intended and the lag I previously saw when viewing the resource manager was gone too. The performance you're seeing is certainly not intentional to discourage the use of PSDs, but as the feature sets aren't 1:1 you can't always map them easily from one application to the other so you may get some things perform worse than others. In this case the 402 pixel layers (if you didn't enable Import PSD Smart objects as Smart objectS) was likely causing the memory to struggle in some places. @Hangman, with regards to the 0kb showing up, we're not entirely sure why, but suspect it's likely related to it coming from a PSD Smart Object where the file size is not logged. However, I will get the Gradient Overlay position looked at as I can see that with just a single layer.

Thanks for the update @tonywaghorn 👍

Hi @Antony parks I'm glad the LKB link was useful. I haven't used her blog much as I took part in her tutorials on Skillshare but as it's a paid subscription it's not one I can really share. I didn't realise that the first one on the blog was all about symbols as I've only covered her lessons using Assets so far. I'm glad it was useful. Thanks for the document, I'll give it a poke.

Hi @tonywaghorn Sorry for the delay in replying to you. Does this always happen with a specific palette? If so is it a custom created palette? Have you tried remaking it? There was a previous post where a customer had created a custom palette that would crash when edited. Once he remade it, everything worked fine.