THIS
Currently I can’t fully take advantage of StreamingEnabled because it’s not compatible with my terrain destruction system. All I’d need to fix that is a function on the server to force stream in/out a part.
(and maybe .InstanceStreamedIn/InstanceStreamedOut event? 
)
Just wanna say. I was thinking the best way you guys could push streaming enabled and I had no good answers.
I think this is fantastic.
It doesn’t negatively effect existing games but the performance and stability benefits come to all future games and any problems can be resolved as they happen instead of breaking anything that already worked.
Preventing OOM by 50% is huge.
20% faster load times on average is worthwhile.
I understand the intent behind Roblox making everything one size fits all.
The whole point is that they want to develop solutions and it should just work for developers. Specifically by giving the developer control it takes away their ability to sunset a feature, it becomes permanent legacy features and like everyone says you can’t just remove things that already work… but what if you never did anything to make it work? Thus this design philosophy.
I have the same problem with understanding this aswell, Streaming also caused one of the script i’ve made to not execute and it only loads a few parts in workspace that’s in player’s range when i have the preload functions on, used to look on documents at that time but it was awfully pain to get into this as i don’t see examples how it’ll work.
Add POV render culling please. I recently add my custom pov culling for high poly character and it massively increased performance. Imagine the performance gain if its part of the engine. You can start with just voxels, and eventually polygons, parts, etc. That + streaming, you can probably make detailed massive world with no issues.
I always use streaming in big open worlds. I don’t know if any real performance change will happen with smaller games.
Occlusion (or pov culling, frustum culling) is sadly not on Roblox since some devices can’t utilize it.
I’m thrilled about the update that enables streaming by default on all starter templates in Roblox Studio. This game changing feature allows for the creation of massive, detailed worlds, reduces join times by approximately 20%, and decreases crashes due to out of memory events. The availability of controls to modify streaming behavior and the emphasis on updated documentation and tutorials demonstrate Roblox’s commitment to supporting developers. I appreciate the proactive approach in addressing unexpected behaviors and welcome the opportunity to provide feedback for future improvements. Overall, this update enhances the development experience and empowers creators to push the boundaries of what they can achieve on the Roblox platform. So glad! Xx
I don’t think there is a chance it will break games now or in the future - it’s only if you create a new experience that it’s on by default. Existing experiences that didn’t have it on to start with, still don’t have it on.
As long as Low Memory and Opportunistic will both be available in the future, I think the majority of Devs will remain happy. Each has it’s use case, strengths and weakness. Opportunistic is helpful for new projects, so people new to the game engine can get a handle on how it handles rendering and memory usage. I see Low Memory mode as a “advanced” mode where the Dev can customized their own streaming radius for each individual player on the fly as needed which is good for low-end devices trying to play your game. I know the technical challenges of the behind the scenes code needed to make all this work, so my hats off to the game engine devs. Well earned praise for hard work. 
While streaming enabled has improved heavily over the past few years, a large amount of experiences will not benefit significantly enough from this change. Not every game wants to be a massive open world game and very few people have the resources to develop an open world game that can massively benefit from streaming enabled.
A much more preferable solution is to let us decide what features are enabled when creating a game from a template before the place is actually created (or let us create our own template games) instead of having Roblox decide for us.
I agree in principle, but I know this change is aimed at new young developers that make giant obby that span tens of thousands of studs. The change is easy enough to revert for any knowledgable developers. 
Don’t agree much, but at the same time i don’t really care that much to be honest. As long as you’re able to turn it off quickly then i don’t see the problem with this (which is automateable trough a very simple plugin, and at that point you don’t even need to do anything)
I have mixed opinions about this feature. For large templates, I think this will be beneficial. For small templates, I think this will not be beneficial and probably will not do anything at all, so it should not be enabled by default on these small templates.
Hi roblox I’m sorry to ask that in every post about StreamingEnabled you make but me (and as I can see many other developer) want to control which object is StreeamedIn or Out.(if this is not only StreamingRelated but we can control every Instabce that would be better)
Yeah no, enabling this and allowing the process of many people enjoy their session with less unnecessary lag and loaded parts of the map will help a lot. In the event it does mess with someone’s game enough they can easily toggle it off. Having it on by default helps games where most people probably dont even realize it’s a feature.
That may work for a showcase that has next to no programming. Otherwise, you simply cannot toggle it off.
I’ve outlined this in my post:
Honestly an L take.
You know this is disruptive to workflows … right?
To a degree which is on par with how the Team Create Enabled by Default update was disrupting many devs’ workflows as well— you knew that … right?
Having to remember to click buttons to disable <a horrendous setting> each time you make a baseplate is disruptive.
If it’s THAT much of an issue (it isn’t), how about you just save a baseplate as a template yourself rather than worrying about 1 second of setting changing?..
Like let’s be real here. If you’re developing anything worth anything, you’re already changing about a dozen settings upon opening up a new template to make sure the game settings work with the game you’re making - The extra time is negligible, and that’s assuming you want it disabled on EVERY project, when in reality, you’re better off leaving it enabled on a significant amount of projects.
I don’t want to sound rude, but whether it’s default off and you have to turn it on, or vice-versa, makes very little difference, and I’m not sure why this is being complained about…
This too. L take? Comparing it with team create turned on by default? There is no doubt as many people out there who, before, had to turn ON streaming-enabled every time the loaded a template, as there are people who now have to turn it off.
The only L here is y’all posting about how a setting that’s in a place you should already be adjusting settings in anyways is somehow “disruptive”, and the arrogance of thinking that everyone would benefit from this highly beneficial, usually benign checkbox being turned off by default, for your specific, 0.1-second convenience.
Team Create takes minutes to load out of and is a pain to enable/disable. This here is not disruptive to workflows, it’s a setting you change once at the beginning of your game’s development. The same way you’d adjust your lighting to be some exact hour with Voxel/Comp/Future/etc., you can disable StreamingEnabled.
Let’s look at it your way. Many games have main menus, so the character shouldn’t load in immediately. Let’s add an option for the CharacterAutoLoads property. Having the character load in is not what you want, so disabling it is disruptive to your workflow, right?
Oh wait, I actually want bubble chat for my game. Tons and tons of game have/need bubble chat (more than main menus for sure), so I have to enable it. Why should I enable it manually under Chat? This is disruptive to my workflow!!!
In the end you get something which looks like this:
Is this what you want?
Exactly. It seems like pure arrogance for someone to assert that a setting that takes under a second to change (Since people should already be looking at settings when a template is opened) and compare it to team create, something that is incredibly hard to properly work around in the modern context.
I had every single game locally saved prior to Roblox making Team Create the default. At the time they did this, many things were broken about it - For a time, Ctrl+S was changed by default to ‘Save to Roblox’ even on local files, meaning for a few weeks after the release it was literally not feasible to work on local file games.
Meanwhile, Roblox has patiently waited before toggling Streaming by default - Only doing so now that it is in the most stable state it has ever been in. And that’s coming from me, someone who still hasn’t toggled it on due to my already-made game not being compatible with it.
To compare team create to a setting being toggled to default? It’s just like. Man, roblox players must be SO privileged to come to that conclusion.