NathanC

Hi @anto, This has been logged with the devs previously, I've bumped the issue with your report.

Hi @Chiefsub68, Could you perhaps shape the document with us where you're encountering the crash when linking frames? The crash report backtrace makes reference to Pinning/Notes in the events leading up to the crash so it would be helpful if we could take a look and confirm if it can be replicated. If you don't wish to share the document publicly I've added a private upload link below. https://www.dropbox.com/request/A670ASXszSMFkjIXIeQm Thanks

No worries, I have just had some clarification internally that in v2.3.1 the functionality wasn't available as the key object selection only worked with the alignment options, not the spacing options so you'd essentially have the same functionality in 2.4.2 by not selecting a key object as the object was ignored in 2.3.1 anyway. That doesn't change the fact that this is logged and we'll hopefully see it added. 2.4 feature overview:

Hi @Mr. Doodlezz, This missing functionality to turn off 'auto distribute' and set a user defined distance when considering a key object is currently logged internally so i've bumped it with your report. Also many thanks for the recording as i've added this on since you've clearly demonstrated it was possible in 2.3.1 so i've added this info onto the internal report. I can't really say why this was changed in 2.4.X but hopefully we'll see it added back in.

Hi @kirk23, I've bumped the issue internally with your report with regard to the 'Update' not capturing newly created layers, i'm still waiting to hear back from the devs as it currently stands.

Thanks @MikeTO, the apostrophe bug is logged (AF-1399) and has now been tagged on this thread, I think there's just been some confusion/wires crossed as that specific bug was originally reported and dealt with separately via email, while the original focus of this thread was the problem with importing/pasting cyrillic text that we can't replicate in 2.4.2. However, it's quite interesting that you can via Copy/Paste so there must be some environmental differences, have you got a clipboard manager app active? I'm also just using the latest available version of Word for Mac from 365 (v16.83), so perhaps there's something with your current version of Word.

Thanks @DGee, Looks like there is a bug with the .PSD clipping mask import with smart objects, we do have this logged with the developers so i'll bump it with your report.

Hi @Marco Soijer, Thanks for sending those files over, i've been able to create from and edit both templates without any resulting app crashes across a few different devices, but I did find the app crashes following an app quit which is a template/UI related bug rather than specific problem with your files. Since i'm not seeing the crashes on my side it could be related to that 'Logo Full RGB.afdesign' file since that's a linked resource I don't have access to, the location of the resource appears to be local to your documents folder. If you either delete or move this .afdesign file so it unlinks and then try opening the file again see if it crashes.

Hi @Marco Soijer, Sorry for the late reply, if you could upload a copy of your file to the private dropbox link below we'll take a further look. https://www.dropbox.com/request/oJCMJYon3Ry1t8nEmmMs Thanks

Hi @chelcod, The app may be having trouble maintaining a connection to the location your file is stored on, such as an External Drive, Network Drive or Cloud Storage. You should still be offered the option to 'Save As' when this happens, but try moving your file to your local storage and saving back locally as this should prevent the issue.

Hey @jonwright, It sounds like your vector objects are getting flattened to pixel layers on export possibly due to unsupported properties affecting the curve objects such as FX or Adjustment layers- but regardless of that happening the corruptions/artefacts present on the final document should not be occurring. I'd suggest disabling Hardware acceleration found under the app Settings -> Performance. Once the setting has been unchecked close the interface and restart the app when prompted to before trying the export again. There's a known bug logged internally with raster corruptions occurring with metal enabled on PDF which is very similar to what you're describing, but this bug trigger relies on JPEG compression being enabled at 98 rather than disabled, so hopefully this will also work for you.

