Streaming Enabled Parent to nil Vs Script Parent to Nil

I did some Research and apparently Streaming enabled streams objects out by setting the parent to nil what’s the difference from me doing this with a local script with an object that’s only seen by the client.

Is there a difference?
is the difference that one is by Roblox and one is by a script made by the user?

If anyone knows the answer and can back it up with proof it would be greatly appreciated if you would be willing to help answer my question.

3 Likes

Streaming is replicated from the server to the client, it’s not like it’s invisible.
If the instance hasn’t been replicated to the client then the client will never know about it.

1 Like

What do you mean ?? By

My question is what’s the difference between setting streaming enabled setting the object parent to nil and a local script setting the object to nil on the client

Object isn’t on the server also it was created on the client

1 Like

I can be wrong, but I think that setting an object`s parent to nil will make it not render, but it will still exist in memory

while streaming enabled replicates objects from server to client when the client is close enough to them

1 Like

Right. I know it will exist still in memory. But here it says it sets them to nil so connections can stay on those objects. If it sets it to nil using the server and mine aren’t even made on the server what’s the difference from me setting my stuff to nil using a local script it’s not like the server can affect it by rendering it in and out because it’s not there

2 Likes

idrk tbh but Roblox has already made that system for us to use, so we don’t have to make it ourselves

just like culling, Roblox has added it, and we don’t have to recreate it

and it would probably be more optimized to use an engine built in feature

1 Like

It’s good but not amazing what I don’t like is how when a object renders in you have to go past the rendering distance I believe 2 times farther for it to render back out WHICH IS REALLY dumb lol. That’s the first issue second is people have mentioned how if you set a object to nil and move that object on the server it will still consume network data on the client. however if the object isn’t even made on the server that issue doesn’t even matter because the server can’t manipulate that object ( its client sided ) so I don’t really understand if there’s even a problem other then there still being memory usage ( which streaming enabled looks to be doing too by setting the objects to nil )

2 Likes

Kk I understand that but these are objects being created by a local script the server should not be able to affect these objects and even if streaming enabled could what’s the difference from me just setting there parents to nil and streaming enabled doing it ( objects aren’t on the server so it wouldn’t consume network data if something happens to it on the server ( because it can’t be edited on the server ) - client sided objects

1 Like

In this case, you would have access to them within the client’s memory, the difference would be this.

If you want to store them in a table for multiple scripts to access, you can.

When you use a variable to store an instance of the server that is streaming, the variable will not lose the instance, but it will not have any updates to it while the parent is nil.

do you mean can or can’t. if you mean can then ya I can do that easily but main issue is streaming enabled even worth using on these objects or would it be better to make my own system that can stream these client only objects in and out I would have more control plus its not like there will be network data issues caused by objects being edited by the server or the client. plus I could keep streaming enabled on for the server stuff but for client sided objects I can use a system that manages them

If the objects do not need to be replicated, then you can do it just on the client. Streaming is more intended for objects that will be replicated to all clients.

nice nice so the answer is no setting the stuff to nil if they are made on the client is fine and theres no difference because streaming enabled is for server side objects rendering to client and this is just rendering out objects seen by a specific client right !

or no is there a problem with this

What’s the problem? What’s the error?

just making sure of the last thing I mentioned could I do this without having any problems

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.