There’s a really annoying new bug in studio which has reared its head, now.
Look at all that white space!!! Why is the name being shortened because it’s too deeply nested? I need to make properties huge to see every script name now. Roblox pls fix
There’s a really annoying new bug in studio which has reared its head, now.
Look at all that white space!!! Why is the name being shortened because it’s too deeply nested? I need to make properties huge to see every script name now. Roblox pls fix
“PluginDebuggingEnabled”, “Show Core GUI in Explorer while Playing”, “Show Hidden Objects in Explorer”, “Show Plugin GUI Service in Explorer”, “Show Navigation Labels”, “Show Navigation Mesh”, “Show Pathfinding Links” and “Show Singly Selected Attachment Parent Frame” properties now invoke signals on change.
Just right now several Roblox clients were updated that broke UIGradient
keypoints with less than a 0.01 time difference to another keypoint. This is detrimental as nearly every progress bar in my game uses UIGradient
s like this along with the Offset
property.
The keypoint is no longer visible, and is being ignored when rendering.
The keypoint reappears when the time difference is 0.01+. This workaround causes blurring at the end of the progress bar
I have a drawing game which uses the CanvasDraw module, this update basically broke my entire game as it relies on a gradientmap drawing system and now all the drawings have weird lines and blurs all over them. Oh boy.
Similar to a couple other users in this thread, the internal changes undisclosed to UIGradients have also affected my studio’s games, which I’ve posted in a bug report here:
When will the fix for game.CreatorId go live?
The game.CreatorId fix should be live now in the latest Studio!
I just took a look after restarting studio but it still doesnt seem to be working properly.
Hm that’s interesting, are you in a published place? The CreatorId for an unpublished place is expected to be 0
I am in a published place yes.
ah rip, does this also happen if you make a new Baseplate place, publish that, and then try printing out the CreatorId?
If it works with the Baseplate/other places, I can try looking into that specific place file if you’re able to send it
i just opened a new baseplate place and launched a local test server, it prints 0 there aswell.
Do you want me to send a place file of the fresh opened baseplate place?
Thanks for the extra info, I can repro it now so no need to send the file. Looks like the CreatorId fix doesn’t work with the local server testing - it should work though if you do a playtest with the Play button.
I’ll look into getting a fix in for the local test server use case + will let you know when it’s live.
Ever since this release, it has made a huge bug in all my games. I use a custom proximity prompt and since this release whenever someone uses a proximity prompt it doesn’t go away. The prompt kind of just stays there and never disappears after.
Hi there!
I was wondering if you have an update on this for me.
The fix should be available in the next release - will let you know once it’s live