Release Notes for 429

[LuaCow]

Notes for Release 429

[Maximum_ADHD]

Client Difference Log

0.429.0.403819

API Changes

Added Class Atmosphere : Instance
	Added Property float Atmosphere.Density
	Added Property float Atmosphere.Offset
	Added Property Color3 Atmosphere.Color
	Added Property Color3 Atmosphere.Decay
	Added Property float Atmosphere.Glare
	Added Property float Atmosphere.Haze

Added Property bool DebuggerBreakpoint.IsLocal
Added Property bool Studio.Show Whitespace
Added Property Color3 Studio.Whitespace Color

Added Function void Player:RequestStreamAroundAsync(Vector3 position, double timeOut = 0) [Yields]

Added EnumItem StudioStyleGuideColor.ScriptWhitespace : 56

Changed the parameters of Function ScriptDebugger:SetBreakpoint 
	from: (int line)
	  to: (int line, bool isLocalBreakpoint)

Changed the parameters of Event Lighting.LightingChanged 
	from: (bool skyboxChanged)
	  to: (bool skyChanged)

Changed the value of EnumItem StudioStyleGuideColor.DebuggerCurrentLine from 56 to 57
Changed the value of EnumItem StudioStyleGuideColor.DebuggerErrorLine from 57 to 58
Changed the value of EnumItem StudioStyleGuideColor.DiffFilePathText from 58 to 59
Changed the value of EnumItem StudioStyleGuideColor.DiffTextHunkInfo from 59 to 60
Changed the value of EnumItem StudioStyleGuideColor.DiffTextNoChange from 60 to 61
Changed the value of EnumItem StudioStyleGuideColor.DiffTextAddition from 61 to 62
Changed the value of EnumItem StudioStyleGuideColor.DiffTextDeletion from 62 to 63
Changed the value of EnumItem StudioStyleGuideColor.DiffTextSeparatorBackground from 63 to 64
Changed the value of EnumItem StudioStyleGuideColor.DiffTextNoChangeBackground from 64 to 65
Changed the value of EnumItem StudioStyleGuideColor.DiffTextAdditionBackground from 65 to 66
Changed the value of EnumItem StudioStyleGuideColor.DiffTextDeletionBackground from 66 to 67
Changed the value of EnumItem StudioStyleGuideColor.DiffLineNum from 67 to 68
Changed the value of EnumItem StudioStyleGuideColor.DiffLineNumSeparatorBackground from 68 to 69
Changed the value of EnumItem StudioStyleGuideColor.DiffLineNumNoChangeBackground from 69 to 70
Changed the value of EnumItem StudioStyleGuideColor.DiffLineNumAdditionBackground from 70 to 71
Changed the value of EnumItem StudioStyleGuideColor.DiffLineNumDeletionBackground from 71 to 72
Changed the value of EnumItem StudioStyleGuideColor.DiffFilePathBackground from 72 to 73
Changed the value of EnumItem StudioStyleGuideColor.DiffFilePathBorder from 73 to 74
Changed the value of EnumItem StudioStyleGuideColor.Separator from 74 to 75
Changed the value of EnumItem StudioStyleGuideColor.ButtonBorder from 75 to 76
Changed the value of EnumItem StudioStyleGuideColor.ButtonText from 76 to 77
Changed the value of EnumItem StudioStyleGuideColor.InputFieldBorder from 77 to 78
Changed the value of EnumItem StudioStyleGuideColor.CheckedFieldBackground from 78 to 79
Changed the value of EnumItem StudioStyleGuideColor.CheckedFieldBorder from 79 to 80
Changed the value of EnumItem StudioStyleGuideColor.CheckedFieldIndicator from 80 to 81
Changed the value of EnumItem StudioStyleGuideColor.HeaderSection from 81 to 82
Changed the value of EnumItem StudioStyleGuideColor.Midlight from 82 to 83
Changed the value of EnumItem StudioStyleGuideColor.StatusBar from 83 to 84
Changed the value of EnumItem StudioStyleGuideColor.DialogButton from 84 to 85
Changed the value of EnumItem StudioStyleGuideColor.DialogButtonText from 85 to 86
Changed the value of EnumItem StudioStyleGuideColor.DialogButtonBorder from 86 to 87
Changed the value of EnumItem StudioStyleGuideColor.DialogMainButton from 87 to 88
Changed the value of EnumItem StudioStyleGuideColor.DialogMainButtonText from 88 to 89

(Click here for a syntax highlighted version!)

[Noble_Draconian]

Glad to see this minor bugfix got through! I had actually disabled the Beta feature because of this bug, now I can turn it back on.

[ThatTimothy]

Great update, we finally have access to atmospheres!

There’s just so much potential with this, and I can’t wait for the community to start making some awesome builds and scenery.

Also great to see that adding one enum item:

Added EnumItem StudioStyleGuideColor.ScriptWhitespace : 56

Caused one of the longest chain of changes I’ve seen in a while:

