Hi everyone! I’m here with the release notes for 674.
Fun fact: in May of last year, to celebrate the baguette , a French post office released a scratch-and-sniff stamp that smelled like bread. Revolutionary.
Have a great rest of the week!
Hi everyone! I’m here with the release notes for 674.
Fun fact: in May of last year, to celebrate the baguette , a French post office released a scratch-and-sniff stamp that smelled like bread. Revolutionary.
Have a great rest of the week!
Does this mean you guys fixed the blurry text and icons?
Definitely interested in this one, is this a performance improvement or a fix for some physics jankiness?
Give it to me raw doc when’s it coming?
I got the StyleEditor to work with FFlags I couldn’t get effects to work but I might’ve just missed a few flags.
This seems like it could be breaking.
When you say ‘destroyed’, do you mean just parented to nil or like parent-locked and callbacks disconnected?
im guessing it’ll act similar to how it does it on the server (it does :Remove() instead of :Destroy()) so u can just reparent it, but i don’t feel like this needed to be patched anyways
Will the Mouse KeyCodes for InputActions also be set on mouse InputObjects?
Hi,
InputObjects are not changing. You should still check for UserInputType
. Mouse KeyCode support is only be added to InputBinding
(For InputActions
).
Any updates on this? It was added recently and then removed with this version and is no longer on the docs page:
I’m assuming it wasn’t production ready.
Can someone please fix ztestmodulescriptvmstateoptimization2
.
It is not in Version 674 nor inherits the current configurations.
It will be back but possibly in a different form, we’re reconsidering the API design.
This channel being behind is intentional; users in it will update when it closes as scheduled on Monday. Is it causing problems for you?
Regarding the contents of the channel, I haven’t noticed anything.
I’m curious what the purpose of these are supposed to be - do we not already have these maps available?
Yes, we’ve had these maps, but they only accept the ContentId
data type, which is formatted strings that link to an asset (e.g, rbxassetid://123456789).
The Content
data type, on the other hand, while still being a reference to an asset, provides more flexibility in the types of content to be used. Currently, the Content
data type can represent the “normal” way of referencing an asset (rbxassetid://123456789) through a URI or an Object
. This opens up the door to using features such as EditableImages
within Material Variants and other instances.
It needs to be better communicated to the user what channel they’re on, and there needs to be an option to switch the channel in studio. Being randomly enrolled into a channel that is intentionally out of date without my knowledge is really annoying.
What was the issue with the current API design though?