peseoane

@Lee D I had two saved editions of the file (in the snapshoots tab). Switching between them, I have not managed to reproduce the failure now, but it has happened to me more times (in case it happens again I will try to save it)., when you have a file with: - You have SVG and/or EPS elements, this triggers RAM usage. - Many Affinity tabs open (never the same file open at the same time by two programs of the suite respecting the lock). When switching versions, if you delete the unwanted version, sometimes the canvas under the container disengages and floats and loses the "Title bar" where you are supossed to grab and drag back to the main container. Not always. It has never happened to me in documents without SVGs or EPS. I am a developer (of other kind of software but maybe i could be helpful here), the only useful thing I can tell you is that these bugs only happen to me when I see a high RAM usage (> 32 GB with Designer for example), my system is 64GB RAM. I have looked for you, hope this helps to debbug a bit. Exception information: System.AccessViolationException in <Module>.Kernel.Countable.Release(Kernel.Countable*) in Serif.Interop.Person.CountedPtr<DocumentController const >.Reset(DocumentController*) in Serif.Interop.Interop.Persona.CountedPtr<DocumentController const >.Dispose(Boolean) it could be some broken pointer in the Persona class with high RAM usage caused by something causing SVGs and invading the memory space pointed to by Interop.Persona.CountedPtr...? You will know better than me! Again, i'm sorry to not be able to provide a better trace of the bug for you right know. Best,

Good afternoon. I have noticed a small bug, which, although random, can be forced further by using under the "versioning/snapshoot" panel a particular version, reversing backwards towards the oldest version and deleting other for example, it sometimes triggers this canvas without the top control bar. On some of these occasions, the canvas is disengaged from the mainWindow but the window controls do not show to reset it. I attach a video with the bug. I'm using the Affinity default driver, not WARP, with a 3060ti on Windows 11 (all up to date, Affinity Versións are 2.1.1). Grabación 2023-07-13 074152.mp4

Thank you. Now i'm ussing as you suggested WARP rendering and is more or less the same. Look at the slider for highlights (down right). The corruption is different, now is on the sliders an app canvas, the photo area has glitches but they dissapear randomly.

Thank you! But, this is not a "aceptable" solution. Let me explain I paid for Affinity because unlike other alternatives it promises up to 60 fps average in simple scenes, it comes in giant in advertising. With Illustrator or Photoshop I have no problem. By the way, disabling it still makes the artifart be there the same way, since Windows 11 offloads CPU per GPU even if you disable Direct3D.

EDIT: * The format i was editing is TIFF16 with LZW compression. Is not a DNG or RAW. While editing a photo, everything is fine but they stop appearing when I zoom in and out, move or apply a brush to areas of the image. However, they remain recognisable by affinity for automatic tracing and adjustments, they are simply not displayed on the screen. When the document is exported, the destruction is still there. If I convert to .psd and open in Phtoshop it comes out fine. i5 12th with 16 GB RAM and Intel Xe 98 CE using graphics accelerator. Latest DHC drivers. Windows 11. When you export, the data gargabe still there. But if you export from PSD and later in photoshop you export to PNG the file it's fine This is a representantion of what happend during the edit, just zooming and panning creates the issue.