NathanC

Hi @Ranpo, Thanks for providing detail, I've been able to replicate this on MacOS and Windows using a V1 file and it has now been logged with the developers.

Hallo @Sigurt, Wenn Sie im Explorer keine Miniaturvorschau Ihres Dokuments sehen, liegt das daran, dass es derzeit eine geöffnete Datei in Publisher ist. Wenn Sie die Datei schließen, sollte die Miniaturansicht aktualisiert werden. Dies ist ein Problem, das bei den Entwicklern protokolliert wurde. Deinen Bericht habe ich hinzugefügt.

Hi @BryantJwelcome to the forums, We're currently aware of an issue with the adjustment panels flickering when the iPad is held/positioned at certain angles, this is logged with the developers. I've not been able to replicate an issue with adjusting the gradient map values, however. If this is something you're able to replicate I would be grateful if you can provide a screen recording demonstrating the issue. Many thanks!

Hi @MikeTO, Thanks, I've now logged the issue with the development team.

Thanks, this crash isn't occuring for me using your file, though as Paul mentioned you are using a mesh warp on an image/pixel layer, if you create a new document and then add a vector curve and try and add a mesh warp to it, does the crash still occur?

Could you provide me with a few recent crash report(s)? Many thanks

Many thanks for providing further detail, It doesn't appear to matter if the file is an .afdesign or an .afphoto to get this layer visibility menu to appear, you need to ensure that your linked file contains a Layer container which can only be created in Designer/Publisher, so in order to get new layers to appear in an .afphoto file open in Photo 2 you would need to duplicate a layer or paste one in to the file, for example. Following your workflow, I created an .afphoto file and then opened it in Designer and added 4 Container Layers and saved. I then placed this .afphoto file into Publisher which then gave me the 'Layers' dropdown showing my 4 layers. Back in Designer, when I added an additional container layer and saved the file. Back in Publisher, this then updated automatically and when I checked the Layer visibility toggle I now had 5 Layers to toggle between. The above was done with update external resources automatically enabled in Publisher, without this enabled I had to manually update the resource in resource manager, at which point my 5th layer appeared, as expected. I'll continue to try and replicate this on a few different devices to see if I can get this to fail to update the layer visibility.

I've been toggling visibility of the layers within the .afphoto file in the Photo 2 and then saving and checking the resource manager in APub. I've also just tried this by opening the linked .afphoto file in Publisher and then toggling layer visibility in the file and saving, but this is still updating as expected in resource manager back in my publisher doc.

Thanks for sending the crash report via PM @nobduck, We'll focus on trying to get one app working rather than removing them all, could you try a complete re-install of Designer 2 by following the below: From applications, move Designer 2 over to the bin and delete it From finder, press CMD + Space to bring up Spotlight search and enter ~/Library/Application Support/ In the Application Support folder, rename the 'Affinity Designer 2' folder to another name, like 'Affinity Designer 2 old' Go to the Affinity store and re-download and install Designer 2 again Once installed, launch the app again and try and open and edit your files. If this works then this can be repeated for the other two apps.

Out of control? Whoops, Corrected. Thanks

Thanks for sending that over, since the print dialog framework is shared with other mac apps it's possibly a Ventura issue as you've mentioned. Since we've not been able to replicate this yet, do you mind confirming this by trying this in an alternative app (such as Pages)? Many thanks

Hi @pjglad, This issue is currently logged with the developers for resolution, I've bumped the issue with your report.

Hi @joe_l, I'm struggling to re-create this on Windows 10, I created a new blank publisher document (auto update enabled) and separately created an .afphoto document with 3 coloured rectangles with the top two hidden, when I placed the file (as linked) and then toggled the visibility of the layers and then saved the .afphoto file in Photo 2, it auto updated in my publisher document and the resource manager thumbnail correctly reflected the current document's state and did not show the 'old' version. Am I missing something key? Could you possibly provide me with a screen recording/sample file(s) used? Many thanks!

Hi @sw-fuzzy Affinity Photo uses the Lensfun database for lens correction when developing RAW files, It looks like the current release of Lensfun doesn't contain support for your lens, which is why this is not compatible with Photo currently. We are reliant on Lensfun adding support for these lenses in a future update for Photo to be able to support this lens by default. Unfortunately I cannot provide a timescale for this, as it relies on third parties, which are out of our control.

Hi @Deano.S welcome to the forums, I've not been able to replicate your issue with an Intuos P S on Ventura, screen panning responsiveness is identical when using mouse or pen to pan the screen. Could you confirm/try the below: Disable hardware acceleration under Preferences > Performance, restarting the app and trying again. Re-install your tablet drivers. Does this issue occur on a new blank document (with no other documents open)? What tablet model are you using?

Hi @tatanka, We've not been able to replicate your issue on Ventura or Monterey, the ICC profile and print quality settings are retained that the Preset was originally created with when recalled. Could you provide me with a screen recording which demonstrates the issue from creating the Preset to recalling it? Screen recording guide: https://support.apple.com/en-gb/HT208721 Many thanks!

Hi @tonyt, I can't replicate this on iOS 16, after re-ordering both a basic brush to the top of the list and then closing the app the order is retained, even when starting new documents. Have you tried this with a brush in the basic category? I also was not able to replicate this with an affinity store brush pack. Could you possibly provide me with a screen recording demonstrating the issue? Additionally, if this does only affect a specific brush category, could you provide me with the exported .afbrushes file? Screen recording guide: https://support.apple.com/en-gb/guide/ipad/ipad08a40f3b/ipados Many thanks in advance!

Hi @RomanMtz welcome to the forums, Could you provide me with the file you're having issues with so I can investigate further? I can provide a private upload link if required. Many thanks!

Hi @Erica176, I've logged your broken file with the developers so they can diagnose what might have caused the file to corrupt.

Hi @Markus M, I've now logged this with the developers and added the details of your report, many thanks 🙂

Hi @Fantomas.CZ @MikeTO, Many thanks for providing detail on this issue, I've been able to replicate the problem using Mike's file and have now reported it to the developers for further investigation/resolution.

Hi @David Dessert welcome to the forums, This crash is likely occurring as Photo V1 does not support RAW files from this camera, after following your workflow in V2 which does support RAW files from the X-H2s this adds it without crashing as expected. V1 Raw support list: V2 Raw support list:

Hi @Morast welcome to the forums, Could you provide me with the brush pack that you're experiencing this issue with? I can provide a private upload link if needed.

Welcome to the forums @jadeb, Could you advise if this behaviour occurs when just using a standard basic round brush or does this only happen with custom brushes? Could you try doing a force restart of your iPad to clear the cache to see if that makes a difference? Guide below. Additionally, could you provide a screen recording of this happening on iPad on a new document? Screen recording guide: https://support.apple.com/en-gb/guide/ipad/ipad08a40f3b/ipados

Hi @tonyt, This is currently logged with the developers, I've bumped the issue with your report.