Attached Link: picture showing the problem

I'm having trouble with grass not populating (dynamic population) in the distance. If I use a different camera that is closer to the area, the grass populates as expected.

This material has several ecosystem layers.

Is there some setting I'm missing or is there a workaround I can use? This happened before when rendering at reduced resolution, but it cleared up when rendering at full res. Now it's breaking at full res too.

I'm using this in LightWave via xStream, but it happens when I render the scene in Vue Standalone

Win 7 64 Home Premium - i7 2600 not OC'd- 16GB RAM - nVidia GT440

Vue 10 xStream - Build 10008479

Dynamic population works like this: the further to the camera, the less detailed the instances are, all the way to billboards for the farthest instances. Here, I see instances in the backgroud, it just doesn't look good, because the grass is not following the shape of the terrain, you can change this by changing the direction from surface of the ecosystem towards Perpendicular in the Scaling and orientation tab.

Thanks for the input. I tried adjusting the perpendicular setting (I set it to 100%) and it did smooth out some of the grassy areas, but the big choppy section stays the same.

If I manually populate it, I can render the grass, but the scene crashes when I turn on the other layers of the ecosystem.

I think I'll try painting the grass in next. This is very frustrating. :)

 

Thanks again for taking the time to help.

I'm using Vue 9 and am also having a problem with Vue not fully populating an ecosystem. Let's say my camera angle is 30 degrees. When I click to populate the screen only the lefft 15 percent is being populated, other than at the closest point there are no plants appearing in the right half of the image. Any idea what could cause that?

Renderholic: are you talking about the final render, or the OpenGL preview of the ecosystem? It's possible that the ecosystem is not previewed in full in OpenGl, it depends on your ogl settings. If it's in the render, then there must be a bug somewhere.