Disappearing Terrain

Started by Jonathan, June 20, 2011, 06:54:05 AM

Previous topic - Next topic

Jonathan

Hi All - looking for some guidance here....I have just re-opened a TGO I have been working on and my terrain has disappeared (I used one heightfield and a make river shader). I clicked on generate now and the terrain has totally altered so my scene is not what it was. Any ideas (I had autogenerate unchecked - don't know if that makes any difference?). I also (when previously rendering this scene) discovered that when rendering in 1290 x 1068, the image maps I have been using for rocks have not been rendered onto the rocks (fake rock shaders). The image map works fine in lower res renders but not in higher res. I did have a "script error" appear at the time it was rendering.

Any thoughts welcome!

Thanks, Jonathan.
Every problem is an opportunity, but there are so many opportunities it is a problem!

Henry Blewer

Can you post the tgd file? Actuallly, you'd have to zip the whole project.

I would guess that the render camera and the image projection camera might have different image aspect ratios. This is just a guess...
http://flickr.com/photos/njeneb/
Forget Tuesday; It's just Monday spelled with a T

Jonathan

Hi - here is the attached zip file containing the project plus the jpg for the rock used on the fake stone shaders. Regarding the render / camera settings, I use 1.7777 aspect ration on quick and full renders. The image map for the fake stone shader works on the quick render, and full render (640*380), but not when I move up to 1900 x 1080. And I still don't understand why, when re-opening the project, my terrain has disappeared. When I regernerated the terrain (no changes to any settings), the terrain was completely different! Thanks for your help. jonathan.
Every problem is an opportunity, but there are so many opportunities it is a problem!

jaf

First, I would go to Heightfield generate 01 and turn "Auto generate" on. Or maybe you remember to generate the terrain each time?
(04Dec20) Ryzen 1800x, 970 EVO 1TB M.2 SSD, Corsair Vengeance 64GB DDR4 3200 Mem,  EVGA GeForce GTX 1080 Ti FTW3 Graphics 457.51 (04Dec20), Win 10 Pro x64, Terragen Pro 4.5.43 Frontier, BenchMark 0:10:02

Jonathan

Hi Jaf, tried it both ways and the terrain has completely changed :(
Every problem is an opportunity, but there are so many opportunities it is a problem!

jaf

#5
Have you tried moving your render camera higher.  It looked like it was "inside" some of your terrain geometry.  You can usually see that in the preview window -- pieces of terrain in the sky.

(04Dec20) Ryzen 1800x, 970 EVO 1TB M.2 SSD, Corsair Vengeance 64GB DDR4 3200 Mem,  EVGA GeForce GTX 1080 Ti FTW3 Graphics 457.51 (04Dec20), Win 10 Pro x64, Terragen Pro 4.5.43 Frontier, BenchMark 0:10:02

bobbystahr

I always make a note of the seed value in the Generate tab if I'm using a non default value which seems always to be 22328 so I can re-establish a scene that's gone nuts on me.. ...
something borrowed,
something Blue.
Ring out the Old.
Bring in the New
Bobby Stahr, Paracosmologist

Jonathan

Hi Jaf,

When I first created the terrain, the camera was above the terrain - the issue was that when I re-opened the project, the terrain had changed - it is possible as bobbystahr points out that I might have used a different seed, and it defaulted to the standard setting - something that needs addressing by Planetside, as all fields should be saved with the project - I am going to try again, changing the seed, but making a record of it. Thanks for giving it a try though. I will report back!

Jonathan
Every problem is an opportunity, but there are so many opportunities it is a problem!

Tangled-Universe

Did you try creating a new (default) project, changing the seed value, saving the .tgd and the re-opening it?
I have never seen before that the seed value wasn't saved.

Oshyan

The seed value should always be saved with a TGD. If you can reproduce a problem where it does not save please let us know the exact steps you followed and we'll look into it.

- Oshyan

Matt

#10
It might be Heightfield Make River that's at fault. I think it might have a random element that doesn't get saved. We've decided not to recommend using it, and it will become a hidden node in future versions.

If you do use it, save the result to a heightfield file (.ter)
Just because milk is white doesn't mean that clouds are made of milk.