Release Notes for 605

Notes for Release 605

69 Likes

Sanitized ID still not fixed. Please roblox. for the sake of us

62 Likes

What?

41 Likes

This refers to an update to the Luau programming language and was not intended to be included in the public release notes for the engine.

27 Likes

Is this supposed to be AssemblyLinearVelocity or AssemblyAngularVelocity? no property called AssemblyVelocity afaik

28 Likes

Appears to be both. Good catch.

(A previous version of this post said just AssemblyLinearVelocity, but I think now that is not true)

19 Likes

Are there plans on adding require-by-string to the Roblox ecosystem, or is this just for the REPL?

If so, how would that function with relation to asynchronously replicated modules, or will they have to be put inside a static container?

18 Likes

What specific conditions?

The error is failed to load animation. There’s many situations in which an animation could fail to load and many reasons why, some of which are legitimate, others of which aren’t.

As far as we can tell we fixed the main illegitimate failure case. That main failure case just happened to start around the same time the error was reworded, hence the association with “Sanitized ID”, but the rewording of the error message doesn’t have anything to do with animation loading issues.

There could be others or the original problem could still persist but please include more info than “Sanitized ID” when reporting this because there are cases where you should legitimately be getting that error, for example, if you’re missing permissions to the animation asset.

27 Likes

Yes, we plan to have it on Roblox.

While they could work exactly the same (yield until childs arrive), our focus right now is to only support modules that have already replicated at the time they are required.

24 Likes

amazing update! (i have no clue what any of these words mean)

31 Likes

This sounds very interesting though, is it an improvement to dynamic require behavior?

11 Likes

I can’t wait! So much more intuitive and can be used anywhere

14 Likes

Making a game: The setup involves the game owner, who handles the building, myself as the coder, and another person responsible for animations. The problem arises when the owner imports animations into Roblox, and we end up with sanitized IDs. Despite delving into various forums for solutions, the issue persists.

Interestingly, when I, as the coder, import and use animations, everything seems to work fine on my end, but not for the actual players. On the flip side, in a different game scenario, where the owner imports the animations. It gives the error.

I’m uncertain whether this hiccup stems from a scripting error or some other source. I’ve exhausted every avenue to find a solution but haven’t been successful so far. Any insights or guidance on this matter would be greatly appreciated.

this post went a few ways…sorry

16 Likes

think you can try to get the word out that there is a glitch going on that doesn’t change the material when picking a material varient in properties, it gets quite annoying manually finding which material the material varient applies too. Thanks

9 Likes


I won’t spend 5 hours trying to figure out this dumb mistake anymore, yay

24 Likes

Hopefully these have type checking and autocomplete…!

12 Likes

It’s been ages since we got some release notes.

Finally, we got one. I assumed we would hold off for another month.

Man, I wish this would happen sooner rather than later.

14 Likes

This is already fixed in an update coming early next year.

13 Likes

Glad to see somethings being done about the poor state particle emitters have been left in, devs constantly either working with or around bugs to achieve certain effects.

7 Likes

after this release note studio freezes when i open the live game and stays frozen until i close the client entirely, not just leave the game was this an intended change and why in the world?

7 Likes