malayali Posted March 22, 2023 Share Posted March 22, 2023 Not sure if this is a bug. I'm having a strange issue with marquee selection tool. When making a selection in this document, test.afphoto, position of selection is automatically shifting slightly. Any insight on why this is happening? Here's a screen-recording. Quote Linktree | Freebies Affinity Photo, Affinity Designer, Affinity Publisher | 1.10.6Windows 10 Home (64 bit) Version 22H2 Intel i5-6200U CPU @ 2.30 GHz (4 CPUs) | NVIDIA GeForce 940M | Intel HD Graphics 520 | 16GB RAM Link to comment Share on other sites More sharing options...
walt.farrell Posted March 22, 2023 Share Posted March 22, 2023 I believe that's a known issue if the document has Bleed assigned. In that case a pixel selection will jump up and left by the amount of the Bleed. 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...
malayali Posted March 22, 2023 Author Share Posted March 22, 2023 11 minutes ago, walt.farrell said: I believe that's a known issue if the document has Bleed assigned. In that case a pixel selection will jump up and left by the amount of the Bleed. Oh, ok. It does have bleeds. Do you know the bug reference/ID? Quote Linktree | Freebies Affinity Photo, Affinity Designer, Affinity Publisher | 1.10.6Windows 10 Home (64 bit) Version 22H2 Intel i5-6200U CPU @ 2.30 GHz (4 CPUs) | NVIDIA GeForce 940M | Intel HD Graphics 520 | 16GB RAM Link to comment Share on other sites More sharing options...
walt.farrell Posted March 22, 2023 Share Posted March 22, 2023 Sorry, but I don't. I do know it should be fixed as of 2.0.4, but you're still on V1 where I would not expect Serif to issue a fix. As a workaround you can temporarily disable the Bleed. malayali 1 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...
Staff Callum Posted March 22, 2023 Staff Share Posted March 22, 2023 Hi Malayali, Walts advice in this thread is correct this is a known issue that has since been fixed with version 2.0 unfortunately the only work around for this would be temporarily disabling bleed as Walt has suggested. Thanks C walt.farrell and malayali 1 1 Quote Please tag me using @ in your reply so I can be sure to respond ASAP. 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.