Dan C

Thanks for your post @awakenedbyowls! I'm not seeing this behaviour here - when selecting the Pixel Tool in the Pixel Persona of Designer, the default fill colour (black) is applied to my strokes. Are you able to provide a screen recording showing the behaviour you're referring to please? If you navigate to the Designer Persona, then select the Move Tool. With this enabled, navigate to Edit > Defaults > Factor Reset - you should find that the Colour options are reset to the default Black/White. Now, return to the Pixel Persona, select the Pixel Tool and begin painting - you should find this uses the default Black colour to paint, as expected. 2024-04-06 12-08-09.mp4 Under Edit > Settings > Assistant, ensure the Assistant is enabled with the checkbox at the top of the dialog, then the Painting with no layers selected option needs to be set to Add new pixel layer and paint

Désolé d'apprendre que vous rencontrez des problèmes @baussaron! J'aimerais demander une copie de vos fichiers Affinity, car je ne vois pas ce problème ici actuellement. Veuillez télécharger une copie de vos fichiers .afbook et .afpub sur le lien ci-dessous pour moi - https://www.dropbox.com/request/NA5tdKsokiHBKW9u3okt Une fois téléchargé, veuillez répondre ici pour me le faire savoir. Merci d'avance

Thanks for your report @Thomas Geist! I'm getting this logged with our development team, as I'm unsure why the behaviour of the Place dialog would differ from the File > Open dialog. This is behaviour that I see in Affinity, but also in every other application I tested on macOS Sonoma. This included Pages, FontBook, Chrome, Photoshop - all of which through File > Open offer the Icon view in Finder, but do not offer a thumbnail size slider - therefore this appears to be the OS standard for Sonoma and not a bug in Affinity. I hope this helps

你好 @_考槃 感谢您的报告！ 我可以确认这个问题已被我们的开发团队记录为错误，因此我一定会立即与我们的团队“碰撞”并更新此问题，以再次引起他们的注意。 不幸的是，我们目前没有任何时间表来说明何时将中文垂直布局文本作为一项功能添加到 Affinity，但我们知道许多用户正在等待此功能，对此我们表示歉意。 我希望这有帮助

We are happy for users to have relevant and courteous discussions regarding AI tools and the ethics surrounding them here - but please do not use the Affinity Forums as a place to simply copy and paste AI transcripts and AI artwork with the accompanying prompt. If you wish to log your findings when using AI models, we ask that you do this elsewhere online as this is not what the Affinity Forums are designed for.

Sorry to hear this! We can try and resolve the issue by clearing the applications 'Recents' list. Please open Windows Run (Windows Key + R) then depending on the Affinity app you're using, paste the following string and press OK: Photo - %USERPROFILE%\.affinity\Photo\2.0\Settings\ Designer - %USERPROFILE%\.affinity\Designer\2.0\Settings\ Publisher - %USERPROFILE%\.affinity\Publisher\2.0\Settings\ In the window that opens, please select the 'RecentFiles.xml', then delete this file. Relaunch the Affinity app(s) and you should hopefully find this freeze/force close no longer occurs

Apologies for the delayed response here as I was out of the office yesterday - I can confirm that I'm seeing multiple issues with your shortcuts file, that I've yet been able to replicate from scratch. I'm in the process of attempting to repair these shortcuts, so that I can return a working .afshorts file to you that does not require a complete recreation, but this will take a little longer for me to complete, so I appreciate your continued patience here! In the meantime, can you please confirm for me, have these shortcuts perhaps been transferred to/from beta versions at any point? Is there a chance these were originally created in V2.1 or before? I ask as we're aware of a specific issue with some shortcuts between V2.1 and V2.2 and I suspect that may be related, and explain why I cannot replicate this from scratch in 2.4 currently

