NathanC

Hi @Bryan Rieger, Thanks for reporting, I've replicated and logged this with the developers, it looks like the Appearance panel stroke width value is not correctly updating.

Hi @Mike Christelow, Can you confirm if the issue is specific to that document only, or does this happen when creating new files or when opening other publisher docs? If the app fails to create a new document/open any existing documents, this can be an indication of a GPU/Driver based issue on your device which is causing Affinity to crash when rendering the canvas/page area, as while OpenCL may not be for your Graphics card the app will still likely be using your GPU as the app renderer. I've provided some potential solutions to run through below. Update your GPU Drivers Make sure that you have the latest available drivers installed for your GPU, I've linked the Nvidia search tool below. If given the option during the driver installation, check 'Perform Clean installation'. https://www.nvidia.com/download/find.aspx Once you have updated your drivers, restart your PC and then try creating a new document, if that works try loading the existing document again. Reset drivers via DDU If it still freezes/crashes, try doing a complete uninstall of your graphics card drivers using a dedicated tool for this purpose (Such as DDU linked below) and then restart and install your graphics card drivers (using the link above to search) to completely refresh them. https://www.guru3d.com/files-details/display-driver-uninstaller-download.html -- Let me know how it goes. If the crashes persist after trying both of the above, could you possibly upload a few more recent crash reports? I attempted to debug your uploaded one but it fails to debug successfully. Many thanks

Welcome to the forums @No Tuppence, Could we possibly take a look at your original .afdesign file you created for the repeat pattern, along with the exported PNG/JPEG used for the bitmap fill so we can see what's potentially causing this? If you don't wish to share the files publicly I've provided a private upload link below. https://www.dropbox.com/request/GDDFZ56cA2rTFOVzA5jK Many thanks

Welcome to the forums @MFH, Could we take a look at the problem document and see if the crashes can be replicated? If you 'Save As' the document to an .AF file from the app live docs/home screen via the Burger menu (3 lines) and then upload it to the private dropbox link below that would be great. Upload link: https://www.dropbox.com/request/8wxJL2RYYHzLL5ZwLVin In addition to the file, could you advise which Affinity app you're using and what the app version is, along with your iPad model and IOS version? Many thanks

Hi @Lobivia, This Export Area recall issue is currently logged with the developers as Hangman has referenced, i'll bump the existing issue with your report. 🙂

Hi @clonkel, This is a known issue with the displacement live filter currently logged with the developers, i've now bumped it with your report. Also, many thanks for demonstrating your workaround. 🙂

Similar queries have cropped up previously with regard to this workflow, James's reply in the thread linked below should be helpful if you're attempting to export from an EXR to a standard gamma-encoded format such as PNG, the preview should be kept as a standard ICC display transform over using an OCIO transform. And another similar expanation in the thread linked below

Hi @leminilab, This isn't particularly an area of expertise for me, but have you watched the OCIO setup and usage video tutorial? This tutorial may provide some clarity on the available options in both the 32 bit preview panel for display transform/calibration, as well as a use case for the OCIO adjustment layer. Additional info is also available in the links below. https://affinity.help/photo2/English.lproj/pages/HDR/ocio.html https://affinity.help/photo2/English.lproj/pages/Adjustments/adjustment_ocio.html

Welome to the forums @McAdamsx, Try Window (along the top menu bar) > Zoom and this should bring the app window back into focus. 🙂

I've now logged this with the developers for further investigation, taking the bucket JPEG as the sample file I observed the artefacts were visible on the cropped + rotated image without requiring any colour profile conversion on export, and became more defined the lower the compression value set.

Hi @gsax, This Recent Colours inconsistency is currently logged with the developers, i've now bumped it with your report.

Hi @Hangman, Looks like this is an OS-specific bug in V2 on Monterey, as i'm able to replicate this using your examples provided on Monterey consistently for the first instance but not whatsoever on Sonoma. I've now logged this with the developers. 🙂

I'm also being prompted to enter a brush name when selecting 'Save as' on both the Pixel and Vector brush tools across MacOS and Windows and I've not been able to create a scenario where it doesn't do this thus far.

Thanks, i've added info this onto the existing report as it appears to have the same trigger (Select Bottom/Top), just a different selection.

Welcome to the forums @cookkoo, The pre-flight warning indicates that the spelling language used for your text frames is set to one that is missing on your system, for example if the document was created on a different system with access to that dictionary this warning would prompt. This can normally be resolved by importing the missing dictionary onto your device via the Hunspell dictionary library, however I can't find one for en-TH available in their library (English-Thai maybe? Not sure). In this scenario it would likely be easier to just change the spelling language of all text and art text frames in your document. One way to do this is to use the Select (Along the top menu bar) > Select Object > Frame Text to highlight all the text frames in your document, and in the 'Character' panel (Window > Text > Character) under the 'Language' dropdown set the spelling language over to an English dialect that is available. You can then repeat this for Art Text layers if applicable. After correcting your existing document I would also suggest defaulting your text frame tool to use an available spelling language, with the tool selected and the language updated in the Character panel go to Edit > Defaults > Save. You can then repeat this for Art text.

Welcome to the forums @Arend, We have a dedicated video tutorial linked below which details the process of installing dictionaries on both MacOS and Windows.

Hi @Affinity_Pro, Good spot, I've now logged this with the docs team for correction.

Hi @FrM, I've now replicated and logged this issue with the developers.

The Isometric panel is a Designer exclusive feature so the panel not prompting in the Publisher persona in V2 (and V1 Windows) is the expected behaviour, and the V1 MacOS Publisher persona behaviour was likely an oversight. It could be argued that the panel would prompt if the user has access to the Designer Persona in Publisher, but at that point it would be feature request.

Hi @Polygonius, On the basis you purchased the app via the Affinity store once you've signed in to your Affinity ID you can access your Universal License downloads on the 'V2 Licenses and downloads' page linked below. https://store.serif.com/en-gb/account/licences/

Hi @Dybkjær, This import styles crash bug is a known issue that has been fixed in 2.4 beta, meaning that when 2.4 is officially released this fix will be present. 🙂

Hey @MikeTO, This is currently logged with the developers, i'll bump it with your report. 🙂

As @Return's found the problem appears to be with the stock images themselves, as the grey line is visible on the stock download from pixabay.com directly, which takes affinity out of the equation. I've just checked and it's the same with that initial 'Face' image, the grey line is visible on the high res download directly from the website.

Hi @Iztok, RAW Support for the DC-S5M2 has not yet been added in Photo 2, the FAQ below details the currently supported Camera RAW models.

Hey @Hangman, Thanks for the steps and recording, I've replicated this issue and logged it with the developers. 🙂