Jump to content

Recommended Posts

Posted

In the attached file, the magenta border at the bottom is not drawn completely.

When the border width is se to 204px it is drawn correctly.

When the border width is set to 228px it is drawn correctly

The problem seems to exist at all widths in between.

When opened on an older machine with Photo 2.4.1 it displays properly.

Beta 2.5.3.2516
Windows 11
AMD 7950X
Radeon 7900XT - Windows reports "best drivers installed"

Accleration on or off - same issue

 

 

funicular.afphoto

Posted

Can you provide screenshots of incorrect rendering, including:

  1. full app window
  2. layer stack / thumbnails
  3. navigator panel
  4. transform panel (magenta layer active and move tool)

ps: a empty pixel layer as background is sufficient to trigger this bug.

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.

 

Posted

I think this is what you want.

I've also noticed that when  I move the model around, the part of the magenta border that is affected changes.

fullapp.png

layers.png

navigator (magenta active).png

navigator.png

Posted

For a test: can you use the noise button for the colors (clicking on the opacity button), instead of using noise filters?
those are “heavy” and might cause the issue.

BTW noise looks correct only if zooming to 100%, when zooming out the noise effect is exaggerated and does not match exports. 

 

Does the image looks correct when exported or when using merge visible?

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.

 

Posted

After playing with the file on iPad, I can reproduce the issue. Merge visible results in wrong result, cutting part of pink frame.

A combination of bevel/emboss and multiple noise filters seem to trigger the effect.

The 3d effects creates a kind of semi-transparent halo around the shapes which I rate as (additional) bug.

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.

 

Posted

Steps to reproduce:

  • create new document 1750px both axis
  • place image file, move image slightly off center so it doesn’t touch lower and right edge, and extends over left and upper edge
  • add rectangle, no fill, stroke in any color 225px alignment to inside
  • merge visible

the stroke misses a portion.

reproduced on iPad. 2.5.4 retail

225 stroke bug.afphoto

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.

 

Posted

I think it's way more straightforward and simply a glitch with Stroke Inside across all three apps on Mac and Windows when exporting to raster-based file formats specific to a stroke width range between 215 px and 237 px for a 1750 px x 1750 px document regardless of the document dpi... It doesn't affect vector-based file formats...

When the stroke width is less than 215 px or greater than 237 px for the same document dimensions the stroke renders correctly for raster-based file formats...

Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

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...
×
×
  • Create New...

Important Information

Terms of Use | 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.