NathanC

You'll probably need to convert the file's to a compatible RAW format, such as using Adobe's DNG converter tool. https://helpx.adobe.com/camera-raw/using/adobe-dng-converter.html#:~:text=download the dng converter RAW support relies on the LibRAW decoder supporting the format first, it's possible that support will be extended to the High Efficiency format. If support is added it will be reflected on the official supported formats thread linked below.

Welcome to the forums @IvashistaI, Support for the Z8 RAW format in Photo covers standard compression formats only. If your Images were shot with the RAW recording set to 'High Efficiency' this will be the reason the file fails to open as this isn't supported. I've linked the manual below which details how to change this setting on your Camera. https://onlinemanual.nikonimglib.com/z8/en/psm_raw_recording_123.html

フォーラムへようこそ @I.Nishikawa ペイントミキサーブラシの「強さ」を100%に設定すると、色が正しく混ざらないというバグがあります。強さを99%に設定してもう一度ペイントしてみてください。 ----- There's a known bug with the Paint Mixer brush with the Strength value set to 100%, the colours fail to mix correctly. Try setting the Strength to 99% and paint again, it should now mix the colours.

Hi @Fanie Prins, Many thanks for your detailed report and sample files, I've replicated the app hang and logged it with the developers.

Thanks @Natters for sending them over, I should've included this on my previous reply but for future reference please reply back on the thread once you've uploaded the contents as we are not automatically notified when files are uploaded. The process name in the reports is listed as 'Affinity Publisher 2 Affinity Store' which makes it easy to identify if it was originally installed via the Mac app store or directly via the Affinity store, the store is not the cause of the crash. I've had your document open for a while and I'm able to freely edit your file without any subsequent crashes. However, I don't have access to any of the many linked resources used in the document. Based on this factor and the crash report backtrace indicating towards the app communicating with your dropbox link leading up to the crash I believe this may be the source of the problem. Unfortunately I don't have a way of identifying any specific resource or location from the crash report as the cause, but what you could try is downloading the resources so they are stored locally instead of on dropbox, and then unlinking from dropbox in the app 'Linked Services'. Hopefully this should then cause the resources to become unlinked in resource manager, so you can then use the 'Relink' function from resource manager to re-associate the file paths of the local resources and then see if this prevents the intermittent crashes.

Hey @David Battistella, I'm assuming that you've sourced the Latin dictionary files extracted from the .OXT file provided by David in the thread below since you posted there? I opted to rename the files to 'la_VA.dic' and 'la_VA.aff' based on the advice of MikeTO and then put them in them both in the root of the ~/Library/Spelling/ folder instead of putting them inside another subfolder. Once I did this I restarted the app, checked back in the Language section of the character panel and I was able to change the spelling language to 'Latin (Vatican City)'. For me it was listed at the very bottom of the spelling dropdown list.

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