Chris B

Hey Affinity-Inspiration, Can you attach that document, please? If you can enable History with the document from the File menu, that would be brilliant.

@debraspicher we may have made some progress with this as @Dan C has been able to reproduce it and recorded a video. We can get this logged and see if the developers can find a solution

You are right, however, I just thought that if we can start gathering info on the Taskbar settings that everyone is using it might shed some light on these two issues that we're seeing.

I get the crash doing File > Place with only 4GB VRAM

Hey Designer1, Respectfully, I've split this from the PNG HDR thread posted by Ash as we want to keep replies relevant to the new feature. We understand your feelings regarding the current PNG/JPEG export and any further comments should be posted in your existing thread if possible. That way, if and when the time comes that the developers wish to look into this, everything is in one place.

I wonder if this is relevant: I did check this yesterday but my settings were already set to Always for both Combine taskbar buttons and hide labels & Combine taskbar buttons and hide labels on other taskbars

Ah, looks like we've only done it for UK. Sorry about that, we can get that sorted.

Hey Mac3104, I have reproduced this in the beta and will log it with the developers. Thanks!

Hey NotMyFault, This is a little odd but I think it's due to the PT—the rotation stuff is just a red herring. We've seen it in the past when using live filters (and masked adjustments). Sometimes, they will have undesirable effects on what is considered the document 'bounds'. Also, when uncropping an image when using multiple live filters etc. as it goes beyond the bounds of the pixel content. It's like adding a margin or border to the pixel content, I suppose. I'm not entirely sure what we could do. I'll check with development and see if they want anything logging.

That's good news (for now). I will see if there's something we need to do going forward.

Great news. I'm so glad that worked. Please let us know if the issue happens again.

Hey jinkah, That doesn't sound right. They should have recently been modified. I would uninstall everything and then do a fresh download of each of the apps and install them to the default location. Did you move the apps to your D drive at some point?

Could you also try the following: Run all the Affinity apps up and open a document With a document open, click the File menu Close the apps Navigate to: C:\Users\yourusername\.affinity\Publisher\2.0 Inside this folder, you should see a log.txt, please attach it and then repeat for the other remaining apps We want to make sure that the apps are all talking to each other correctly.

Are you using the MSIX version of the application or the EXE or are you using a mixture of MSIX and EXE?

Hey jinkah, Could you upload the .afmigrate file to this private Dropbox folder please - https://www.dropbox.com/request/3NqS3zOjJDOaM1F7m7zx We should be able to rename it and recover the file. I'm not sure why this is consistently happening for you, though.

I hear what you are saying. You do indeed make a fair point about this being reported before Sonoma and it's probably coincidental we are seeing more reports about this since Sonoma was released. After a further discussion, we'd like you to try something: Under Apple > System Settings > Privacy & Security > Files and Folders > expand each app and please disable 'iCloud Drive' for each app. This will not prevent you from saving to or loading from iCloud. This may prevent the seemingly infinite loading message you are getting.

This is not true. I have spent hours trying to reproduce this (as have staff in other departments). It's an unfortunate case of 'we just cannot reproduce it'. Developers have a very difficult time fixing something that cannot be reproduced. See this known issue post: It may be something that Apple needs to help us resolve.

I tried this intermittently yesterday however, I was not able to reproduce on Windows. I was using a similar recipe that I was using on macOS (dragging the window from screen to screen, min/maxing, etc.) I'm going to try today on a different setup and see what happens.

Thanks, I'll give it a poke and report back.

Is this with a second monitor connected to the Windows machine @anto?

I think just a brief run-through of your folder structure and the process of opening a file from its location will help. I can work on doing the other bits.

@anto and @TomJr I believe I have reproduced this issue. I have to trigger it in a very specific way though. I also managed to get the new document into a state where I cannot even properly close it but I certainly get the display issue where the new canvas does not fully display and I get perhaps 1/4 of it showing white and the rest is black. I will do further poking and can finally get this logged with the developers.

So I tried this when Nopemann provided a recipe - I could not reproduce it. I've just tried again this morning for a good 30 mins doing all sorts of combinations of loading, saving etc. from iCloud and I still cannot reproduce. I think a video recording of your workflow where you create a file, save it, attempt to open it and get the message might give us some clues. Other than that, I don't know what else I can suggest, sadly. It's certainly not from lack of trying.

Brilliant news! I'm really pleased about that!

Have you raised this before in here? https://forum.affinity.serif.com/index.php?/forum/122-feedback-for-the-affinity-v2-suite-of-products/ I do think it's a good idea but like I said, just a bit beyond the current scope—that doesn't mean it would never be considered. Cheers