stokerg

Nope you are correct, delete the artboard and keep the objects and the export/preview is fine. Just ran this past QA and they have informed me it's actually AF-1318 so has already been logged. This is caused by the Gradient Overlay Layer Effect using non-100% stops. I'll get the report updated with a link back to this thread so the Affinity Info Bot can update here when it has been resolved

Hi @simonsanchezart, I wonder if you are running into another version of the bug reported in this thread which affects the Colour Dodge blend mode and that likely would account for the colour issue on the egg? I'll try and confirm if that's the case and make sure there isn't a separate issue here that needs logging. @NotMyFaultThanks for reporting the issue with the Preview, as that is a separate issue. The Tech Agent who has that ticket will reply shortly

Hi @Hangman, Thanks for bringing this up. I was pretty sure this rang a bell with me and I've just found the original bug report (AFB-5840) This was a bug logged in a very early version of Affinity V2 and was fixed. So looks like this is a regression, sadly the bug report doesn't say what the fix was, so I'll need to do a bit of digging here. Let me find out when this regressed and I'll get the issue reopened and also confirm the expected behavior

Hi @gregj, Did exporting to a folder not managed by OneDrive, allow you to export?

At first i couldn't replicate this, but I've found out why. I was creating my alias in the same folder as the images, so the files were named 'imagename.png alias' and this just worked. However, I then created the alias outside of the folder with the images in so they are missing the 'alias' part from the file name and then I can replicate the issue you show. If you can just confirm I've done this the same way as you have, I'll get this logged with the Developers

Hi @Darner, Thanks for the recording and for reporting this. As @Hangman just stated, we've already got this logged with the Developers to resolve. I'll get a link added to the report back to this thread, so you'll get an update from the Affinity Info Bot when this has been resolved

Hi @Darner, What type of lines are you trying to Snap to? Are they grid lines? If you can attach a sample .afdesign file or a screenshot showing the full Affinity Designer window with the Layer panel on screen, that would be a big help

Hi @n.k.0508, While I don't get a crash, exporting your afbook file does cause my Publisher to just hang. I can cancel the Export but after that, the rest of the interface just doesn't respond to my clicks. I'll get this written up and logged with the Developers

Hi @Halex, Can you post a screenshot of the Dynamics section from the Brush Editor, for both V1 and V2. Please feel free to upload a better quality recording, as it's a bit difficult to make out all of the settings in the current recording.

Hi @Claudina19and Welcome to the Forums, This may be Metal acceleration causing this, so can you try switching it off? To do this, please click on the Affinity Photo menu in the top left corner and select Preferences>Performance and at the bottom of this dialog please untick Hardware Acceleration and close Settings. You'll then be asked to restart Affinity and once restarted, open the image, is it now displayed correctly?

Hi @Bololoco, Can you let me know your complete workflow? The way I would do this, create separate panoramics for each exposure set and then HDR merge those results.

Hi @KenWHand Welcome to the Forums, I've been able to reproduce this in V1 and V2 and have logged this with the Developers. However, as V1 is no longer actively being developed, I doubt the fix will make it into V1 of Affinity.

Hi @barbichn, Could you check for a crash report and attach it? To find the reports see here, you may have more than 1 report but please only attach the latest one as that will relate to this crash. Can you also see if disabling Hardware Acceleration in Edit>Settings>Performance improves things for you?

Hi @Peter Werner, We have had reports of this before but I don't think it's something we've been able to replicate here. I've tried replicating it here on my office laptop with multiple Assets files, all of different sizes and my Assets panel is refreshed each time. So I can try with the same files you are using, could you upload the assets you are importing to our Dropbox here and I'll see if I can replicate this with your files

Hi @Atlas Games Webmaster, Can you attach the file or upload it to our Dropbox here and I'll see if I can replicate the issue and get it logged with the Developers if needed

Hi @Mochiand Welcome to the Forums, I've just pressed the Force Resync button, so if you can now bring up the My Account feature in the app and sign out and back in, do all the addons now show?

Hi @Eva__and Welcome to the Forums, If you start a New Document and click Document>Add Pages From File and then select the file you can't open and click okay, are the pages then added to the blank file and are then able to work with it? If you'd like to upload the file to our Dropbox here, I'll see if I also have trouble with it and get it logged with the Developers

Hi @bigtimenobody, Do you still have a copy of the file that's crashing when saving? If so, could you upload it to our dropbox here and i'll get it logged with the Developers. Could you check and see if you have a crash report, that you could also attach? To find the report see here

Hi @MikeTO, Thanks for reporting this. I've logged this with the Developers and will make sure the other threads get added to the report

Hi @NotMyFault, Thanks for reporting this. I've been speaking with another member of staff about this and we are sure this does need changing/updating. I'm going to get this logged with the Docs team to update the help file and also ask for comment from Dev, just to confirm the correct order of things

Hi @David Battistella, I've tried to replicate this and I can't but I'm also not running 'Sync Folders Pro'. As you've been able to get a crash, would you be able to attach your crash report? To find the report, Open the Console app from Applications > Utilities. In the left hand panel click Crash Reports - you will see a list of Crash Reports. Find the relevant crash report - it should display the app's name in the Process Name column. Right click and select Reveal in Finder and then attach the report here. The report should at least tell us where or what code is causing the crash.

Hi @Larry Fjeldstrom, This isn't something I've been able to replicate here in the office on my Windows laptop. What are the full specs of your laptop?

Hi @DigitalVisuals, Can you just try a basic reset of Affinity. To do this, start Affinity while holding down the Control key on your keyboard and you'll get shown a Clear User Data screen and 3 options will be selected and you can just click on Clear. Affinity will then start as normal. Now try using a brush again, if you are still having issues, click Edit>Settings>Performance and disable hardware acceleration and close Settings. You'll get asked to restart Affinity and once restarted, try using a brush again and let me know if there's any improvements.

Hi @CM0, I've replicated the crash here on both Windows and MacOS. I've just logged this with the Developers to resolve. Any updates I get on the report, I'll be sure to update this thread

Hi @hinespraise, Try opening the attached file and let me know if that opens for you Recovered.afphoto