PhilipPeake Posted November 11, 2022 Posted November 11, 2022 Platform: MacOS 12.6, Apple M1 Max processor, 32 GB memory. To reproduce: Open an image (stock image is fine). Add live adjustment layer - exposure. Add live mask layer (Luminosity). All works fine to this point, changing mask and exposure. Now, try sliding mask layer down (click, drag downwards, blue line appears between exposure and base levels). Result - crash. Reproducible. Every time. crash-report.txt Quote
NotMyFault Posted November 12, 2022 Posted November 12, 2022 Seems it only works correctly on pixel layers. rasterize image layers before using live masks. Quote Mac mini M1 A2348 | MBP M3 Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.
_qua Posted November 13, 2022 Posted November 13, 2022 (edited) I also experienced this crash on Windows 11, Intel i7, 16 GB RAM, Affinity Photo 2. Luminosity mask works on a pixel layer but crashes otherwise. Would be nice if Affinity caught the error rather than crashing. Edited November 13, 2022 by _qua Quote
PhilipPeake Posted November 13, 2022 Author Posted November 13, 2022 The crash on the Mac is not trying to apply it to a non-pixel layer (didn't try that) bu trying to move the sub-layer to a top-level layer. Quote
Staff Affinity Info Bot Posted January 26, 2024 Staff Posted January 26, 2024 The issue "Drag-dropping a masked child layer out to the parent stack without releasing the mouse button causes a crash" (REF: AF-977) has been fixed by the developers in internal build "2.4.0.2252". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.