Hi @nickbatz, AFAIK, there is no difference with how the Affinity app itself handles RAM/memory management between Sonoma and Ventura - any differences will be made by Apple under the hood of the OS. It's expected for the Affinity apps not to relinquish control of used memory when the application is still open, provided it is not being required by other applications etc. However the app should always release any used memory once it has been fully Quit (as you've mentioned on macOS 'Close' can actually leave the application running in the background and therefore the memory may not be cleared). You can use Activity Monitor on macOS to track the hardware usage of apps, and you should find that after the Affinity app is Quit the app no longer appears within this list. Provided the app is not listed here after being quit, this confirms the Affinity app is no longer running and the Affinity code no longer has control over your macs memory. If you're finding that not all of the 'available memory' seems to be returning, but the Affinity app is not listed in the Activity Monitor, then this is out of our control and completely dependant on macOS itself. If you believe there are issues with Affinity handling certain files, can you please attach a copy of these files here for me to test further? Note if these are image files, please provide them within the .ZIP format as otherwise the upload process to the forums may change the exact behaviour experienced with the files. Many thanks in advance.

Hi @edw3cats, Thanks for your report! I can confirm I've been able to replicate this issue here and I've logged it with our development team now. I hope this helps

Hi @sdaniel693, Welcome to the Affinity Forums & our apologies for the delayed response here! HEIF files are included on the list of Affinity Photos "Full Import / Export List" and therefore I'd expect your HIF file to be compatible within Affinity and render correctly - thus I am getting this issue logged with our development team now as a bug. I will be including a copy of your .HIF file provided here with the report, but it would help our team to have a copy of the same file that does render correctly. Are you able to please attach a copy of the .JPEG or the .ARW file from your A6700 that matches this HIF provided above? Equally, I have noticed a few issues across Windows/macOS with these alternative file formats (.HEIC, .HEIF & .HIF) correctly being listed in File > Open / File > Place, therefore I'm also getting this logged separately with our team now - as I'd also expect these files to show and be selectable within these dialogs. Many thanks in advance & I hope this helps

Thanks for your post @viterzbayraku; This thread is for Affinity V1 apps, and as confirmed throughout by myself and other Affinity Forum members, this was not an issue that was replicable in V1, therefore no bugs were logged with our team. If you are truly using Affinity v2.0, then this may explain the issue you are having. Please update to the latest update, v2.4.1, as many bug fixes and improvements have been added between these versions. If you are already using Affinity V2.4.1, or continue to experience the same issue after updating to this version please create a new thread in the relevant section of the Forums (depending on if you are using Windows or macOS) with as much information as possible and a copy of your file, and our team will be happy to assist and advise further.

Thanks for the info David! I must admit I tested this in V2 macOS/Windows only - though I now recall there are known issues with certain HEIC/HEIF images in V1 that were fixed in V2, which may explain the users report

Affinity is a fully colour managed application, meaning your images will be displayed using colour profile conversion, based on your documents profile and screen profile, set in your OS. "My Pictures", assuming you're simply referring to the Folder where your images are saved and the built-in OS Image viewer is not colour managed, meaning the images are usually displayed as 8bit sRGB, regardless of the source file or your monitor settings. You can find out more about colour management in Affinity here - https://affinityspotlight.com/article/display-colour-management-in-the-affinity-apps/ https://affinity.help/photo2/English.lproj/index.html?page=pages/Clr/ClrProfiles.html&title=Colour management I hope this clears things up!

Hi @Pey, Thanks for your report and I'm sorry to hear you're having trouble. After the 'checking license configuration' stage, the Affinity app then begins checking your installed fonts, whilst continuing to load - it sounds as though the application is unable to complete this font check on your system and equally isn't changing the displayed text to confirm this step is underway, hence it appears as though the app is 'stuck' during the license configuration stage. We're not aware of any specific issues with Typeface and Affinity apps, as this has even been suggested by other users on our forums as a font manager on macOS to use with the Affinity apps. Can you please confirm for me, which exact Google fonts are you installing through Typeface? How many total fonts do you have installed through Typeface? If you install the Google Fonts from the Google Fonts site into your system, does the same loading issue occur? Many thanks in advance!

Thanks for your report @edw3cats! I've tried replicating this using all V2 documents, and a V1 document converted for use in V2 and I'm equally unable to reproduce this at this time. It's certainly possible that this is an edge case relating to your original file and should hopefully not occur again - but if you do find a consistent workflow to trigger this issue, please do let us know

