NathanC

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.

Hi @JrCustomTs, As Mike mentioned the file is not recoverable by any standard methods available to us, so it will need logging with the developers for further investigation into what's caused this issue. It's possible that the team may be able to recover your file, but this isn't guaranteed or something we're able to provide a timeframe for. If you could answer the questions in the FAQ below to the best of your knowledge we can then get this logged: Thanks

Hi @Mercury, The issue you've described appears to be a little different to the OP's reported (crash on file open). This PDF dictionary crashing issue has actually been fixed in the current 2.6.2 beta if you'd like to give the beta apps a try. I've linked the fix list below, which includes this issue (AF-5978). ---- Thanks @DOYOON, Could you also advise on my other questions? Referenced below.

Hi @Alex_M, I've replicated and logged this issue with the developers, thanks for you report. Since it is a regression over 2.5.7, rolling back would be the advisable option until this issue is resolved if you need this functionality.

Many thanks @design punch I've confirmed this is a regression and logged this issue with the developers for further investigation.

Hi @Actonbooks, These 'ghost' indexes are indeed a bug/unexpected behaviour, but I'm limited as to what I can log internally as we haven't been identify what the trigger is to create these in the first place, but rather only use a method to delete them after they appear. Is this a different document as to what you've previously sent me via PM or in previous threads? Seemingly the only correlation i've found is that once it's happened in a document, it's more likely to continue to appear again in that specific file, which, while not ideal may mean leaving generating the index as the very last step. For reference this is the method used to remove them once they appear: Delete the Original (real) document Index by clearing out the index text frame Open the ‘Index’ and ‘Find and Replace’ panels, it helps to have them side by side for this In the Index panel ‘Between Items’ field enter the following symbol: ± and then press Tab to commit the change Paste the ± symbol into the ‘Find’ field in the Find and Replace panel and press Find Click into the text frame it’s found and then press CTRL + A to highlight all of the rogue index text Delete all the text Press ‘Find’ again in the Find and Replace panel to confirm it’s been deleted In the ‘Index’ panel press ‘Update Index’ Repeat steps 4 onwards until all instances of rogue Indexes are deleted.

Hi @design punch, So I can confirm the issue can be replicated and is a regression over 2.5.7 I'd be grateful if you could provide the following: - A copy of your Myriad Pro Font installed on Windows - A copy of an .afpub document containing a text style affected by this mapping issue I've provided a private upload link below for the files. https://www.dropbox.com/request/MEBta4mZGURxgc5mEuxK Many thanks

Many thanks, I've mirrored your Performance settings on a Apple Silicon device running MacOS 15.3.1 but I still can't seem to replicate what's shown in the recording using your file so it may be isolated to specific devices or environment related. I'll try on a few different devices just to be sure. I'd suggest disabling Metal Compute Acceleration and set the 'Display' dropdown to 'OpenGL' and then restart the app when prompted to and see if this issue triggers again. This is just to confirm if this is related to an issue with Metal, you're then free to change it back after.

Hi @joe_l, You are correct, it was possible to change via the styling shortcuts in 2.5.7 and earlier with the Milo OT font, so I've logged this with the developers as a regression.