Release Notes for 736

Hey everyone, release notes are available for 736.

You’ll probably notice some differences in the release notes for this week. We’re trying to provide better clarity into when changes went live and what’s pending. Let us know here if you have thoughts on the new format!

26 Likes

how do we view new pending changes from previous updates? I also kind of liked the pending status next to it since it gave more visual separation of each change to me

3 Likes

The new release page is different. Will take some getting used to but I’m sure it will be easier to read in the long run.

2 Likes


w changelog


someone put the same change twice

6 Likes

they are in the pending changes tab

2 Likes

i dont see an issue honestly, they said that they changed it and this is imo a lot more informative

2 Likes

Why is the windows client one version behind. Like why is the windows client on v735 instead of v736


?

1 Like

I would honestly either combine the Pending page as a separate section under one page, or at least have a button that directs to it in the Current page. It is a little bit confusing in it’s current form.

7 Likes

Honestly liked the old version better
On mobile it was kinda tricky to find the pending changes tab (it was on the side bar hamburger menu)

1 Like

Seems there’s no 736:


and nor 735
and even nor 734.

Since this versioning is not purged, (well, I presume that studio will always show version number instead of “Week of”) could you please show on the documentation also?
Thank you!

1 Like

seems like the biggest change was the release notes themselves, interesting

4 Likes

This sounds hacky DFFlagPlayerCharacterDestroyDelay. What is this for?

Whatever this means, it sounds good DFFlagRakNetBanOnNetworkMisbehavior well, not sure what they refer to with “Ban” but yes.

Where is this Remote Profiler DFFlagRemoteProfilerCaptureAtFlip

what? DFFlagRemoveBasePartSizProperty

FFlagAnimationRigV2 I wonder what this will mean.

1 Like


pretty sure its referring to this mispelling property

4 Likes

oh it was lowercase

strange though this property is not writeable though there’s telemetry flags to figure out if anyone on Roblox is setting the .siz property

unless it’s by C++, but I don’t think so, that wouldn’t need telemetry, or unless it’s for “get”

 

Anyways

I wonder FFlagRenderShadowResolutionScaling

uhhh???

https://en.wikipedia.org/wiki/Multiple-document_interface

FFlagStudioClientServerMDI2

maybe? What could this be? Test multiple clients and server without it opening 100 Roblox Studios? Maybe not.

 

:thinking:

FFlagStudioPluginWindowCaptureAPI2 and FFlagStudioPluginWindowScreenshot

 

Optimization, Cinema FFlagStudsPerTileOptimization

 

Next Beta feature FFlagDeviceSimulatorRefreshBetaFeature

The changes mention a new entry point for collections, but the passed link gives no info on what this so called “new entry point” may be.

The changes are interesting. It seems like all pending changes don’t show on the releases page at all, only on that separate page.

I think they should show on both, with a drop down maybe or section still on the same release page.

I do like the supposedly comprehensive pending changes page though.

People who implement rbxm parsers (cough) will have a field day about siz and shap. What legacy jank caused such a property to exist is beyond me.

Its shouldn’t be possible to generate RBXM blobs with it anymore, but it will probably be given the quirky LoadOnly state that quite a few other removed properties have. It is definitely possible to generate such a blob that has siz in it by hand, but I think Roblox would prefer you dont.

this is def only for mcp servers