Changed the value of EnumItem StudioStyleGuideColor.DebuggerCurrentLine from 56 to 57
Changed the value of EnumItem StudioStyleGuideColor.DebuggerErrorLine from 57 to 58
Changed the value of EnumItem StudioStyleGuideColor.DiffFilePathText from 58 to 59
Changed the value of EnumItem StudioStyleGuideColor.DiffTextHunkInfo from 59 to 60
Changed the value of EnumItem StudioStyleGuideColor.DiffTextNoChange from 60 to 61
Changed the value of EnumItem StudioStyleGuideColor.DiffTextAddition from 61 to 62
Changed the value of EnumItem StudioStyleGuideColor.DiffTextDeletion from 62 to 63
Changed the value of EnumItem StudioStyleGuideColor.DiffTextSeparatorBackground from 63 to 64
Changed the value of EnumItem StudioStyleGuideColor.DiffTextNoChangeBackground from 64 to 65
Changed the value of EnumItem StudioStyleGuideColor.DiffTextAdditionBackground from 65 to 66
Changed the value of EnumItem StudioStyleGuideColor.DiffTextDeletionBackground from 66 to 67
Changed the value of EnumItem StudioStyleGuideColor.DiffLineNum from 67 to 68
Changed the value of EnumItem StudioStyleGuideColor.DiffLineNumSeparatorBackground from 68 to 69
Changed the value of EnumItem StudioStyleGuideColor.DiffLineNumNoChangeBackground from 69 to 70
Changed the value of EnumItem StudioStyleGuideColor.DiffLineNumAdditionBackground from 70 to 71
Changed the value of EnumItem StudioStyleGuideColor.DiffLineNumDeletionBackground from 71 to 72
Changed the value of EnumItem StudioStyleGuideColor.DiffFilePathBackground from 72 to 73
Changed the value of EnumItem StudioStyleGuideColor.DiffFilePathBorder from 73 to 74
Changed the value of EnumItem StudioStyleGuideColor.Separator from 74 to 75
Changed the value of EnumItem StudioStyleGuideColor.ButtonBorder from 75 to 76
Changed the value of EnumItem StudioStyleGuideColor.ButtonText from 76 to 77
Changed the value of EnumItem StudioStyleGuideColor.InputFieldBorder from 77 to 78
Changed the value of EnumItem StudioStyleGuideColor.CheckedFieldBackground from 78 to 79
Changed the value of EnumItem StudioStyleGuideColor.CheckedFieldBorder from 79 to 80
Changed the value of EnumItem StudioStyleGuideColor.CheckedFieldIndicator from 80 to 81
Changed the value of EnumItem StudioStyleGuideColor.HeaderSection from 81 to 82
Changed the value of EnumItem StudioStyleGuideColor.Midlight from 82 to 83
Changed the value of EnumItem StudioStyleGuideColor.StatusBar from 83 to 84
Changed the value of EnumItem StudioStyleGuideColor.DialogButton from 84 to 85
Changed the value of EnumItem StudioStyleGuideColor.DialogButtonText from 85 to 86
Changed the value of EnumItem StudioStyleGuideColor.DialogButtonBorder from 86 to 87
Changed the value of EnumItem StudioStyleGuideColor.DialogMainButton from 87 to 88
Changed the value of EnumItem StudioStyleGuideColor.DialogMainButtonText from 88 to 89

[CaptinLetus]

Seems like this update added a lot of unnecessary glare on beams and other reflective items in my game. Completely ruins the aesthetic that my game has had for months. Is this intended?

Before the update, these weren’t nearly as bright

On the beams, light emission and light influence are both 0.

[Hexcede]

Does this function mean we will be able to stream certain areas of our games manually or is this meant to be limited to CoreScripts?
Added Function void Player:RequestStreamAroundAsync(Vector3 position, double timeOut = 0) [Yields]

[buildthomas]

See the bug report here: Rendering Issue (Beams, Trails, Fog, Lighting)

[UnderMyWheel (Wheely)]

I believe this may be related to the Pre-Streaming API that is targeted for release this quarter. It seems unlikely developers will ever have access to forcefully stream areas as networking streaming is meant to be completely handled by the engine.

[Maximum_ADHD]

I have a pretty good feeling this enum is generated at runtime from the Theme.json files found in Roblox Studio’s Qt resources:

https://github.com/CloneTrooper1019/Roblox-Client-Tracker/blob/roblox/QtResources/themes/DarkTheme.json

https://github.com/CloneTrooper1019/Roblox-Client-Tracker/blob/roblox/QtResources/themes/LightTheme.json

If an engineer inserts a new value into the middle of these files, it results in the large value shift observed in the API diff.

[Hexcede]

It seems to be that way, however it appears that said API is going to available to developers (Aka, the API is meant for developers to make that hint rather than the engine attempting to predict it?). If the function is intended to have any security level its not currently marked as such.

[opplo]

Underwater fog seems to have changed perhaps unintentionally?

I’ve been asking for a long time to be able to edit properties of underwater fog similar to Lighting fog so players can see further under water instead of just having a colour and a broken transparency value that doesn’t make much sense.

Now we can’t see as far underwater as before, and water has become grey & ‘murky’ which a lot of my SharkBite community don’t seem to like.

Same position & angle before update:

After:

Underwater fog also seems to have no effect on the visibility of ropes now either:

Can water be put back to how it was? Or ideally some sort of water fog properties be added to Atmosphere so we can change this ourselves.
See:

Underwater 'Fog' WaterTransparency Limit of 1 Too Small

As a Roblox developer, it is currently impossible to see long distances underwater. We are limited to a WaterTransparency property of 1. If a player is in control of a fast moving object underwater such as a Shark or Submarine it’s hard to predict oncoming objects until it is too late and a collision takes place. As creator of SharkBite, the largest game that completely relies on Roblox water terrain this limits what I can create, I can’t create fast sharks or fast under water boats. It also l…

[UnderMyWheel (Wheely)]

The API will definitely be open to all developers.

From the way I understand the description on the roadmap, it will allow for developers to “hint” to the engine of what areas to load. But, developers shouldn’t necessarily rely on the area being forecfully loaded as it may not be possible due to the client’s resource limitations.