Dan C

Just to confirm, I requested a copy of your file in order to check the X & Y / H & W positionings of the layer - as mentioned above these need to be on 'whole' pixel values in order to avoid the line shown in your screenshot. If you're still having trouble after editing these layers to be on 'whole' pixel positionings, please do let me know and I can provide the link, so that I can check your file directly and offer my suggestions

Thanks for letting me know - I'm glad to hear you're back up and running and I appreciate the further information provided here, as it's helpful should other users encounter similar problems with their documents. Just to double check, is everything now working correctly/as expected for you - or are you still having trouble with a particular file?

Thanks for your feedback @Sid J! Just to confirm, I have logged the following with our development team: For Windows - The 'Add Folder' and 'Remove Folder' icons do not match macOS. I have suggested that an icon showing a Folder with a plus symbol and a Folder with a minus symbol for 'Add'/'Remove' template folders respectively would be best. The hover tooltip on the Bin icon shows 'Remove Folder'. I have suggested this should match macOS's 'Remove Template Folder' wording. When removing a template folder, no confirmation dialog is shown. I have suggested that a confirm dialog should be shown, matching the behaviour on macOS - including the below suggested improvement to the macOS button wording. For macOS - The 'Add Folder' and 'Remove Folder' icons do not match Windows. I have suggested that both OS's should use the same icons, with the above recommendation of a 'Folder +/-' icon used, respectively. When removing a template folder, the confirmation dialog button uses the incorrect wording. I have suggested that the confirmation dialog shown uses 'Remove' correctly in the wording, but 'Delete' incorrectly for the button itself. This should be 'Remove' consistently throughout. I hope this helps

However, in V2.2 the 'Add' Geometry option will no longer reset the Bounding Box, even for a Closed Curve object. This has been discussed further recently here - A feature request for a dedicated 'Reset Bounding Box' option is currently logged with our developers, under consideration for a future version

Thanks for verifying that - as you are editing using the P3 Colour Profile and then exporting to the sRGB Colour Profile, this may cause certain tones to appear differently in the exported image, especially when viewing on a 'wider colour gamut' screen such as your iPhone. If you export the image using the same P3 Colour Profile that is in use when editing, does the image appear as expected through Photos on your iPhone?

Thanks Walt, seems like this has been missed by the team- I'll get this logged with them now

Sorry to hear this @CyberAngel! Just to confirm, does the same crash occur with version 2.0, 2.1 & 2.2 - or only with version 2.2? Your Log.txt file shows that the Affinity app is currently unable to initialise your GPU for rendering, likely causing the crashing. As suggested earlier in this thread, have you tried using DDU to remove your current GPU drivers and performing a 'clean install' with new drivers directly from the manufacturers website?

Apologies, my testing for the FAQ was performed on Windows, as I had assumed the OS's would be the same in this regard (as they both use the same PDF library). In checking the above, I can confirm I'm seeing the same as you on macOS and the manual specify workaround is happening on Windows only. I'll update both the FAQ and dev report to confirm this behaviour, as it's incorrect across all apps/OS's.

Thanks for your file provided @HydroJLW! I can't see any specific issue with the layer setup to cause this to occur when using Vistaprint - as mentioned above I'm not seeing the same occur when viewing the exported SVG file in Affinity, or other applications. If this is only occurring when uploading the exported file to Vistaprint, you may want to speak with the Vistaprint support team to understand why / how their software is interpreting this SVG incorrectly. I hope this helps

I believe these unlinked attributes is By Design - as this allows each Symbol instance to have it's own transform properties, as required. If you want to resize / orientate multiple instances of your Symbol at once, you have to apply the transform to the specific layers within the Symbol, as such: 2023-10-30 14-10-30.mp4 If your symbol contains multiple layers, you may want to Group these within the Symbol, then apply the Transform to the Group layer. I hope this helps!

Many thanks for that! I can confirm I've been able to replicate this issue here, it appears as though your images have Orientation: Bottom Right set in the EXIF data, causing this issue when using New Stack - interestingly this doesn't occur with a HDR or Focus Merge. I'm logging this with our developers as a bug now, to be resolved in a future update. I hope this helps

I assume this is a reference to 'Thread Starter', also sometimes called 'OP' (Original Poster)

Thanks for confirming that for me - if this is only occurring when viewing the image in Apple Photos, it may be due to the Colour Profile that you're using within Affinity, or your Windows colour profile applied to your PC monitor. I understand you are using RGB/8, but which Colour Profile appears in the context toolbar for this document please?

