BEHOLD! Release Notes 667
40 Likes
Camera → PVInstance, thanks for not telling me why
12 Likes
Roblox got rid of the demons, hurray!
10 Likes
We want to make some changes that have to do with Attachments – making Camera inherit from PVInstance is part 1 of N, but we’re splitting this up into several pieces so as not to accidentally break anything.
If later changes turn out to be too reachy we might do a studio beta or a 3-phase rollout
19 Likes
Does this mean we can now input math operations into properties (e.g. set a part’s size to (1/8, 1, 1/8) )? I’d love to have this feature regardless.
4 Likes
AuroraScripts appear to be an upcoming feature for code to run on physics step or more frequently than traditional scripts.
7 Likes
You can do that currently! I think it’s been like that for quite a while now.
3 Likes
Wow, I’ve given it a try about once a month while building up until this point, and it’s never worked for me until now. That’s probably the bug they fixed in this release.
2 Likes
Interesting! The only time I tried it was when they released it, so it must have broken a little bit after that
1 Like
Context: Doing math in the properties pane has always worked but was broken for a couple weeks recently. This is the release note associated with the fix for that.
15 Likes
Any news about viewportframes? like render 2 cameras at the same time 
3 Likes
I noticed the HapticService got deprecated in docs and UI buttons got new haptic properties. When can we expect this new HapticEffect instance?
10 Likes
Fixes an issue that sometimes caused sounds shorter than one frame not to play.
Oh shit you mean this wasn’t my own fault? I have animations triggering short sounds such as beak/teeth clacking and occasionally random sounds would not play though they did other times.
4 Likes
Please tell me you guys are planning on removing the stupid attachment parent limit. They’ve been virtually unusable ever since they came out because of it.
15 Likes
+1 what’s the reason for restricting attachment parent type? It’s way more valuable to us if they would simply exist based around origin if they’re in a non-PVInstance parent. The only workaround we have is to shovel hundreds of these things into Terrain, or use container parts.
7 Likes
can you tell me what does this mean ?