Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

Pixel layer strokes not rendering outside of parent layer bounds


Recommended Posts

What system are you on, what system spec? Can you create a sample file to upload that still does this or is this document specific?

I'm currently on Catalina and cannot reproduce this.

iMac 27" Late 2019 Fully Loaded and running Monterey 12.6.1, iMac 27" Late 2013 running Catalina 10.15.7 - Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9 B|  

Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions

Link to comment
Share on other sites

  • Moderators

Hi Vozf,

Does this happen with Hardware Acceleration on/off or both?  Edit > Preferences > Performance ?

If it's document specific and you'd like to send us the file directly to take a look you can upload it -here-

Lee

Link to comment
Share on other sites

Probably related to one of these older cases

 

 

Mac mini M1 A2348

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

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.

 

Link to comment
Share on other sites

It might not be involved nor solve the visibility issue but makes me just curious:
What are the two top most layers in your screenshot, it looks like a Layer layer and a nested "frame (Rectangle)" – whereas I don't understand how this "frame" is nested. Any kind of masking?

55251032_nestedlayer.jpg.2f0f47320e73a8e1d5baf30693260ea7.jpg

macOS 10.14.6, MacBookPro Retina 15" + Eizo 27"

Link to comment
Share on other sites

I managed to whittle down the file to a simple case with nested vector layers. See attached.

@thomasoThat vector-masked rectangle did not have an effect when I deleted it. The key is a top-level layer (with vector mask, disabled or enabled makes no difference). Then nest a vector layer inside it, and try to use pixel layers inside the child layer.

@LeeThorpeTurning hardware acceleration on or off doesn't have an effect.

@firstdefence I'm on Windows, but this also reproduces in Affinity Designer for iPad, and I now suspect it's universal.

nested layer pixel bounds.afpub

Link to comment
Share on other sites

16 minutes ago, vczf said:

I managed to whittle down the file to a simple case with nested vector layers.

To me the issue occurs even in a more simple setup: 2 layers only, pixel paint in a Layer layer:
(ps: same works fine outside of this parent layer / not in the video)

Feels like a 'simple' redraw issue. FWIW, my performance settings (my permanent default without getting such issues / I haven't tried others for this test). Since it is set not to use the separate GPU the mac's fan was speeding up quite obvious while painting the above strokes.

664405909_pixelbrushinaLayerlayerbug-performance.jpg.77ad0f17fa6c22e232b0d3d0d47d80c6.jpg

macOS 10.14.6, MacBookPro Retina 15" + Eizo 27"

Link to comment
Share on other sites

@thomaso Based on the more erratic way your pixels are disappearing, I think these are different issues. With the nested layers in my test case, the behavior of the strokes being "clipped" by the layer bounds is very consistent and repeatable. In your case, it looks like rectangular chunks of the canvas are failing to update.

Link to comment
Share on other sites

The issue matches the older one:

In Designer (or Publisher), a pixel layer nested to a layer layer or group layer causes severe delay of paint brush. In this Case, you need to zoom to get a valid rendering. You can identify the issue if you use the navigator panel: it’s thumbnail shows the correct result, only the canvas is severely delayed, until using zoom to enforce a redraw.

The observation that the redraw issue is related to the (inactive) rectangular vector mask is no proof of totally new unrelated bug.

 

Mac mini M1 A2348

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

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.

 

Link to comment
Share on other sites

45 minutes ago, NotMyFault said:

a pixel layer nested to a layer layer or group layer causes severe delay of paint brush.

Sorry!, I did not look into your linked thread before, where Dan C mentioned this to be known and logged for all platforms …

On 1/14/2022 at 1:59 PM, Dan C said:

I can confirm that this issue is already logged for all platforms, the bug occurs when the Pixel layer is within a container layer (either a 'Layer' or 'Group').

macOS 10.14.6, MacBookPro Retina 15" + Eizo 27"

Link to comment
Share on other sites

The „virtual“ rectangle you observe is the bounding box around the visible layer content.  There are other issues documented where Affinity fails to render the canvas, and rendering artifacts occur aligned to these bounding boxes. (Mostly when dealing with alpha and having more than one vector mask, combined with alpha aware adjustments)
 

Note that wrt bounding boxes I relate to rendering level mip map process boxes (zoom level depending), and not the actual layer bounding box (move tool). Of course, both can look identical like in this case, but not in general.

To summarize: clearly a rendering bug, but I assume based on already identified common root causes (links I posted before).

If you want this clarified, you may open a new bug report in the bug section, and link to this post (in the questions section). 

Mac mini M1 A2348

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

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.

 

Link to comment
Share on other sites

  • 4 months later...

I am disappointed to note that this bug continues to reproduce in Affinity 2 for Windows and iPadOS (on the 30 day trial).

However, I became curious why this is not a larger issue for other users. 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.

Which is to say that this issue can be avoided by always working inside a single top-level "main" container layer with a fill, rather than having multiple layers or groups at the root level. If you want multiple root siblings, then you'd have to give each of them a fill layer child to avoid this rendering flaw.

Example attached to this post.

nested layer pixel bounds.afpub

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.