Lucas Varela Posted November 16, 2022 Posted November 16, 2022 When drawing in the Pixel persona on certain layers, the canvas doesn't seem to update correctly and only a part of the painted brush stroke is visible until some action "forces" the canvas to redraw, like zooming in, changing the current layer or hovering the mouse over the painted area. I'm able to reproduce the issue on Mac and iPad, using either mouse or Apple Pencil. I've captured the bug on iPad since it's easier to record there: RPReplay_Final1668621991.mp4 This issue only seems to happen on specific layers, and I couldn't reproduce on a new file, so I attached the one I'm working with in the video. Steps to reproduce: Open the attached file: docs-glossary-models.afdesign Change to Pixel persona Select the Artboard1 -> Revistas -> Pixel layer (the first in its group) Select the Brush tool and draw something big Notice how some of all the painted brush stroke is missing Zoom in/out, change the selected layer or simply move the mouse over the painted area to force a screen to redraw I can draw normally on layers placed at the root of the artboard, but nested layers will still present the bug if I go back to them. That being said, there's a workaround: moving the layer I want to draw on to the root of the artboard, then moving them back to where they were after I finish. It works, but it's not ideal. Additional info: I'm using v2.0.0 on Mac (2020 MacBook Air, M1) and v2.0.1 on iPad (3rd Gen iPad Pro 11', also M1). Both devices have an M1 processor, which might be related. Still reproducible with the given settings on Mac: Display: OpenGL, Hardware Acceleration enabled; Display: OpenGL, Hardware Acceleration disabled; Display: Software, Hardware Acceleration disabled. Happened on a couple of other files, but I couldn't figure out how I got to solve the issue. I probably moved layers or created new ones, and the issue seemed solved at the time. Olidoesaffinity 1 Quote
walt.farrell Posted November 16, 2022 Posted November 16, 2022 Welcome to the Serif Affinity forums. There is a known problem in V1, which has not yet been fixed in either V1 or V2, when painting on pixel layers nested within a vector layer. Here is a search that shows a couple of discussions of this bug: https://forum.affinity.serif.com/index.php?/search/&tags=afd-5473 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, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Patrick B Posted November 16, 2022 Posted November 16, 2022 I can confirm that I'm seeing this bug happen on an M1 iMac, running macOS 11. Quote
Lucas Varela Posted November 17, 2022 Author Posted November 17, 2022 14 hours ago, walt.farrell said: Welcome to the Serif Affinity forums. There is a known problem in V1, which has not yet been fixed in either V1 or V2, when painting on pixel layers nested within a vector layer. Here is a search that shows a couple of discussions of this bug: https://forum.affinity.serif.com/index.php?/search/&tags=afd-5473 Thanks for the response, Walt! I tried some search terms before posting and couldn't find any related bugs, so thanks for pointing these posts out. Good thing this is a known bug. To anyone who gets here looking for a solution, there's an easier workaround detailed in one of the posts Walt mentioned: Quote Further testing revealed that this behavior will not manifest if your uppermost (root) layers has a fill layer, which expands the rendering bounds to the whole canvas. You can have further nested layers or groups without strokes failing to render for this reason. This fill layer can be a white+multiply layer to have no visual effect, but as long as it's set to visible, it will fix this specific rendering fault. Source: Quote
Olidoesaffinity Posted January 12, 2024 Posted January 12, 2024 I am seeing the same problem on PC. The workaround works to fix it. I was also seeing this problem on Ipad. 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.