Path2d is Invisible for no reason

[sheyler1j (sr_animaciones)]

Hello, There is a rather strange and annoying bug with Path2d. The bug will be generated but not solved (the bug is not from my code, it is from the instance).

It is generated as follows:

Create or clone a path2d, if you toggle the visible property or it already starts to false, the bug will be generated. The bug causes the path2d to be invisible, so if I manually set Visible to true and change the ZIndex it will now appear (if you do it with code it doesn’t work).

As a note, if the bug is already fixed by toggling the ZIndex while it is visible, if I add a child the bug is generated again

[thirdtakeonit]

Thanks for the report! I filed a ticket in our internal database and we’ll follow up when we have an update for you.

[CharlieGordonnn]

Hi @sheyler1j , just to clarify - does the issue happen only in Studio, or also in the Roblox Player? If in the Player, is it across all OSs? And when did the issue first start happening? Thanks a lot!

[sheyler1j (sr_animaciones)]

Okay, the problem occurs on both. My operating system is Windows 11; I don’t have any other operating systems to try, but there are more reports of people having similar problems:

Path2D rendering bug in ScrollingFrames

When a Path2D instance is within a frame within a ScrollingFrame but outside the viewport bounds, it fails to render when scrolled back into view. Disabling and enabling the Visible property on the ScrollingFrame allows the path to render, but not a path that’s within a CanvasGroup. You have to manually update the Visible property on the CanvasGroup or the Path2D instance. Repro file: Place1.rbxl (65.9 KB) For some reason, in my game, I must constantly flip-flop the ZIndex property of my pat…

Your case mentions exclusively the ScrollingFrame but it fails me in every instance.
I have no idea when this started happening, as the same day I posted the error was my first time using this Instance.

[sheyler1j (sr_animaciones)]

Any news? I had to abandon my project after this problem.

[NoUniqueAddress]

Hi!

We’re working on a fix, will update when it goes live! Give it a ~few weeks or so.

Thanks!

[quartz708]

Hi, sorry to be a bother, do you think a fix will be included in the next studio update?

I’m using Path2Ds for a game’s HUD and I’m getting really buggy behaviour when it comes to toggling .Visible on the Path2Ds themselves as well as parent UI objects.

Certainly looking forward to the fix.

Thanks.

[NoUniqueAddress]

Hi! A fix for this was rolled out. Could you check if the bug still occurs? Thanks!

[sheyler1j (sr_animaciones)]

Mmm… Okay, I have the latest version of Studio and the problem persists.

I now understand how to generate the bug. You just need to start the game with the “Visible” property set to false. Then, when you try to change the value of that property, it won’t work. Also… I just found out that if you toggle the Zindex value, the instance will still become invisible even if you change the “Visible” property to true.

[sheyler1j (sr_animaciones)]

To be clear, the problem is between Zindex and Visible. Toggling Zindex at runtime or in the Editor causes the bug. It’s annoying, because I don’t even understand why it happens. You must change Zindex while Visible is false to generate the error, but also to fix it.

[NoUniqueAddress]

Could you share a repro. Might be a different issue. Thanks

[sheyler1j (sr_animaciones)]

In Studio:

In Ejetution:

The problem is when you change the ZIndex property while it is invisible.

[NoUniqueAddress]

Okay turns out this is a different issue. I have a fix but it’ll take a few weeks to roll out. I’ll update once it’s fixed! Thanks