One of the terrain files don't load. Can you send me your scene? (both .workspace file and the associated folder with the same name). You can send it via email (licu at quadsoftware.com) or, if it is too big (over 10 mb), drop me an email and I will send you a FTP account to upload it.

I've sent you an email right after I've received the map from you (it was probably caught in your spam filter).

Seems that the zone area data is already missing from the scene you've sent. Here is the original email:

"The scene data you've sent doesn't contain TerrainZone (12) file (the one that gave you the error). You can check this by looking into Valley_Alicu\Terrain folder. You will see that TerrainZone (12).tdata is missing. This name is the internal name. Probably in the UI you will see this as TerrainZone11.

Did you save the scene again after the error occurred? Let me know if you still have the scene with this file in it. I will need it to test why it didn't load."

I've received the map and indeed the terrain zone data is invalid. It seems that the writing stopped somewhere during saving the color layers (or immediately after). I cannot figure out from data what went wrong, I just know that somewhere the write stopped.

Can you remember what was done differently for that terrain zone? Was it in swap, did it had different layers or editing in any way compared with the other zones? Do you remember the last operation you've made before the save? Did you ran out of disk space at any time?

I am sorry but I cannot restore your data from that zone since most of it is missing (as you can see the TerrainZone (12).tdata file is much smaller than the other .tdata files).

But it would be great if we can figure out why this was happened as this may be a major issue. Fortunately no other clients reported this kind of files corruption so maybe was just an isolate incident. We will study the file more maybe we can figure out what happened. Any help is greatly appreciated.

I had no "crash" for a long time, errors, freezes of some sort, but not the program dying and disappearing without warning, so I didn't saw messages you speak about, maybe in the console (I don't look a lot at it I admit), you think there are logs for the console I can retrieve and send you ?

Edit : about what happened .. well I had plenty of space (some hundreds of Go left) and plenty of ram avaiable (I have 8 Go) ..
I can't remind if I swapped but I can tell that my work HDD are SSD disks, they are working fine, no errors as for now.

In fact, I was working on the project one day, saved, and when coming back it loaded like that.

The only thing that I can think should have caused problems is my trying at import of colada mesh found on google sketchup gallery with very few success.. I added mesh, deleted it, added again, in an attempt to get it working well in Grome project.
But none of my tests were done on the area 12 that is missing, the area where I tryed some integration are ok.

As for colors .. I don't remind having problems at all in this area, I did lot of tests on the entire project, going back after each bad try but in the end when getting something I liked, there were no troubles and I begun to work with grass and tree integration.

The missing area incident happened long after I finished with textures.

I thank you for confirmation that project is wrecked, at least I'm not waiting anymore with false hope, I will redo it from scratch then ..

Last edited by Finstern on Mon Feb 27, 2012 12:05 pm; edited 1 time in total

The console will usually show up automatically when there is an error (unless you choose not to, from an option in the preferences dialog).

What is really strange is that if an error occurs when a zone is written other files (for example the project file) should also reflect this error. But it doesn't. We are still looking to see if something that goes wrong when writing the zone goes unnoticed.

Did you had a low disk space at some point during that period? This may explain the zone not being written completely (but again, this is not the last zone in the scene, so why did it happen only to this)?

Was this zone edited as any other zone from that scene? It is very strange that all the other zones are intact.