Hi @Udo B., Thanks for the recording and steps, I've now been able to re-produce the issue on my M1 mac using your file. There appears to be a bug with the Info panel's live sampling and the panel's interaction with live filters in your 'Group' layer, as soon as I delete the 'Group' which contains these filters performance returns to normal with the Info panel active. I'll get this logged with the developers for further investigation and resolution. I found that while performance was good if I toggled the Info panel off from the 'Window' menu the performance remained strong during subsequent app sessions, so I'd suggest keeping this panel toggled off entirely for now, and if it needs to be used follow your workaround to return the app performance to normal.

Hi @anto, This is similar to what you've reported in the thread below albeit with a different recipe, but i've replicated and logged this separately with the developers.

Hi @Bartek, To me this looks like a bug, particularly as setting the left node K100 only and the other to 4C black does show a colour gradient on the gradient map dialog, and there is a somewhat similar issue logged with the CMYK sliders failing to convert to RGB correctly. I'll log this with the developers for further investigation and confirmation.

Hi @anto, I'm not seeing this behaviour in 2.4.2, my page view remains where I left it before clicking save. could you possibly share a screen recording and a sample file?

Hi @DGee, The Unknown property errors are normally the result of a lack of feature parity between the apps on FX layers resulting in mapping issues which can also include gradient fills, improved support has been requested before such as the thread below and is hopefully something we'll see in later versions. As for the masking issue, could we take a look at the .PSD file?

Welcome to the forums @paradrenaline, We'll need a bit more information, so I've included a few queries below: - What Operating System are you using? - What Affinity App(s) are you using, and what version are they? - What objects are you copying? E.G pixel layers, quick shapes, curves etc. - Can you provide a screen recording that demonstrates what happens when copy/pasting within the app? Many thanks

Hi @Natters, Could you provide a copy of the crash reports, as well as a copy of the document(s) where you're typically experiencing these crashes? We can then look into this further by confirming if it can be replicated and the potential source of the crashes. I've provided a private upload link below if you don't wish to share the file publicly. https://www.dropbox.com/request/WP8UKTDiWG02kW1P2xDo Crash report FAQ: Thanks

It's normal/expected, your initial adjustment has no effect as the exposure value is set to 0, so there is no greyscale preview of the mask.

Thanks @Hangman I had noticed that the adjustment had no value set, but I had overlooked preview being set in the mask dialog on OP's screenshot which you've pointed out. Yes, as far as i'm aware that's the expected behaviour, 'Preview' shows a greyscale preview of what's being masked, and since the adjustment is having no effect on the image, the luminosity mask nested to the adjustment also has no effect and so the preview of what's being masked is empty.

Hi @paperova, Could you provide a copy of the full crash report files from the app so we can debug and see if the error can be identified? FAQ on finding these below. Thanks

Good to hear that it works on the new user, however unfortunately local user account issues can be quite difficult to identify, as there could be a problem with the mac user account itself if there's no difference in terms of the active and background programs running. The Affinity apps store the app preferences and user settings in the local user library folder, so by creating a new user these files are re-created. You could try deleting these files + folder on your original user to reset the apps, but there's no guarantee this will work but it will eliminate the possibility of the problem relating to the local app files, you can get to these folders via spotlight search (CMD + Space) ~/Library/Group Containers/ delete or rename the '6LVTQB9699.com.seriflabs’ folder. ~/Library/Containers/com.seriflabs.affinityphoto2/Data/Library/Preferences/ delete or rename the com.seriflabs.affinityphoto2.plist file. ~/library/application support/ delete or rename the 'Affinity Photo 2' folder.

Thanks for sending the file over, i'm also observing this page view render issue when changing the zoom level, unusually it doesn't happen when the file is linked, only as an embedded resource. I'll log this with the developers for further investigation.

Thanks, looks like it may be a rendering issue on your local device, as it's loading as expected on my side, and continues to do so as the exposure is increased or the Luminosity map is changed. I'd suggest disabling Hardware Acceleration under Edit -> Settings -> Performance, close the interface and restart the app and see how it goes.

Thanks @Hangman, This works as expected on Sonoma but as soon as I switched over to Monterey it broke as you described until the CTRL + TAB, i'll log this.