stokerg

Hi @MikeTO, I've no doubt you are correct but I'm struggling to get the exact workflow to show the issue. If you could give me a set of steps to follow, I'll get this logged with the Developers, as it doesn't look like this is logged or come up before

Hi @MikeTO, Thanks for reporting this. I've replicated it and have just logged this with the Developers

Hi @joe_l, Thanks for reporting this. I've replicated it here and from checking the previous versions of Affinity, this appears to have stopped working in 2.1.0. I'll get this logged with the Developers

Hi @Alex_M, I've replicated this in 2.4 and the behaviour is different to 2.3.1, so I've logged this with the Developers We already have this logged I've updated the report with a link back to this thread so the Serif Info Bot can update you when it's been resolved.

Hi @Alex_M, Thanks for reporting this. 've replicated the issue and have just logged this with the Developers

Hi @Michail Potemkinand Welcome the Forums, This is a known issue that we have logged with the Developers. I've left a link on that report back to this thread, so you'll get a notification from the Serif Info Bot when this has been resolved

Hi @Karokazzyand Welcome to the Forums, As @walt.farrellhas pointed out, the Live Docs areas is stored in a Sandboxed area, so its not straight forward to get access to. But the steps in the linked thread, as the best methods to try and recover a file when it gets in this state. We do have this logged with the Developers that this can happen but as of yet, don't have an exact recipe of what causes it and haven't been able to replicate it happening. So if theres anything about your workflow or if you noticed a pattern to it happening, please do let us know.

Hi @combdnand @Old Bruce This is a bug and is already logged with the Developers. I've updated the report with a link back to this thread so you'll get a notification from the Serif Info Bot when this has been resolved

Hi @Shamblerand Welcome to the Forums, Glad to hear everything is now working. Normally issues with starting New Documents are related to graphics card drivers or Hardware Acceleration, which can be disabled in Settings>Performance.

Hi @Floor, Thanks for reporting this. I've been able to replicate this and have just gotten this logged with the Developers. It could very well be related to AF-1162 from what i can gather from reading that bug report. Either way, this has been logged as a crash is always unwanted behaviour. This thread will get a reply from the Serif Info Bot when this has been resolved and if theres any feedback from the Developers, i'll update here as well

Hi @prophet, Thanks for reporting this. @ronnybis correct and this is something we already have logged with the Developers. I've updated the report with link back to this thread so you'll get a notification from the Serif Info Bot when this has been resolved

Hi @Bryan Rieger, A couple of us here in the office have been able to replicate this with the States panel not showing. Bit tricky to constantly replicate as it appears to only happen after first updating from 2.3 to 2.4 I've just logged this with the Developers and have left link back to this thread so the Serif Info Bot will update here when this has been resolved

Hi @Interior Book Design, Thanks for reporting this. We do already have this logged with the Developers. I've updated that report with a link back to this thread, so you'll get a notification from the Serif Info Bot when this has been resolved. @walt.farrell afb-6879 was fixed a few builds back and a new Bug Report was created: AF-1036 which this issue fits under

Hi @sansnom, I believe this is the issue you are encountering and an improvement has been logged to make this feature work when duplicating objects by dragging them:

Hi @Ken Hjulstrom, Like @R C-R, this is also working for me. Can you create a screen recording of the issue? To record your screen, see here.

Hi @DrewRomo, I can see that @NathanC replied to your email to us about this and has logged this with the Developers. I'll leave it with the Developers because if @NathanC can't recover the file, then it will need to be looked at by the Developers.

Hi @DrewRomoand Welcome to the Forums, Would you be able to attach the file or upload it to our Dropbox here and i'll see if it can be recovered?

Hi @Saro, Which operating system are you running Affinity on? When the switch happens and you start Masking, if you look at the History panel, what does state the last few actions were?

Hi @stevedband Welcome to the Forums, This isn't something I can replicate on my Windows laptop. Would you be able to provide the RAW file you are working with? I've set you up a Dropbox link here to upload the RAW to.

Hi @dpt, Thanks for reporting this. This is something we already have logged with the Developers to resolve. I've updated that report with a link back to this thread and you'll get a notification from the Serif Info Bot when this has been resolved

Hi @lysynski, Is that an 8-bit, 16-bit or 32-bit file? If 8 or 16-bit, does following the same workflow in a 32-bit document clear the banding/ribs?

Hi @Foucault, Sorry, you've experienced this. The autosave only keeps track of changes, so needs the original file in order to apply those changes. It's not meant for recovery in this way, which is why you get the message about it being linked to another file. Could you see this link can you just check and see if you have a crash report that would match up to the date of the crash and attach the crash report here? As crash is always unwanted behaviour but seeing as it also deleted the .afpub file, I'm hoping that's covered in the log file. If you could attach the .autosave file, i can see if there's anything that can be here to extract some data from the file but I suspect it won't be a complete copy of your original file due to how the autosave function works. Sadly there isn't much more you can do, you may have luck with a File Recovery app that can recover deleted files.

Hallo @TMCC und willkommen im Forum, Ist das Affinity Designer Version 1 oder 2? Auf welchem Betriebssystem führen Sie Affinity aus?

Hi @F5subli, Could you just try this in the 2.4 beta? There was an issue in this area resolved in the beta, so would be interesting to see if you can replicate the issue in the beta. You can sign up for the beta via this link: https://affinity.serif.com/affinity-beta-program/

Yup thats my mistake. Hadn't spotted that was in the Archived section of the Forums. Here's one that isn't Archived: Wonder if having multiple devices connected is affecting things? I know the few times i've tried this when i had a scanner in the past it worked and i would only of had the scanner connected to my Mac at the time.