Dan C

Thanks for your report @typotaurus! As confirmed above, this is a bug logged with our development team - I'll be sure to 'bump' this now to bring it to our teams attention once again

No problem at all, I certainly understand! To confirm, I have logged your .afmacros file with our development team a a bug, including all the info here - as they may be able to pinpoint the cause of this issue in the apps code without your source files. I hope this helps

@MikeTO, @pbasdf @thomaso & @Hangman Please note I have split the recent replies to this thread as a separate thread here, as I believe this requires further investigations, separate from that initial report. You may want to 'Follow' this new thread to be notified of replies here. In regards to the issues being raised, I will do some further tests/investigations and reply here ASAP with my findings

Welcome to the Affinity Forums @ella.2! Unfortunately your cursor is not visible in any of your screenshots and there is no 'Mouse Tool' in the Affinity apps - so I'm a little confused by your post currently. The Move Tool in Affinity apps allows you to select objects directly on your page and uses an arrow cursor icon for the tool, similar to the regular mouse cursor outside of the Affinity apps. Can you please provide screenshots/ a screen recording with your cursor visible and a further description of the issue you're reporting here, so I can advise further? Please note if you are editing any of the Text layers shown in your document screenshot - the Affinity app will automatically switch from the Move Tool to the Artistic/Frame Text Tool during text editing. This is expected behaviour and cannot be changed at this time

Welcome to the Affinity Forums @Utz78! Please ensure View > Show Toolbar is enabled in the Affinity app to see these controls. If you're still unable to see the top menu bar, please try using Window > Zoom to return these to view. I hope this helps

¡Gracias por tu sugerencia @Antonio Lupiañez! He movido este hilo a la sección de comentarios de los foros para que nuestros desarrolladores consideren tu solicitud de una actualización futura. Espero que esto ayude.

Thanks for your report @TroyTroy22! I can confirm this issue is logged with our development team as we're aware the 'rotation handle' can occasionally obscure these values incorrectly. I've 'bumped' this report with our team for you now to bring it to our teams attention once again

Thanks for all the further information / documents provided here - I've collated this and included it with our development reports now

Thanks for your report @cgidesign! As @NotMyFault outlines, these Live Filters unfortunately don't work on values outside of the SD 0 - 1 range, however it is not explicitly clear to our team whether this is a hard limitation of the filters, if this is something we don't support currently & hope to in the future, or if this is classed as a bug to be resolved. Therefore I have logged this with our dev team for further investigation & I'll be sure to update this thread with any information I'm provided. I can verify this is logged separately with our team, though as you've mentioned the current algorithms are more suited to 'natural' image noise, rather than noise added in post. I hope this helps

Hi @Bill Carter, Welcome to the Affinity Forums & our sincerest apologies for the delayed response here as our team are exceptionally busy due to our current 50% sale & extended trial offer. In regards to Photoshop 'actions', you might want to check out Macros in Affinity Photo - as these allow you to record and replay a set of actions which may help speed up this workflow for you: However in regards to your specific workflow, unfortunately it's not possible to Mask FX only and not affect the pixel content - or have FX applied to a separate layer affecting the layer beneath, again without masking the pixel content also, our apologies. Using your sample file, the only way I've been able to achieve this effect in Affinity is by using a duplicated version of the pixel layer. You can condense the layer setup slightly, but as shown 2 pixel layers are still required: 2024-08-02 14-42-58.mp4 I hope this clears things up!

Hi @Leonide Principe, Thanks for your report & our apologies for the delayed response here as our team are exceptionally busy due to our current 50% sale & extended trial offer. From your crash report provided, it appears as though this may be due to a specific hyperlink in your exported file, though unfortunately this is not 100% clear. Therefore I'd like to request a copy of this file to investigate further - can you please upload a copy of your .afbook and all .afpub chapters to the below link for me? https://www.dropbox.com/request/TOj6YNynJ2rxo5QOwl0x I don't require your linked resources at this time, as I am hoping to find the issue without these, but I will be sure to request these separately if required. Once uploaded, please reply here to let me know

Tut mir leid, dass Sie Probleme haben, @Dirk_Vau! Können Sie bitte eine Beispieldatei bereitstellen, in der dies auftritt, da ich derzeit Probleme habe, Ihr Setup zu replizieren. Ihr Screenshot zeigt, dass Sie ein Objekt ausgewählt haben, anscheinend mit dem Knotenwerkzeug in Ihrem ersten Beitrag – zur Bestätigung: Können Sie das doppelte oder das ursprüngliche Objekt nicht auswählen? Vielen Dank im Voraus

