I'm sorry, Stewart. I'm not very good at explaining what I mean (which is why I stopped writing tutorials).

This is actually more involved than my previous posts would suggest. Guess I'm just used to working with scale, so I overlook stuff along those lines.

First, I should've pointed out that when increasing the res of the terrain in the editor, you have to go to the size thing on the upper right and adjust it to match the editor. That is, if the editor is set to 1024, the actual size also needs to be 1024. And while I'm thinking of it, the inverse will also work. That is, leave the terrain at 256 and reduce the overall scaling of your ecosystem.

What I was trying to get at before, is that this isn't about size specifically, its about the ratios between your terrain, the stuff in the ecosystem, and the details on the driving map. In other words, the scene you set up has a ratio that appears to have too low a threshold for Vue to handle. That's why I suspect that instead of being a bug, this is a limitation of the code being used. Whether it's a bug or not, I DO agree that it's something e-on needs to work on. The scene you have isn't unreasonable... it should be able to work as is!

Anyways, until e-on does solve the problem, we need to work around it. Unlike graphs and nodes, this is something I'm used to dealing with. If you have trouble thinking in terms of 3d ratios, I'll be glad to try and help. As I noted, I'm bad at explaining... but I'm always willing to try to help.

Oh yeah, in case you haven't noticed... I'm absolutely positive this problem is about ratios. Not density, nor bitmap res, only ratio. Of course, that doesn't mean we can't use those as a work around.