RedSnapper Posted February 25, 2023 Posted February 25, 2023 I Open a raw file in Develop Persona and go to Overlays. Show Edge is Off, Show Overlay is Off, Show all layers is ON. I paint the Overlay. The Overlay is shown in RED. It shows regardless if the Show Overlay box is ticked or not. Sometimes painting the overlay and showing the overlay is not instant. There is often a delay. I then now go to Basic or any other Tab and Affinity Photo closes. It only closes after I have painted the overlay. When I launch Photo again the delay in painting the overlay and it showing is reduced and is often instant. Quote
walt.farrell Posted February 25, 2023 Posted February 25, 2023 The crash (at least) is probably a known issue: https://forum.affinity.serif.com/index.php?/search/&tags=AFP-5990 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Ron P. Posted March 1, 2023 Posted March 1, 2023 FWIW, on Windows10, Beta 1714, it still causes a crash. Quote Affinity Photo 2.5..; Affinity Designer 2.5..; Affinity Publisher 2.5..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD
walt.farrell Posted March 1, 2023 Posted March 1, 2023 1 hour ago, Ron P. said: FWIW, on Windows10, Beta 1714, it still causes a crash. To be expected, I think, as it's not marked as fixed in .1713/.1714 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Staff Chris B Posted March 8, 2023 Staff Posted March 8, 2023 This is fixed in 1720 but this is just inernal. So you should hopefully get a build soon with said fix. Ron P. and _Th 1 1 Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
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.