Hi @No Papertrail! Welcome to the Affinity Forums & our sincerest apologies for the delayed response here as our team are exceptionally busy due to our current 50% sale & extended trial offer. I can confirm that you can simply enter your Affinity ID details used to originally claim the trial in this dialog and you should find the app detects this in-progress trial and continues with the amount of remaining days as expected. I hope this helps

There appears to be a few issues being reported in this thread and it's getting a little tricky to follow. 'Filled' a characters on export I have been unable to replicate this using Palatino Linotype on Windows as kenmcd outlines. Also as mentioned, Affinity does not officially support the Apple AAT fonts, so we'd recommend using a TTF/OTF version where possible. However we'd expect Affinity on macOS to better handle text using this font, therefore I'm logging a macOS specific issue with our team for this font now. 'Pseudo-shadow' 3D effect I'm able to replicate this using both Inside and Outside align stroke, however this does not seem specific to this font as I can see the same occur with Arial on Windows - therefore I'm logging this as a suite-wide bug on all platforms. Separate/offset fill & outline Again, I can replicate this using Arial on Windows with the characters used in the document with all Stroke options, less 'Centre Aligned'; I believe this and the 'pseudo-shadow' effect are essentially the same bug, so I will be including this info within the aforementioned development report. If there are further issues than this to report, please do so in a new thread, rather than here as this is easier for our team to investigate and log with our devs. Many thanks in advance

Thanks for your report @caze! Although 'Scale with object' is unticked in the Stroke Studio, you have Scale Override enabled in the Transform Studio, and as the name suggests this will override any other scaling (or non-scaling) properties set; Transform Panel- Affinity helpfile. Disabling this Scale Override option should allow you to resize your object as required, without scaling the stroke: 2024-08-02 10-42-17.mp4 I hope this helps

There are different purchase options for Affinity, all of which I can confirm are still discounted by 50%, until August 15th. Universal License - All 3 Affinity apps on 3 platforms (Windows, macOS & iPad) Individual desktop apps - One Affinity desktop app, on one platform (ie Photo on macOS, Designer on Windows) Affinity Collection for iPad - All 3 Affinity iPad apps on iPadOS Individual iPad apps - One Affinity iPad app on iPadOS (please note the iPadOS collection/apps are only available to purchase from the iPad App Store, as an 'in app purchase') You can find these listed at the below link with the current prices: https://affinity.serif.com/affinity-pricing/ However for V1 users, we also offer a V2 upgrade discount path for a Universal License purchase, which is also 50% off currently, you can find this offer here: https://affinity.serif.com/store/upgrade-offer/ I hope this clears things up

No problem at all, thanks for providing those for me - they now contain the expected information! I can see the GPU driver that Affinity is enumerating in the Log file is from November 2022, which could certainly explain these slowdowns in Affinity for you, as the number one cause of rendering issues in Affinity are due to outdated GPU drivers. Therefore, I'd like to suggest performing a complete removal of all drivers, followed by a reinstall of the latest AMD drivers for your device. Can you please download DDU from the below link: https://www.wagnardsoft.com/forums/viewtopic.php?t=4992 You can then find a guide for using this tool here, where I'd recommend the 'Clean and Restart' option: https://www.wagnardsoft.com/content/How-use-Display-Driver-Uninstaller-DDU-Guide-Tutorial This will remove all of your current and previous GPU drivers from your system. After the restart please download & install the latest AMD drivers from the below link: https://drivers.amd.com/drivers/whql-amd-software-adrenalin-edition-24.7.1-win10-win11-july19-vega-polaris.exe After installation, restart your PC once more, then try editing in Affinity once again. Does this improve the performance for you please?

