Creating a zone loader

[Alienhead]

I have a request, I'm not even sure this can be done editor side or not but I thought I'd toss it out there in hopes it is something that can be added.

I'm creating a zone loader, let me explain - I wish to be able to load and edit objects in the editor as normal. But some objects I don't want to have loaded at runtime, but rather load and place the object at my own choosing.   I could later parser the .map file and get these objects flagged for 'Don't Load'.  Now the editor would still load these objects and allow normal editing, placement, scale etc..

A mockup - 

Is this something that can be done user side? or would this require editor side work? Is it even something you would consider adding?

My thoughts and plans are:  for example,  I have a HUGE sky scrapper building with many many floors and rooms, the building consists of 1000's of objects but usually the player only gets to a fraction of these rooms per game session thus causing a huge load time delay for no reason.

I wish to still have the references to these objects and create a <please wait, loading> signal when player enters said area.   I should be able to parser the .map file and get the unloaded but referenced objects then create my own stream loader or<please wait> loader or async/mutex loader or something.

For large, open world - like games this would be a major step forward. This isn't something that I wish to do later on but rather a need for projects already facing this dilemma.

Any thoughts?

[Josh]

8 hours ago, Alienhead said:

I don't want to have loaded at runtime

Why? What problem are you trying to solve?

[Alienhead]

I'm trying to work around extremely long load times for maps with a large amount of entities. I wish to create a zone loading procedure. 

[Josh]

Okay, first step should probably be to determine exactly what is making up that load time, and whether the number of entities is actually the bottleneck, before we attempt to solve it with a complicated multithreaded system.

What are the load times, in debug and release builds?

• It's possible that JSON might not scale well, but I can't tell until I test.
• Textures load pretty much instantaneously, but may hit a bottleneck when they are being uploaded to the GPU. I doubt this is a problem, but have not measured at at scale.
• Mesh data should load fast, but there is a processing step when vertex data is converted to the more optimized layout that actually gets sent to the GPU. I don't think this is an issue, but maybe STL is running slow in debug builds.