Subtle terrain import bug

[angus.wood]

When creating a terrain there are certain circumstances where the imported terrain becomes corrupted and sometimes leads to an engine crash.

 

Steps to reproduce.

 

* Create two height maps which are different. Any difference will do

* Add the first terrain to Unigine, saving the .ter file to "anything.ter"

* Save the project

* Restart Unigine

* Delete the terrain node.

* Add the second terrain to Unigine and saving the ".ter" file as the same filename ("anything.ter")

 

The terrain will display as corrupted.

 

The console will log errors " Compress()::zlibCompress(): Can't decompress <x> bytes in to <y> buffer"

 

The SDK I'm using is the last 1.0 version. 

 

 

 

EDIT: This report looks like it is the same issue; https://developer.unigine.com/forum/topic/2945-solved-strange-terrain-issues-from-imported-heightmap/?hl=heightmap#entry15818

[silent]

Hi Angus,

 

Yes, this is a known issue. It still can be reproduced in Unigine 2.0 alpha. Unfortuantely, we don't have any solution to it yet.

 

Sorry for the inconvenience caused.

[angus.wood]

It seems to me that the .terNNNN "anything.ter0000" file is held open even after the node has been deleted. Reproduce-by: add heightmap, save terrain, remove node, attempt to delete .ter0000 file. Under Windows the file can't be deleted as it's still open. 

 

If the terrain is saved with the same name, per my first post, the likely outcome is file corruption. Perhaps this is the root cause of the bug.

[silent]

Yes, this bug exists only on Windows platform. Hope it would be fixed in the next SDK update. Currently we don't have any solution to it, sorry.