Jump to content
You must now use your email address to sign in [click for more info] ×

NathanC

Staff
  • Posts

    2,738
  • Joined

Posts posted by NathanC

  1. Welcome to the forums @Giorgio37,

    This is a known bug in the Photo persona, having a bleed set on the document will cause selection functions (Select Sampled Colour, Tonal Range, Colour Range etc.) to become offset when applied. Back in the Publisher persona if you remove the bleed via the Document Setup menu and then use the same selection function again this should work. I'll bump the existing issue with your report.

  2. 13 minutes ago, Udo B. said:

    I noticed in the benchmark that no values were determined for the "grid (multi-GPU)“ and "combined (multiple GPUs)" points.

    Is that normal?

    Yeah that's completely normal for Silicon Macs, as this only applies to Multi-GPU hardware, for example my Windows device has both a dedicated Graphics card and Integrated Graphics, so it gives me a combination score in this field.

    ---

    Thanks for giving safe mode a try, unfortunately I don't have any direct access to an M3 device, however I'll raise it internally and see if I can get this MacOS version checked on M3. To rule out there being any local user environment issues on your device, could you try creating a new temporary Mac user and running the app from this new user account for comparison?

    https://support.apple.com/en-gb/guide/mac-help/mchl3e281fc9/mac

    Thanks

  3. On 4/4/2024 at 10:55 AM, Udo B. said:

    I have already restarted the Mac several times - without success.

    Thanks for confirming, just needed to rule that one out early.

    It may be something environmental or possibly specific to M3's as on my M1 I'm not experiencing any of the same performance issues running the same version. The document shown in your recording does have a quite complex layer structure with multiple live filters active, any chance you could send a copy of that .afphoto document over for a fair comparison as well as a screenshot of your performance settings in the app? I've added a private upload link below for the file.

    https://www.dropbox.com/request/QHDcJKjoPbMtbL0AnKzt

    Could you also try a Mac Safe mode boot and running the app, and then trying to run it again out of safe mode? This also clears some of the caches that could be problematic.

    https://support.apple.com/en-gb/116946

    Thanks

  4. Welcome to the forums @lagmoellertim,

    While there is some differences between how the two apps generate and move the mesh, there does appear to be a bug with the liquify filter as eventually an unwarp-able image renders in the background, However using the destructive liquify persona rather than the filter does not trigger this bug, i'll get this logged.

     As thomaso suggested, try using a combination of liquify tools, particularly the twirl tool rather than just trying to push forward tool over and over again in the same location, as this will eventually just form blade-like swirls.

     

  5. Thanks, wow that file is huge. Exporting from desktop works, but reached RAM usage of 13GB during the export process, which far exceeds the general iPad RAM capacity so that's probably related to why it's crashing. I can't get the ghost files to appear but I can get it to crash when it really shouldn't be so I'll log this with the developers.

  6. Hi @LiquidThinking,

    Are those files that don't have thumbnail previews, are they .afdesign files or something else, such as .SVG? For those .afdesign files that don't have thumbnails present, have you tried opening them, checking 'Save thumbnails with documents' is enabled under Preferences, and then triggering a modification of the file by showing/hiding a layer and then saving again?

    If it doesn't work, you could also try clearing your windows thumbnail cache: https://www.windowscentral.com/how-reset-thumbnail-cache-windows-10

  7. Hi @Affinity Rat,

    While I agree from your description this is definitely unexpected behaviour as a result of a crash, I'm quite limited by what I can log and report to the developers on how to trigger this. Is this something you can replicate by performing the same steps in the app? If you are able to, could you provide the document which causes the crash?

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.