It seems like it was the terrain file corrupting as it was only 66kb. Whereas the terrain file in the exported game you sent StarFire a while back is 5.26mb.
If you have a backup:- Locate the .ter file from the backup and copy the file
- Go to the directory with your scenefile. Underscore the terrain file that is broken.
- Paste the terrain file from the backup into the folder.
- Rename the terrain file to match the scene file.
- Load your scene and it all should be there.
If you do not have a backup:Let me know and i can send you the file we have stored on our machines from the exported game you sent us.
CauseThis error is usually caused by ram usage exceeding the 32bit limit. Or can happen as a random crash. we haven't seen this one much though, mostly ram limits due to constant scene editing. When the scene loads, its around 1.3gig used which is fine. But if you go over 2gig, then there may be problems approaching. We do have 64bit being developed on the side and hope to see that in a couple of releases time.
Hence make backups
Performance TweaksI copied the assets from your exported game to fill the scene as you see it mostly.
However, on my computer the scene is running quite slow. This can be caused by:
- Heavy poly meshes. Try to setup some LOD stages(Tattie Tutorial) for distance control or set visibility distance(Tattie Tutorial) in the mesh properties.
- you have grass set on a density of 2.0, we use around 0.3-0.5. Even new modern games don't have grass everywhere.
- Goto Scene settings and set the Camera Setting "LOD Bias" to around 0.5, instead on 2.00. I gained 15 frames by doing this. It makes the terrain and LOD distances pop in sooner and gives a better performance.
Hope this all helps you get up and running