Dan C

Hi @_Amageton_, Thanks for your report! I can confirm that the behaviour shown in your screen recording is expected - it's not possible to 'drag' a guide back into the Ruler in Affinity on Desktop or iPad, therefore in your recording when the guide moves, this is because it is simply being dragged to a different section of your canvas / artboard. However, it should be possible to drag and drop a guide outside of the canvas / artboard area in order for the guide to be removed. This does work correctly on desktop currently, but is unfortunately a known issue on iPad, where the guide will remain present and visible, even when dragged off canvas. Desktop - 2024-04-02 16-02-40.mp4 iPad - RPReplay_Final1712070290.MP4 I'll be sure to 'bump' this guide drag off-canvas issue with our team now, in the meantime if you select your guide line, you can use the Delete icon in the top right of the Guides manager options to remove the guide.

Thanks for your report @_Amageton_! As Walt has confirmed above, this is a known issue which is logged with our development team currently - I'll be sure to 'bump' this with our team now to bring it to their attention once again. Our apologies for any inconveniences caused due to this, as mentioned you should be able to use the On Screen Keyboard to workaround this issue in the meantime

Hi @JesseR, Welcome to the Affinity Forums & thanks for your report! I can confirm this is a known issue in Affinity V1 on macOS Sonoma - unfortunately with the Sonoma update, Apple broke the “pull down” variant of NSPopupButton, which the Affinity apps use for this dropdown functionality. This issue with the NSPopupButton was reported to Apple when our team discovered the issue, but unfortunately has not yet been resolved within an update to Sonoma. I have informed our development team that this issue still exists within Affinity V1 and requested to re-inform Apple, in the hope they will have this resolved shortly. Affinity V2 apps use a different variation of NSPopupButton, meaning this does not occur in Sonoma for the latest V2 updates of Affinity, however I do understand this does not change the behaviour you experience in V1. Please accept our sincerest apologies for any inconveniences caused due to this, as unfortunately I'm not aware of any workarounds for this at this time.

You're very welcome, thanks for letting me know this has resolved your issue

Sorry to hear you're having trouble with your document @ubercool - we can certainly take a look to see if this file is recoverable, although unfortunately we cannot make any guarantees. Please upload your document to the below link for me, and once uploaded please reply here to let me know. https://www.dropbox.com/request/HBSt6yqT83D0zmhc3ex0 We would obviously also like some additional information to see if we can work out the cause of the problem and stop it happening in future. To assist this process, as well as uploading your file, please can you also tell us the following: Which Operating System are you using? Which version of Affinity did the file last get saved in? (2.4.1 beta, as I understand from your post) What drive type was the file last saved to? Local disk USB disk/Flash disk Google Drive folder OneDrive folder iCloud folder Dropbox folder Network location Other (please specify) Any other information you think would help us try to find the problem? (ie did this occur when using a specific tool or workflow?) We suggest that you check to see if you have any backups of the document available in case we’re unable to recover the file. Many thanks in advance

Thanks for your report @Intuos5! I can confirm that this is a known issue which is currently logged with our team - I'll be sure to 'bump' and update this report for you now. I hope this helps

Welcome to the Affinity Forums @sjacobs2602 & sorry to hear you're having trouble! I suspect this is due to the Dell colour profile, which is likely applied to your monitor through Windows Colour Management settings. Please see the below FAQ for steps on how to change the profile applied to your monitor, changing this to the default sRGB profile should hopefully stop this issue from occurring - For example, these are the settings I'm using on my machine for my monitors: I hope this helps

Thanks for providing that - I'd like to update the development log for this issue with some further details, as I can see it has been previously marked as 'fixed' by our team, but subsequently reopened with newer reports. Just to confirm: What iPadOS version is in use? What iPad model are you using? Is this occurring with the V1 or V2 Apple Pencil (or a different input device altogether?)

In my personal testing, I can see an occasional issue at the start of the stroke, only when using full pen pressure on the screen. If I use a light or medium amount of pressure at the start, during or near the end of the stroke, I don't see any issue at the end of the stroke - RPReplay_Final1712061322.mp4 This is using the Vector Brush Tool at 8pt, with the 'Solid Pen with Pressure' brush, edited to be 100% size variance based on Pressure. Is this the issue you are referring to in V2? As this is technically a different issue that the one reported above, based on the location of the 'flick' / 'blob' in the stroke.

Hi @wogh123, Welcome to the Affinity Forums & thanks for your report! I can confirm this issue is known to our team and has been marked internally as resolved for update v2.5 - which we hope to make available via our beta program shortly. I hope this helps

Hi @Corina Nika, Thanks for your post and our apologies for the delayed response here! As I understand it, Affinity Designer V2 contains multiple fixes / improvements when using Brush Tools and a pressure based controller with an Apple Pencil - in order to stop this from occurring. Although some improvements were made to Designer V1, you may find this still happens in certain situations, especially when using smaller line widths. Have you tried the free trial of Affinity Designer V2 on iPad, to see if the same issue is present on your device with these settings?

My sincerest apologies for the delayed response here - I cannot be certain for the exact reason but it appears as though I missed the notification for your original reply here. This is my mistake and can sometimes occur during busy periods, though I will certainly work to ensure this does not happen again in the future. I've opened the .afpackage with your fonts/images provided in 2.4.1 on both macOS and Windows - on both platforms the document was opened and displayed as expected, with all fonts showing correctly within the Font Manager and no 'Open Document Package' toast is shown, as you've screenshotted above. I understand this is also working correctly on one device for you, but not on another. As below are you able to confirm any clear differences between these systems that may help us to identify the cause of this? For example does the OS version differ between devices, do you already have these fonts installed on your device where this fails? Thanks for your continued patience here

