projector - storing nested projector data
Bottom line: I think the projector is storing all the data of the nested projectors and causing my world and blueprint files to grow exponentially.
I was playing with Nanobot build and repair system mod (https://steamcommunity.com/sharedfiles/filedetails/?id=857053359) and I was working on an idea for a multi-projector self-repair system. (each projector held a section of the ship up to the next projectors, 5 total sections, the reason I was trying this: the offset limits to the projector could not get the projection to match up to the ship I was building with the currently limited projector offsets (large ship ~200 blocks long ~100 blocks wide).) and I noticed while I was working on it my computer kept getting slower and slower, then started to take 20+ minutes to save. (I7 5820K, 16 gigs of ram, GTX-980) so I went to look into why and noticed my save file was ~11gig, and the blueprints for each section of the ship were huge as well, sections:1.7gb, 3.3gb, 619mb,2.2gb, 2.0gb.
I get how the logic for the projector works to save it, but essentially my idea breaks how the projector works, if you all have a fix for having a ship divided into smaller separate projectors that hold the information for the projectors next to them without exponentially growing the world I would love to hear it. but I know that if this concept works in mp, someone could easily take it into a server to exponentially grow the world/potentially crash the world which is the reason I am mentioning it here.
create a ship with 2 projectors
step 1: blueprint ship, apply blueprint to projector 1
step 2: blueprint ship, apply blueprint to projector 2
- repeat steps 1 and 2 until your world/projector files are huge
The file continually grows and grows as the projectors will hold all projector data for 1 and 2 in a continual growing nested piece of data, even though you should never get to most of those other blueprints within them.