UIStroke With UICorner Rendering Error

[MapleMarvel]

Reproduction Steps

When a UIStroke and UICorner are used together, a small 1 pixel gap appears above the bottom border of the stroke, depending on the viewport size.

To Replicate:

• Add a ScreenGui
• Add a Frame to the ScreenGui
• Add a UICorner to the Frame
• Add a UIStroke to the Frame
• Resize the height of the viewport (by resizing the Studio size), and you will see the gap appear and disappear depending on the viewport height
  

Repo File:
Repo.rbxl (39.9 KB)

Expected Behavior

No gap should appear between the stroke and the UI element.

Actual Behavior

Depending on the viewport size, a small 1 pixel gap appears above the bottom border of the stroke.

Workaround

This is a rendering error with no workaround.

Issue Area: Engine
Issue Type: Display
Impact: High
Frequency: Constantly
A private message is associated with this bug report

[SomeFedoraGuy (rusuRares)]

Related

1 Pixel Gap Between any UI Element and UIStroke

Reproduction Steps To reproduce, just insert a Frame and add a UIStroke to it and you’ll see a gap at the bottom. This may be a bug caused by 2560x1440 resolution. [gap] CPU: Intel(R) Core™ i7-8700K CPU @ 3.70GHz GPU: NVIDIA GeForce RTX 2080 Expected Behavior I expect there not to be a gap between the Frame and the stroke outline. Actual Behavior There is a gap between the Frame and the stroke outline [gap] Workaround You can workaround it by adding a 1 pixel frame to fill …

[thirdtakeonit]

Thanks for the report! We’ll follow up when we have an update for you.

[Lyzrinn]

Any updates ? I have this issue on my end as well, and it’s especially obvious when the instance has a rotation, a UICorner and a UIStroke.

[Meat_Make]

having same issue, is this still being worked on?

[ScripterVen (vennyyy)]

Still having the same issue.

[0xabcdef1234]

Do you mind getting us a simple set up of your file so we can take a further look? Would be most helpful if you can also provide information of display resolution and system display scaling. We did released a fix for the original issue a while ago and I can no longer repro with the repro file above.