Thanks for providing your file @1trapshell! When recording a Macro using the 'Place' functionality, I'm not aware of any way to modify the file, or file path used within the macro at a later date. If you export this macro to a different machine or moved those placed resources on your disk, I believe the macro has to be re-recorded. However checking the file you've provided shows that your macro uses 'Paste' and not 'Place' which is a different function saved differently in the macro itself. Running this macro adds an embedded PNG Image layer @ 80% opacity and shouldn't be dependant on the machine the macro is run on, or the presence of the originally copied layer - as far as I'm aware. What is interesting about this behaviour, is the file added by the macro cannot be seen directly on the canvas, but does show in the Navigator Studio, which isn't something I've seen occurring previously: Therefore I suspect this issue is related to either the specific image used when recording, or the exact steps you took when making this macro, which is causing it to fail on other machines - rather than a change of file paths etc. Can you please provide a copy of the PNG file that the macro is attempting to paste, and also confirm the exact steps you took in Affinity to record this macro. For example, did you do something similar to the following?; Use File>Place to introduce the image into your document as an Embedded resource Set the opacity to 80% Copy the resource In a different file, began macro recording Pasted the reosurce Stopped & saved the macro The more information regarding the exact workflow used to record this macro can help our team further. Many thanks in advance!

Thanks for the file provided @Anthony R! The 'skull biting pin' file has an active Pixel Selection over Artboard 2: You can remove this 'marching ants' selection using Select > Deselect. The reason you cannot select this layer directly on your Artboards is due to the layer being Locked in the Layers Studio. Select this layer and click the padlock icon to unlock the layer - you'll now be able to select and move this layer as required: Finally, I can see your design actually has 3 Artboards present, with Artboard 1 duplicated and moved over Artboard 2 on the left. 'Stacking' Artboard like this is not recommended as it can cause issues when moving objects etc. I'd recommend condensing the objects from the duplicated Artboard 1 to Artboard 2. I've attached a copy of your file below where I've followed these 3 steps for you, meaning you should be able to continue editing as expected. skull biting pin with pins for eyes and TFP_E.afdesign I hope this helps

Thanks for verifying, but even with GPU hardware acceleration disabled, the app still has to enumerate the GPU in order to set it as the 'Renderer' in the Performance dialog

No problem at all, thanks for letting me know! If you are happy to continue to Link the files and this works for your setup then it does sound like the best option for you

Many thanks for providing this! It appears as though the app is crashing when trying to change the document view (which is expected in the context of creating a new document) however this new document view appears to an invalid value, which causes a null pointer and subsequent crash. This means the crash is likely specific to your machine and the Affinity app has saved a window value that it can no longer use - do you by chance have external/multiple monitors that you have previously connected to the device, but no longer are in use? The easiest way to try resolving this is by creating a new version of your Affinity app data, as this should hopefully not include the invalid value. To do this, please ensure the Affinity app is closed, then open Windows Run (Windows Key + R) then paste the following string and press OK, depending on the Affinity installer type you are using: Affinity Store (MSIX) & Windows Store: %USERPROFILE%\.affinity\Photo\ Affinity Store (EXE) : %appdata%\Affinity\Photo\ In the window that opens, please select the 2.0 folder, then rename this to 2.0_old and open the Affinity app. You should find that a new 2.0 folder is generated in this location, and the Affinity app is reset to default settings once launched. Now, try creating documents using File > New and File > New from Clipboard - does this stop the crashing please?

Thanks for your report & our sincerest apologies for the delayed response here as our team are exceptionally busy due to our current 50% sale & extended trial offer. I'd like to request a copy of these files for further testing, can you please upload them to the below link for me? https://www.dropbox.com/request/6kV2e56gsD4V8CnJ9RA7 Once uploaded, please reply here to let me know - many thanks in advance

Sorry to hear you're having trouble @Henriette W! The Disk Warning you're seeing means the app is using a higher value of 'storage space' on your macs drive, that you have set in the Affinitys app preferences. For example, if you set the Affinity Disk Warning value to 32768MB, the app will only warn you once it has used more than this value. The Affinity apps use this 'storage space' on your machine once the memory (RAM) has been used - this can be used by the Affinity app, as well as macOS and any other apps running on your system. Can you please provide a screenshot of your current settings under Affinity Publisher 2 > Settings > Performance? This sounds like there may be an issue with the Publisher document itself - as the app shouldn't crash when embedding resources. Does this crash (& disk warning) only happen with this file, or do you see this happen with other documents please?

Sorry to hear you're having trouble @Bryce! I've tried to replicate this issue in multiple Artboard documents (some with only one artboard, some with multiple, starting on a regular canvas and converting to an artboard etc) and in all tests the guides have remained both visible, and listed in the Guides Manager. Are you able to provide a screen recording showing the exact steps you're taking when this occurs? Many thanks in advance