Anyone have any suggestions to get this function to work again? I’ve tried all of the settings in 3D resolution limiter but nothing is working.
What exactly is the problem you’re experiencing? When you say the 3D view is “not working”, what doesn’t work about it? Does it crash or give you an error message, or go unresponsive? Do you simply not see terrain at all? Are there visual artifacts? We need detail to help. 
My first suggestion would be to try resetting the camera with the space bar. Often the camera just gets lost, especially when changing terrain size or scale (as the “coverage” of the terrain changes and thus the camera can be over terrain with one setting, and not with another).
- Oshyan
Thanks for the reply. I got everything to work by completing an uninstall/reinstall.
I know exactly what you mean, beacuse i have the same problem.
I think is a bug in the program.
When i work with the program, and want to see the result in 3D view,
i dont know how, but suddently this function seems not to work, and it dosent work at all.
The program dosent crash, only this switching 3D view has a strange malfunction.
But thanx for the tips there, it helps, if i uninstall and reinstall the program
again, then i can use the 3D view again.
But i hope that i dont have to do it every time i use it.
i geting bored of it.
Did either of you try Spacebar?
- Oshyan
“preview not working” is not decriptive enought for us to understand what is happening. I am assuming no message was displayed saying anything looked like “no device selected” or “press build button”…
So far, the only “problem” we know, associated with that decription is, pointing the viewing “camera” elsewhere and not at the terrain, or moving the camera below the terrain. For this type of problem, “spacebar” is the best answer.
If your problem is another one, please post some screenshot of what is wrong, and state what you were doing and what you expected to have happened. If it is a bug, we will reproduce it and note it down for termination in the next release 8) .
Yes, good added detail Fil. Why should you spend time to give us more info? Because if we can’t reproduce the bug (and we can’t yet), then it probably won’t be fixed! And I’m sure you do not want to have to be uninstalling and reinstalling all the time. 
- Oshyan
I think mine messed up at one time but the VIEW had just been pushed out of site.
Mandrake
Hi, like many people I use World Machine to create more true to life landscapes in Terragen 8)
I just had the 3D view problem described above, and thanks to JavaJones it was fixed instantly by pressing the spacebar. I was just considering re-installing also :shock:
This looks like an interesting forum, I might join if I think there is anything useful I can add.
Thanks again for the advice
Well, starting today, I lost the ability to view 3D also, so I figured I had beter start looking for a fix in here ASAP! Glad I did, prevented doing any excess work 
Thanks for this tip!!
It happenned to me to. It does seem like a bug at first- you click toggle 3d view, and there is just a blank white screen. Arrow keys and mouse dragging does not reveal anything 3d. There is clearly a heightfield becuase you can toggle back to the Top view and the preview/visualization box shows the map as well.
It turns out hitting space bar does recenter the view and reveal the 3d view.
This is a minor usability bug because quitting and restarting the app does not resolve it. It should be easy to check for this state when loading a new scene, or rebuilding a scene, and just to auto recenter if it’s off screen in the 3d view.
A minor issue with an otherwise very nifty program.
I would not favor an auto-center, at least not as default behavior. The reason this occurs is because you can adjust the scale of the terrain. If you position the camera on a terrain of large scale then lower that scale and build again, the terrain is smaller and may not be in the camera’s field of view. But it can be useful to use the camera as a reference point when making such changes, and having it auto-center would be a nuisance. At the least I think it could be an option, but not having it on by default would not solve the problem, and having it on by default would annoy me and could again cause some confusion. Being a more advanced user I suppose I would have no problem just turning it off, so it could be made default behavior. Perhaps Stephen has some thoughts on this. It is definitely one of those small issues that does come up regularly, so ideally something would be done.
- Oshyan