Crash saving a large world

[luke.errington]

Using the new large-world version of Unigine editor (with double-precision), we wrote our own script to import height maps and diffuse textures for terrain tiles. Each terrain tile is 2049x2049 with a step of 10.412. There are 15x15 tiles. This makes for quite a large world ... roughly 320 km x 320 km, where 1 unit is 1 metre.

 

While importing these the terrain files were saved to disk. This allowed Unigine to keep its memory usage to around 300 MB of committed memory, which is good. The statistics report around 1500 MB of textures. A side problem was that the virtual memory usage was around 2.4 GB, so this will cause problems on 32-bit systems, but this was OK for us (for the moment) because we could just switch to using the 64-bit version of Unigine.

 

Moving around the scene was quite jerky as terrain was paged in, using far planes of 50,000 and 100,000. A far plane of 1,000,000, attempting to view the whole world, crashed the computer and required dropping the power :blink: .

 

Anyway, with the world created, the desire is then to save it so we can use it in our application. Saving the world (via the editor, which calls world_save) caused Unigine to crash. There was no further debug information, and we don't have source, so can't tell you where it crashed. This is the big issue.

 

Sorry that I can't provide the source data, but it is well over 2.5 GB ... however, empty terrain and blank diffuse textures should probably still be sufficient to reproduce this.

 

(Incidentally, this wasn't just to test capabilities ... this is representative of the world sizes we require, if not on the small side ... and we require better than a 10 m step :o )

[manguste]

Using small tiles does not look good, as geomorphing won't work and there will holes between vertices in different tiles. Try using 8192*8192 or 16384*16384 tiles.

 

Could you provide a log file?