Many thanks for the files provided - my apologies for the delayed response here as I have been out of the office for annual leave. I can see from your crash reports that 'RivaTuner' is hooked into the Affinity apps, as they both use the same Direct3D libraries. This is outlined in the below post - This can cause the Affinity apps to crash, therefore we recommend either removing RivaTuner from your system if not needed, or adding the Affinity.exe, help.exe and crashreport.exe executables to be ignored, setting the 'Application detection level' to none. Once complete, restart your PC and then try using the font search/picker within Affinity again. Does this stop the crashing behaviour please?

To confirm, the search issue when using the online helpfile has since been resolved by our team and you should now find that results are provided as expected - The issue in-app on Sonoma is still currently logged with our team and should be resolved shortly

Hi @Piero Mattirolo, Welcome to the Affinity Forums & my apologies for the delayed response here, as I have been out of the office for a shot while. I have downloaded and opened this HEIC image on both Windows and macOS and I'm not seeing this crash occur currently. Can you please confirm for me: Are you using Affinity on Windows, macOS or iPadOS? Are you using Affinity V1 or V2? Under Edit > Settings > Performance (Windows) or Affinity Photo > Settings > Performance (macOS), what are your settings? A screenshot of this dialog would be appreciated to help our team investigate further. Many thanks in advance!

Welcome to the Forums @lucy dawlish! Sorry to see you're having trouble - as above our team are aware of issues with exported LUTs retaining the same colour adjustments, as present in the file before exporting. This is logged with our development team and I'll be sure to 'bump' this with them now, including the information provided in your screenshots above. I hope this helps

As other users have confirmed above, this feature is simply not directly present in Affinity currently. You can create a new Feedback post if you want these options to be considered in the future. Please do not directly tag moderators in posts like this - it will not change the response from our team, or the features currently available in the app.

As confirmed by this post - Support for the Panasonic S5 Mark II was added in update 2.4 for Affinity Photo. Please ensure you have updated to this version in order to develop RAW files from this camera. I hope this clears things up!

Apologies for the delay as I have been out of the office for a short time - I'm very glad to hear a subsequent Windows Update has resolved this issue for you both, thanks for letting me know! Unfortunately this isn't possible at this time. FAIK when opening any document type in Publisher, the app will always open this in the 'Publisher Persona', regardless of which Persona you are in currently - however I can certainly understand why this would be helpful to your workflow, so I'll be sure to raise this with our team for further considerations

Sorry to hear this hasn't helped - many thanks for the further screenshots / screen recording provided. I'd like to see if the app is generating any crash reports, as these may indicate the exact cause of this on your machine. Can you please follow the steps in the below FAQ to find these reports, and attach the latest 3 .DMP files here for me?

You're very welcome - and as echoed above in this thread we sincerely do appreciate the time and effort you take to help us continue to update and improve the apps

Thanks for your recording @GripsholmLion - unfortunately however I'm a little confused, as I'm not seeing the same issue in your recording as shown by OP. In OPs recording, the cursor position (ie brush outline) is shown where the 'pick' was initiated, even though this is not where the cursor currently is, after 'picking' the colour. It's hard to tell from your recording as this doesn't seem to capture the full colour picker loupe, but I'm not seeing this occur on your machine. I've watched the recording multiple times and unfortunately I'm unsure exactly what you're trying to show. As we've been unable to replicate OPs originally reported issue, and I'm not entirely certain what is shown in your recording, I'd recommend creating a new thread if you need to report a bug that you can replicate on your machine

Many thanks for providing that for me and my apologies for the delayed response! Can you please also try updating your GPU drivers directly from Nvidias website (https://www.nvidia.co.uk/Download/index.aspx), then restart your system after installing and let me know if this continues? The app will currently prompt if you would like to restart after changing such settings - however there is a known issue whereby the app can actually crash silently during the restart, meaning the app closes but fails to automatically reopen, this is logged with our devs as a bug to be resolved ASAP Sorry to hear this! Just to confirm, @grunnvms & @DicownedHawk - are you referring to the Selection Tool cursor issue shown in the OPs recording, or the app failing to restart after changing Performance settings issue?

The Affinity website provides an upgrade offer for the Universal License only - if you were a V1 license holder. There is no upgrade offer path for a singular V2 app. However you are still upgrading from V1 to V2 when purchasing any V2 license after owning V1, as that is the definition of the word upgrade in context of computer applications and versioning. OP already confirmed they own Designer V1, which I can see is linked to their Affinity ID; If any user purchases the Universal License for the V2 Affinity apps, they can access all 3 apps, on all 3 platforms. This is completely independent of V1 licensing. The only difference if you were a V1 user when purchasing the Universal License is the price - provided you take advantage of the upgrade offer. If you have an issue with the Affinity Licensing wording, I'd recommend emailing affinity@serif.com.

Hi @zsh2517, Thanks for your report! I can confirm the issue with the in-app macOS search is known to our team and should hopefully be resolved within the next update. However I can also confirm that I'm able to replicate the search issue with the online help (both in Chinese and Japanese) and therefore I'm also getting this logged with our team now. I understand the importance of this issue to users such as yourself and therefore have requested this is investigated and resolved as soon as possible. I hope this helps