Is there a way to put an instance into a low-memory state?

[sevenpolygons]

I’m creating a chunking system, and instead of completely deleting an instance once it’s been created, I’d like to instead save it in a state that uses up as little resources as possible (reduce memory usage, stop physics calculations, etc.). Is there a way to do this? I’m looking for the equivalent of Unity’s .activeSelf.

[starmaq]

Is re-parenting the instance to ServerStorage or ReplicatedStorage a good idea? It would deffintely take way more less memory since it’s no longer visible and if any scripts are included they won’t run.

[sevenpolygons]

That’s what I assumed. I don’t think physics calculations are done in ReplicatedStorage, so that’s probably the way to go. If anyone has any further insight into this, I’d appreciate it.

[GameTapped (GTGaming)]

I saw this post a while back but haven’t done any experimenting to it’s affect yet.

PartCache, for all your quick part-creation needs

I’ve just finished designing and testing a little module I’m calling “PartCache”. This module is used to make the illusion of quickly creating and destroying parts for stuff like laser beams and such. This module uses CFrame to its advantage to work, since creating parts with Instance.new() can get very laggy. Here’s a stress test. I have 64 sentries here each shooting up to 10 bullets per second. It’s completely lagless! After zeuxcg made a post on a thread talking about how updat…

Basically what I gather is that setting the CFraming of objects to a far away location, is more performant than changing ancestry, or re-parenting.

[mishajones]

An option would be setting the instance’s parent to nil and then reassigning it to a DataModel descendant once you need the instance again. This way, it will not interfere with other stuff until you want it to.

You should change any objects’ properties, if possible, while they have a nil ancestor for optimal performance results.

Note: Any events prevously connected to that instance would have to be manually disconnected.

[Quenty]

Just curious. Is there a reason streaming can’t solve your problem?

[sevenpolygons]

The world is broken up into chunks. My code relies on the entire chunk being available, and since there’s no way to stream in/out entire models at a time, there’d be no way to ensure that the entire chunk was available. Additionally, this chunking system avoids the high network activity that streaming causes, and since chunks are being loaded in very often, that’d cripple the player experience significantly.