issicus Posted September 4 Share Posted September 4 I just updated to 2.5.5 , not sure if that's the problem, tried reinstalling 2.5.3 . havent see this before. merging layers was really slow, than saving was really slow, than it crashed both the files I had open with the same error. I have done this twice . merge selected layers, it keeps getting stuck/slow. and it's using excessive cpu. which it continues to do even after it is done merging the layers. it's slow saving. than i get the error. it's looking like some kind of scratch disk issue. memory pressure goes up to 260% and just merging the two layers uses like 5gb . than saving the file uses another 8gb or something. I tried turning of hardware acceleration , didn't make a difference. I see another forum post with this error from 2021, they mention large file size. the file I am working on is 150mb 6000px by 20000px. I attached a picture of the two layers merged as they should appear and what it looked like when I reopened the file after the crash. kind of interesting glitch, haha. and annoying. computer is intel 11700, rx6800 xt , 16gb ram , windows10 Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted September 4 Share Posted September 4 Where is your file located? Is it on a local (internal) disk drive, somewhere in the network, or a cloud service? How much space is available on your boot drive? Can you check that before running Affinity Photo, and after it starts getting slow, please? And did you install Affinity Photo using the EXE/MSI installer, or the MSIX installer. 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 17.7, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.7 Link to comment Share on other sites More sharing options...
issicus Posted September 4 Author Share Posted September 4 ive been messing with it and editing my post.. "it's looking like some kind of scratch disk issue. memory pressure goes up to 260% and just merging the two layers uses like 5gb . than saving the file uses another 8gb or something. " I used the MSIX installer. file is on second sata ssd internal. my boot drive is low on space which is the reason for the error, i figured out after messing with it. but merging two layers should not use enough cpu for my fans to kick on and use 5gbs of scratch disk. walt.farrell 1 Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted September 4 Share Posted September 4 What you're calling a "scratch disk" is a file that will be on your boot drive, which is probably part of your problem. As you're using the MSIX installer, the files are all in %userprofile%\.affinity and by default and design Windows puts %userprofile% on the boot drive. It's not recommended that you move %userprofile%, but you can move %userprofile%\.affinity and that may help avoid your problem. I've posted about this before, and gave a recipe for doing it for the MSIX installs for V2, here: I have no idea why the merge process requires so much space. 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 17.7, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.7 Link to comment Share on other sites More sharing options...
issicus Posted September 4 Author Share Posted September 4 Thanks. nice workaround for the lack of scratch disk option. That helps, not really with this problem though. now it's doing something new. I can get the layers to merge but then it get pixelated .. see attached. well I uploaded the file, if you want to mess with it. My computer is probably the problem. how to repeat: open "kids shirt" group. ctrl click to select the two 'black' layers right click merge selected than merge the other two layers that arent labeled . .sample sample - Copy.afphoto Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted September 4 Share Posted September 4 59 minutes ago, issicus said: I can get the layers to merge but then it get pixelated .. see attached. I think that is usually an indication that your pixel layers are either: not aligned to the document's pixel grid (i.e., mispositioned so they are not on an integer pixel x/y coordinates); or not using the document's DPI. I'll take a look at the file. Thanks. 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 17.7, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.7 Link to comment Share on other sites More sharing options...
issicus Posted September 4 Author Share Posted September 4 Well the pixelation went away after awhile. I guess it wasn't rendering properly when I zoomed in . Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted September 4 Share Posted September 4 That's good. But to my earlier points: The pixel layers (labeled Black in the Kids shirt group) are not on proper pixel boundaries. Note the fractional X/Y pixels in the Transform panel: Additionally, your document DPI is 95: But if we look at your file using Publisher, and convert those pixel layers to Image Resources (Layer > Convert to image resource) we can see that the DPI of those two pixel layers is different from the document DPI and from each other: I think both of those (pixel grid misalignment, DPI) will cause issues if you Merge the layers. I would right-click each of those layers in the Layers panel and Rasterize before doing the Merge. 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 17.7, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.7 Link to comment Share on other sites More sharing options...
issicus Posted September 4 Author Share Posted September 4 yup. that's the problem. It should ask if I want the layers rasterized before merging. or indicate somehow that the layer is 'live' or what ever they are calling this feature. well thanks . I was about to go back to using photoshop. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted September 4 Share Posted September 4 You're welcome. 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 17.7, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.7 Link to comment Share on other sites More sharing options...
issicus Posted September 19 Author Share Posted September 19 Hey affinity team, did you guys fix this because it's really a game breaking bug. If a new user encounters this thing you WILL lose users. I like writing "bug" lists if you want more. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted September 19 Share Posted September 19 4 hours ago, issicus said: did you guys fix this because it's really a game breaking bug. Which problem are you asking about? You've discussed at least two in this topic? (And the Serif team has not been involved in this discussion yet; so far it's just between us users.) 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 17.7, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.7 Link to comment Share on other sites More sharing options...
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.