It’s a shame that after Roblox imposing the new debugger, and after I’ve pointed out over 30 bugs and there are still a lot of bugs pending, nothing gets done for months.
Will the shaking shadows bug be fixed? It’s only when you’re driving a car, I use A-Chassis Build 6.52S2, or is it from the car’s system?
Some awesome stuff in this update! Really love that SurfaceGuis finally got a MaxDistance, good for optimization.
When can we expect to see more details on how this works? The docs don’t reflect it yet.
A while yet. There will be an announcement post about the thing this relates to so you don’t need to worry about missing it.
Fixed a spike that happens 60 seconds after the a game starts.
Any insight on what that was?? Im curious
very nice, changing multiple number/colorsequences at once was really tedious thing to do and glad its finally addressed.
also glad the model scale clearing made it in.
When are us developers going to be able to customize throttling for it to affect in-game physics? Or maybe a way to slow down the physics ourselves.
Finally! The seams were a building nightmare.
Is this exclusively for when deferred events are enabled, or does it affect all modes?
The core script error spamming: are the errors fixed or is the output log just suppressed?
Or perhaps they were only warnings?
Whats the progress on the audio routing stuff from a few weeks ago, got it working with the right flags and its really cool in its current form especially with the visualiser effect
This is amazing no more need to code it manually for performance expensive surfaces
Out of curiosity is updating the PixelsPerStud dynamically expensive? I want to make it lower when the player is further away from it but I’m not sure if I’m doing worse if I do this.
Yes, because you may force repeated reallocation of the texture memory backing the surface if you’re not careful. You’d have to pay close attention to how often you increase the surface size in that way.
So glad the core script spam is being filtered out of the studio output, got really annoying when debugging. Also happy to know that random lag spike wasn’t from my code, was starting to worry me. 
The PerAxis ForceLimitMode for AlignPosition that was released recently has been mega useful and made transitioning from BodyPosition to AlignPosition easy peasy.
I was wondering if a PerAxis ForceLimitMode property is planned for AlignOrientation too, so that it can behave in a similar way to BodyGyro and it’s MaxTorque property, allowing developers to transition away from that too. (Using a new property called MaxAxesTorque, similar to MaxAxesForce)
Question was answered in a Q&A, and it is planned:
Whoops! The NumberSequence/ColorSequence change was added to the release notes a bit too early. There are still a few things to do before it will be ready to ship. We’ve removed it from the release notes for now.
Actually, the audio API is especially fantastic. I’ll be overjoyed if they arrive quickly.