next »

[TheSpaceMan]

I have reached a point in my game where level changing is once again in focus.

I could load my levels at start up, but loading them also include the fact that the physical geomatry is loaded, and collideable. It could work if i added every level to a different layer, but that creates problems with other things.

I am now considering loading every level on level change instead, adding a overhead on level changing but loosing the memory overhead and collision problem.

I am currently workign with ogre so adding removing models for a level is as simple as detach/add that node. The physics is not as simple. How do you guys do it?

[Flink]

We had the same thoughts with our eniteties in our editor to Boingo. We wanted to place the entities and create all data except for the physics data. So we had a generate_physics function in each enitity which were called when you generated the level instead of when the entity was created. This solution should work for you.

[Mikademus]

What about a queue? Do the fast stuff, and place all entities that needs physics in a queue and add one per frame or something do distribute the load and overhead. 

[TheSpaceMan]

I gave up overplaning it, each level is reloaded completly, all resources freed and recreated.