1. #11
    dasraizer's Avatar Senior Member
    Join Date
    Apr 2014
    Location
    UK, Isle of Wight
    Posts
    1,195
    Hi

    The base worlds object data is stored as part of the base world map data, outside your track save data, so modifying or moving any base world object, although it wouldn't add to complexity, will add to your tracks file size, as it will need to store this extra information + the base world object ID affected, it would be cheaper in terms of file size to just add the new object and clear the base world ones with the area clear tool (if your clearing more than one object), so yes setting the building to invisible, if your doing more than one object would probably add to your tracks file size.
    Share this post

  2. #12
    Originally Posted by dasraizer Go to original post
    Hi

    The base worlds object data is stored as part of the base world map data, outside your track save data, so modifying or moving any base world object, although it wouldn't add to complexity, will add to your tracks file size, as it will need to store this extra information + the base world object ID affected, it would be cheaper in terms of file size to just add the new object and clear the base world ones with the area clear tool (if your clearing more than one object), so yes setting the building to invisible, if your doing more than one object would probably add to your tracks file size.
    Cheers fella that makes sense now. Really appreciated
    Share this post