Unfortunately as I mentioned above, we believe this issue may currently caused by the macOS Sonoma update, though our team are still investigating this further internally as Patrick has confirmed. At this time, I believe the only known 'workarounds' are to leave the file loading for as long as it takes on the first load, however subsequent loads may then be faster. You may also want to try moving the Affinity file (and any linked content) to a non-cloud synced location and pause any iCloud syncing on your mac, as some users have also found this improves loading times for these specific files. I'm not aware of other options currently to change or fix this behaviour within Affinity, as it appears to be specifically related to macOS Sonoma - our apologies.

Hi @j-cat, Welcome to the Affinity Forums Sorry to hear you're having trouble! Can you please attach a copy of your Affinity document here so that I can investigate further? If you'd like a private upload link for this file, please don't hesitate to ask! Many thanks in advance!

Thanks for providing these for me! I have stacked these here and the images appear in the correct orientation - This is likely due to the Forums changing the metadata in the image when they were uploaded. As mentioned previously, could you please ZIP these images into a folder, then provide this ZIP folder here? This will ensure the metadata of the image remains unchanged, so that I can replicate the reported issue

As Patrick confirmed here - Essentially there is a post from 'Serif Info Bot' in this thread, but not one you can see - our team are still investigating the cause of the Bot name appearing in Notification lists, as this isn't expected behaviour. As these are off the shelf forums I would not expect this to change any time soon, as we only update the forums occasionally.

I'm sorry to hear this hasn't helped! I personally use a very similar setup with an ASUS ROG PG278Q (though this is only 1440p) without said flickering occurring, so I don't believe this to be an incompatibility issue with your monitor. As above, I'd recommend performing this 'clean install' with the Nvidia driver, as this can resolve unexplainable GPU behaviours. If this still doesn't help, you can use the same section of the Nvidia Control Panel to limit the framerate of the Affinity apps. If you set this to 60hz, does the flickering stop please?

Welcome to the Affinity Forums @Daniel Boros & sorry to see you're having trouble! The error message you've shown certainly seems to align with the secondary users report of this issue on macOS Sonoma, though I note you're using Big Sur. Currently, I've been unable to replicate this issue internally - can you please confirm for me: How are you trying to open the .aftemplate file? Are you using File > Open, drag and dropping from Finder, or are you using the Template section of the File > New dialog? If you move the .aftemplate file to a different location (ie your Downloads folder), do you see the same error? If you download the attached .aftemplate file that I have just created, does this work as expected, or show the same error? Is your Desktop (and other locations on your mac) being synced via iCloud, or similar? Many thanks in advance test pixel.aftemplate

No problem at all, I'm happy to help

Hi @nick l, Thanks for your report and our apologies for the delayed response here! I just wanted to inform you that I have escalated this issue internally and our team are investigating this further. I will be sure to respond here as soon as possible with our findings. Many thanks for your continued patience and understanding

This would be a good addition to the OPs Feature Request post here - An Artboard in Affinity Designer is essentially just a Rectangle with layers nested inside - meaning you can already use the Vector Flood Tool on an Artboard. However I have noticed that the created layer is not correctly nested within the Artboard when using this workflow, which I'm logging with our team now. To be clear, the current expected behaviour of the Vector Flood Fill Tool on a regular canvas background is to perform no 'Fill' action and therefore the above Feedback post is valid for consideration. However I believe the Vector Flood Fool Tool should work with an Artboard background, though this currently is somewhat incorrect in the layer placement for the generated Curve object, which I've reported to our devs

Welcome to the Affinity Forums @Bruce Adams As above, 2.2.1 is the latest official release from the Affinity team - can you please confirm for me which exact 'Affinity page' you are referring to that only shows 2.2.0? As I'd like to have our web-team update this where possible. Many thanks in advance!

The Status Bar aka Hint Line can become hidden if you use the 'Toggle UI' option (shortcut key TAB) once, then manually reenable the view/studio options. To return the Status Bar, simply use the View > Toggle UI (or TAB key shortcut) twice in a row and you should see this return: 2023-10-27 13-27-32.mp4 In regards to the issue you're reporting, as Garry has mentioned this click+drag action is by design, changing the Tolerance for the Flood Fill Tool as you move the cursor. I hope this clears things up

Absolutely, I raised this with Patrick recently and I believe his team (who have designed the new 'Serif Info Bot' system) are currently considering the best options for this process going forward - to keep visibility of such reports as clear to our users as possible