NathanC

Welcome to the forums @Chris Stotesbury, There is a known issue with JPEGXL triggering an app crash at 'Larger' document sizes on some devices, could you provide a copy of your document where you experienced this crash so we can confirm? Many thanks

Welcome to the forums @DZoned, I've replicated and logged this with the developers for further investigation, many thanks for providing a detailed report with samples.

Welcome to the forums @billalphabet, The Debug reveals a libraster.dll (Render) error. Is the app crashing when creating new documents as well as existing files? If so, I would recommend following the guidance in our FAQ below to ensure your Graphics drivers are fully up to date and also disable hardware acceleration before trying again.

Hi @Mayank Katrodia, This is a known bug currently logged with the developers, Shape Builder subtract mode unlinks attributes (Transform and Curves), causing the sync issues with other symbol instances. I've bumped the existing issue with your report. Comparatively, using Boolean Operations does not result in this issue.

Thanks, I've just imported your .afmacro file and the 'Document Properties' step appears to be working (re-sizes to 1500x1000px) unless it's intended to re-size to other dimensions? See my recording below. This was recorded on MacOS, but it also worked as expected on Windows. Screen Recording 2025-03-11 at 09.39.11.mp4

The appearance panel's reported stroke width is completely out of sync with the stroke properties window. To re-align them I had to expand the stroke, delete the expanded white curve and then set the stroke against the blue rectangle again. I can't reproduce this from a new shape, but this is evidently unexpected behaviour, so I'll get this logged with the developers.

Hi @Freixas, We have recently identified an issue with Macros created in versions prior to 2.6 no longer honouring the 'Document Properties' action for re-sizes. Newly created Macros are not affected by this issue. This is currently logged with the developers. If you can identify any other actions that are also affected by this feel free to send me a copy of the affected .afmacro files and we can take a look. This is a known issue that's currently logged, the option should be unavailable when no image is loaded, but it isn't. Machine Learning Inference currently uses CPU only on Windows (regardless of the setting in-app), so processing can take some time depending on the image content and hardware. Feel free to post on the feedback section of the forums if a cancel button something you'd like to see implemented. Are you using the MSIX(x64) or MSI/EXE(x64) version of the app? For these, I'd recommend just re-installing the app again, as I believe the help .dll files are kept in the install folder. If the issue persists try switching over to the alternative install method for all three apps.

Hi @LEB, I've copied your stroke setup and attempted to replicate it following your steps, but to my surprise, the stroke width property pastes as expected. Could I get a copy of your file so I can confirm if I've missed anything? It can be a stripped-down version of your doc containing only these two strokes, or any other file where it occurs. Many thanks

Hi @StevenRCE0, I've logged this with the developers, thanks for your report.👍

Welcome to the forums @Catalyst Creative, I've not been able to replicate a crash using this filter so far, so we'd be grateful if you could answer and provide the following: Are you using the live or destructive version of the filter? What happens if you try the alternate version? Can you provide a copy of a file where you encounter the crash when applying the filter? Can you provide a recent crash report following the application of this filter? I'd also suggest disabling Hardware Acceleration under the app settings -> Performance and then restart the app when prompted to to confirm if the issue persists. Thanks

Welcome to the forums @PKam, I've confirmed this issue is a regression over 2.5.7 and logged it with the developers, thanks for your report.

Welcome to the forums @Kyuhun, You may be experiencing a known issue with a Missing dictionary preflight error triggering a crash when exporting to PDF. This issue has been fixed in the current 2.6.2 beta, so I'd recommend signing up from the link below and then exporting via the beta apps. These install alongside the release version as a separate set of apps. https://affinity.serif.com/en-gb/affinity-beta-program/

Welcome to the forums @SkyKid, This is a known issue with expanded stroke currently logged with the developers, I've bumped the existing issue with your report.

Welcome to the forums @C ANDERSON and apologies for the late response, 2.6 has been officially released, if you could provide us with as much information as possible on your issue with tables and provide a sample document where you've encountered this we can look into the issue further. Similarly, if you've found a set of actions while working within the app which results in a crash, please provide us with more information and any necessary steps taken. Many thanks

Hi @parusdesign, This is a known issue with guides that has been fixed in the current 2.6.2 beta apps, if you'd like to try the beta apps feel free to sign up below to get started. https://affinity.serif.com/en-gb/affinity-beta-program/

Hi @BOTA, HEIC files shot on devices running iOS 18 or later will not open in the Affinity Photo with the resulting 'Not Supported' message. This was a known issue logged in V2 that was fixed in the recent 2.6 update. However, since you're running Photo V1 unfortunately this fix does not apply, and since the V1 apps no longer receive product updates, it's unlikely this will be retrospectively fixed. Changing the Camera setting on the iPhone device to 'Most Compatible' should resolve this for any future shots taken, but any existing HEIC files will no longer open in V1. You may be able to find a converter online which can convert existing HEICS these over to JPEG.

Hi @plennon, I've followed your steps verbatim and i'm able to launch the Mask context menu from the layers panel as expected via a right click, as far as i'm aware this hasn't been intentionally changed. These mask options can also be found under Layer -> New Live Mask Layer as an alternative route. I can see you've reported this under Windows, but it's worth noting on MacOS accessing the quick mask context menu is different, it requires OPT + Left click to open.

Hi @Ben_Vandebrug I've now logged this kerning issue with the developers, thanks for your report and thanks @kenmcd for the additional working samples and demo file.

This has now been logged internally with the developers, though I'm not able to re-produce any issue with Unsharp Mask (Live or non-live) as this step still appears to be functioning as expected in 2.6. Re-creating the Macro will allow the re-size to function again.

Hi @hunter_sk, Can confirm i've replicated this issue, so I'll get this logged with the developers, thanks for your report.

Bienvenido a los foros @Tsunade Puedo confirmar que puedo reproducir el problema que se muestra con cualquier filtro de desenfoque activo en su documento en varios escritorios de Windows, todos con diferentes tarjetas gráficas y controladores. Registraré esto con los desarrolladores para una investigación más profunda. La única solución alternativa que puedo recomendar en este momento es mantener la calidad de visualización en el vecino más cercano, ya que esto parece mitigar el problema de representación de desenfoque en este archivo.

Hi @Saro, If I've followed correctly, pre-export to TIFF/PNG you could highlight your text and vector elements and then Set Anti-Aliasing 'Force Off' in the Layers Panel 'Blend Options' menu and then export again, does this then preserve the hard edges of these objects? Blend Options can be found under the Cog wheel button in the layers panel.

No worries, just wanted to rule it out. If the issue with the cursor changing displayed in your initial recording was on the same file you sent me on the other thread, it's a similar situation, I can't replicate this behaviour on my device so there must be something user environment specific causing this.

Hey @Maxdanger, Based on the other unusual UI draw issue you reported in this thread below, just wondering if you were to repeat this test with Metal compute Acceleration disabled and OpenGL set as the Display setting in Settings -> Performance, does this issue also disappear?

No news to share, but this thread is tagged with the issue reference so if there are any updates the affinity info bot will automatically reply.