jbikeler Posted January 22, 2023 Posted January 22, 2023 I'm attempting to use the erase alternate action for the pixel tool. It does not fully erase the pixels. Rather it acts more like the eraser tool and makes the pixels slightly more opaque. I have to go over multiple times to fully erase the pixel. Only a week ago I was using this feature and it was fully erasing. I have not changed anything in my settings or brushes. Any ideas on how to fix? Here's a screenshot of my settings. Quote
NotMyFault Posted January 22, 2023 Posted January 22, 2023 Please re-select a basic round brush, and try again. to check, use a layer filled with solid color, and increase brush size to e.g. 32px, then make a stroke. 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.
Bob-NL Posted January 22, 2023 Posted January 22, 2023 Same problem in my AP while opacity, flow and hardness are 100% with standard/normal brush. I attach a sample with one erase stroke through the green area (background is black) and same stroke until halfway. Mark the diferences. NB. In AP V1 erase tool its is working fine. MacOS Big Sur 11.7.2 AP V2.0.3 Quote
laurent32 Posted January 22, 2023 Posted January 22, 2023 Could it be you have this activated ? Quote MacBook Pro 16 pouces (3456 × 2234), 2021 / Apple M1 Pro / 16 Go / macOS Ventura Version 13.4.1 (22F82) + 31,5 pouces (2560 × 1440) + 27 pouces (1080 × 1920) + iPad (8th generation) / iPadOS 17.2 + Apple Pencil + … Macmini6,2 Quad-Core Intel Core i7 16 Go / macOS Catalina version 10.15.7 (19H2026) MacBookAir6,2 Intel Core i5 double cœur 4 Go / macOS Big Sur version 11.7.7 (20G1345) Licence Universelle Affinity V2 updated to 2.3.0
Bob-NL Posted January 22, 2023 Posted January 22, 2023 Yes, "wet edges" was activated. Ik was not aware of this option. Thanks!!!! Quote
jbikeler Posted January 22, 2023 Author Posted January 22, 2023 14 hours ago, NotMyFault said: Please re-select a basic round brush, and try again. to check, use a layer filled with solid color, and increase brush size to e.g. 32px, then make a stroke. I follow these instructions. The problem is that I'm not attempting tp use the basic round brush. I would like to pixel paint one pixel at a time. Even at one pixel the basic round brush will paint multiple pixels at a time with varying opacities. I am then trying to use the pixel tool to fully erase using the alternate operation (holding ctrl). My issue still occurs. While testing this an interesting thing occurred as well. I filled the whole layer with the like you said (using the flood fill tool). I then switched to the pixel tool, chose a different color, and painted a stroke. I then held control and attempted to erase straight through everything and the background, that was flood filled, seems to erase properly but my stroke that was painted still does not fully erase. This is still all on one layer. Here's a screenshot of the result. Quote
jbikeler Posted January 22, 2023 Author Posted January 22, 2023 Just in case the settings for different tools effect this operation, here of the settings I have for each tool. Quote
loukash Posted January 23, 2023 Posted January 23, 2023 50 minutes ago, jbikeler said: but my stroke that was painted still does not fully erase One problem with the Photo persona in Publisher – and with *.afpub documents in general – is the absolute pixel grid of the document. If your document has a bleed, the absolute pixel grid will start at the top left corner of the bleed. If the bleed doesn't have an integer pixel value, your brushes will always appear off the absolute grid, thus causing antialiasing on display. On bitmap export, the actual pixel appearance might be correct though. Same pixel grid bug also affects documents with multiple pages. Your problem seems to show typical symptoms. We've investigated similar issues with @NotMyFault just recently, among others in this thread here: NotMyFault 1 Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2
jbikeler Posted January 23, 2023 Author Posted January 23, 2023 I see. Thank you for making me aware. I prefer using Publisher's workflow for jumping between designer and Photo. Nevertheless, do you know if this issue occurs if we only use Designer(stand-alone not the persona within Publisher)? Hopefully this gets fixed because the workaround would be way to complicated every time you want pixel paint. Quote
loukash Posted January 23, 2023 Posted January 23, 2023 15 minutes ago, jbikeler said: do you know if this issue occurs if we only use Designer(stand-alone not the persona within Publisher) If you create a document with no bleed, or use strictly integer pixel values overall including bleed and page/artboard size and position, and you have Force Pixel Alignment on, then all should be fine. Also remember to use the Pixels view mode. As soon as you add a non-integer pixel bleed, all will be off the grid again and won't come back unless you create a new pixel aligned document and copy all previous content over… This conceptual flaw and the related bugs is a major p.i.t.a. ever since the Affinity beginning. jbikeler 1 Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2
loukash Posted January 23, 2023 Posted January 23, 2023 27 minutes ago, jbikeler said: I prefer using Publisher's workflow for jumping between designer and Photo. As a consequence of our findings, I made me new document presets based strictly on integer pixels. E.g. a standard DIN A4 300 dpi document with 3 mm bleed is then 2480×2508 px with 36 px bleed. The actual difference in mm fractions is really negligible.With Force Pixel Alignment on, this will already fix all pixel misalignment issues on page 1. The next problem in Publisher is the hardcoded vertical spread gap of 30 mm (!). That will bring all pixel objects off the grid vertically, starting page 2. There are workarounds in my aforelinked thread. NotMyFault, laurent32 and jbikeler 3 Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2
NotMyFault Posted January 23, 2023 Posted January 23, 2023 7 hours ago, jbikeler said: The problem is that I'm not attempting tp use the basic round brush. I would like to pixel paint one pixel at a time. Even at one pixel the basic round brush will paint multiple pixels at a time with varying opacities. Here is a misunderstanding. Even if you are using the pixel tool, you need to choose a brush. If you (by accident) selected a different brush like spray brush, you can resize brush to 1px, but this brush won’t paint or erase with full opacity because of its structure. So please, while using the pixel tool, select a basic round brush, then set the size etc as needed. It is essential, to avoid one source of trouble. The only alternative option is to create a rectangular brush on your own. This does not matter at all at 1px, but you then can use it with e.g. 8px to paint larger rectangles or other shapes, getting hard edges and corners. The round brush is perfectly fine to paint or erase exactly 1px. But you need to activate snapping and force pixel alignment, and deactivate move by whole pixels. 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.
NotMyFault Posted January 23, 2023 Posted January 23, 2023 If possible, please upload the actual affinity file. This helps us to inspect other possible sources of the unwanted behavior. 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.
NotMyFault Posted January 23, 2023 Posted January 23, 2023 Please include the following panels in screenshots: layer panel (expanded) color panel (showing color opacity) Try to open the file directly in Photo. Use the info panel to inspect color values. If issue is gone: you are impacted by the „publisher misalignment bug“, linked by Loukash for a test, activate settings(preferences) -> performance -> view quality nearest neighbor. If the issue is gone, your pixel layer is misaligned. If the problem persists, it is more likely a brush or color opacity issue - we need to dig deeper. Don’t forget to activate „Bilinear“ again, otherwise you are unable to spot such issues loukash 1 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.
firstdefence Posted January 23, 2023 Posted January 23, 2023 Just out of curiosity, is Wet Edges turned to ON in the brush settings? It's one of those settings that are easily missed. Quote iMac 27" 2019 Sequoia 15.0 (24A335), iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9 (Please refrain from licking the screen while using this forum) Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions
jbikeler Posted January 27, 2023 Author Posted January 27, 2023 On 1/22/2023 at 10:14 PM, NotMyFault said: If possible, please upload the actual affinity file. This helps us to inspect other possible sources of the unwanted behavior. Attached. On 1/22/2023 at 10:18 PM, NotMyFault said: Please include the following panels in screenshots: layer panel (expanded) color panel (showing color opacity) Try to open the file directly in Photo. Use the info panel to inspect color values. If issue is gone: you are impacted by the „publisher misalignment bug“, linked by Loukash for a test, activate settings(preferences) -> performance -> view quality nearest neighbor. If the issue is gone, your pixel layer is misaligned. If the problem persists, it is more likely a brush or color opacity issue - we need to dig deeper. Don’t forget to activate „Bilinear“ again, otherwise you are unable to spot such issues Here are the expanded panels. Changing to nearest neighbor did not solve the issue. It does works as intended in the standalone Photo and Designer application. It must be the misalignment bug. Still going to attach the files for more data in the investigation. Button.afpub Quote
- S - Posted January 28, 2023 Posted January 28, 2023 @jbikeler As another poster mentioned, this is caused due to the Pixel tool inheriting the "Wet Edges" setting from another brush. The Pixel tool just doesn't show the "Wet Edges" setting in the Context Toolbar at the top. Selecting a basic round brush in Affinity Photo 2 also won't reset it. Therefore, I would create a new square brush like "NotMyFault" mentioned and use this to reset the Pixel tool. If you keep this newly created brush in your Brushes panel, you can select the brush again in the future to reset the Pixel tool if the issue occurs again. See below video. Square Brush.mp4 NotMyFault 1 Quote
NotMyFault Posted January 28, 2023 Posted January 28, 2023 7 hours ago, - S - said: As another poster mentioned, this is caused due to the Pixel tool inheriting the "Wet Edges" setting from another brush. The Pixel tool just doesn't show the "Wet Edges" setting in the Context Toolbar at the top. I would call this a bug - inheriting a setting which is unsuitable, but hiding the control which would allow to deactivate it. One more questions, to avoid the same issue in future: why is pixel tool inheriting only “enforce”, but not “disable”? does it make a difference if you share brushes across tools? what are the circumstances who trigger inheriting wet brushes? You can reach the "wet edges settings of the brush via "more", and modify the settings jbikeler 1 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.
NotMyFault Posted January 28, 2023 Posted January 28, 2023 10 hours ago, jbikeler said: Attached Thanks a lot. I’ not yet fully convinced its related to wet edges. i opened the file on iPad, there the wet edges is visible and off, but the issue persists. But i noticed something that might cause the issue: you have pixel layers stretching over 2 artboards. This is bad and must be avoided. If you select one artboard create new pixel layer (inside that artboard) start to use brush or pixel brush everything is fine snapping settings might play into this, never use “move by whole pixels”. jbikeler 1 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.
pigeon Posted December 29, 2023 Posted December 29, 2023 Is there any way to reset the pixel tool to its default settings (affinity photo)? I have changed brush type for this tool and can't get it back to how it originally was (1x1 square). I've created my own square image brush, but it does behave a bit differently than the default one. Quote
walt.farrell Posted December 29, 2023 Posted December 29, 2023 23 minutes ago, pigeon said: Is there any way to reset the pixel tool to its default settings (affinity photo)? I have changed brush type for this tool and can't get it back to how it originally was (1x1 square). I've created my own square image brush, but it does behave a bit differently than the default one. Which application and what release are you using? 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
walt.farrell Posted December 30, 2023 Posted December 30, 2023 If you're using V2, @pigeon, here's the default Pixel Tool brush from Affinity Photo: Default Pixel Tool Brush.afbrushes pigeon 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 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
brunhilda Posted January 14, 2024 Posted January 14, 2024 Hi, I might have the same problem with a pixel erase brush tool in Designer. I can never erase a bitmap with one click only, even thought the wet edges or other brush settings are on default. updated macOS Sonoma (but the problem persists for a year or longer) Quote
Old Bruce Posted January 14, 2024 Posted January 14, 2024 37 minutes ago, brunhilda said: I can never erase a bitmap with one click only, even thought the wet edges or other brush settings are on default. Is it a square brush or a round brush that you are using? I will wager it is a round brush. Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that.
walt.farrell Posted January 14, 2024 Posted January 14, 2024 40 minutes ago, brunhilda said: even thought the wet edges or other brush settings are on default. What you show as "the default" is "don't set wet edges", which means "do not turn it on if it's off already, and do not turn it off if it's on already". If you want to make sure it's off, set it to turn off. 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
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.