Welcome to the Affinity Forums @tD4WG! Which Affinity app are you using to crop your PDF please? Is this PDF a layered document, or a singular image layer within the PDF file? Are you using File > Open to import the PDF as a new document, or File > Place to introduce it into an existing design? Many thanks in advance

Thanks for letting me know and for the files provided - I can confirm I'm seeing the same issue with your files on Windows, even without the Linked resources present. I'm unsure of the exact reason for this, as I cannot see a clear issue with your file, therefore I'm getting this logged with our development team now for further investigation and to help the app better deal with such a file in the future. I'm very glad to hear you've been able to find a workaround for this in the meantime and we certainly appreciate your patience and understanding here

Just FYI, as part of the Affinity and Canva Pledge, we have confirmed the following: As you've mentioned this is not a definitive timescale, but rest assured we're working to bring this feature to Affinity V2, ASAP

Thanks for verifying that for me - we've tested with multiple keyboard layouts and input languages here and we're still unable to replicate this issue. Can you please try either resetting your keyboard shortcuts within Affinity, or set a different function to the F1 key - then try using this again. If you reset the shortcuts, does F1 open the Helpfile as expected? If you set a different custom shortcut, does this work as expected? It's possible that another application is 'taking hold' of the shortcut, stopping the key from being detected in Affinity - for example we've seen this previously with 'CTRL+D' when TinyTake is active on a users PC.

Sorry to hear you're having trouble @doi & our sincerest apologies for the delayed response here! If you have a previous version of Affinity V1 apps still installed on your device, you may find that your documents are automatically opening within V1 - even if the document was created or saved using V2. Unfortunately the Affinity apps don't support backwards compatibility, meaning files created in V2 cannot be opened in V1, and any V1 files that have subsequently been opened and saved within V2 can no longer be returned to V1. Therefore can you please ensure you have opened the Affinity Designer 2 app directly, then use File > Open from within the app and select this file - does this now open as expected for you please? If you're still seeing this error, can you navigate to Affinity Designer 2 > About and let me know the version number that is shown? If possible, a copy of the document attached to your reply that shows this error would also be very helpful. Many thanks in advance

As confirmed above, this functionality unfortunately is not available currently in Affinity - therefore I'm moving this thread to the Feedback section of the Forums for our team to see and consider adding this in a future update

No problem at all, thanks for verifying that for me! I've provided these details to our team, alongside your screenshots to help them continue to improve this in a future update. You're very welcome, thanks for letting me know! As above I've updated this issue with our team as were always working to refine the tools in Affinity

Hi @Shelbi, Thanks for your post! As mentioned above, this option has not previously been offered in Affinity Photo - however I cannot find any specific reason for this, and I'd personally expect all 3 apps to have the same Zoom menu options (and therefore shortcut functionality) present. Therefore I'm getting this logged with our team now, to consider adding the options to the Photo Zoom menu, matching Designer & Publisher. Interestingly, this functionality is already present in Affinity Photo, as you can double click on the thumbnail of the layer to 'Zoom to Selection' - though I do understand this does not change your issue specifically related to shortcut keys. Do note also that this functionality in all Affinity apps is a 'Zoom to selected object', and not a 'Zoom to Pixel Selection'. If you have a pixel selection active in the Pixel Persona of Designer, for example, then this option will still only zoom to these selected object/layer, ignoring your 'marching ants' pixel selection. I hope this helps

Thanks for your report @Intuos5! I'm seeing the same behaviour as Walt on Windows 10, Designer 2.4.1 - with the Help shortcut set to F12 and the Cycle Selection Box set to F1, both of these shortcuts function correctly for me - 2024-04-02 17-01-19.mp4 Are you using an ENG UK/US QWERTY Keyboard layout? As a different layout may explain why we're unable to replicate this at this time

Thanks for your report @MikeTO! I can confirm this is a known issue which seems to affect many of the 'percentage' based values for Quick Shapes, such as the Inner/Hole Radius for the Cog Tool, or the Upper/Lower Lines of the Segment Tool. However this does appear to currently work as expected for ‘absolute’ values, such as the Teeth count on a Cog. I'm getting this report updated with our development team now - I hope this helps