@Vegi-mite

Check out Silverblade's homepage to see what means when he says "I am sick" and then check out this entry on Wikipedia before talking about laziness.

Quote - Olivier, I've seen your tut at C3D. I just imported one of the preset terrains that come with GC2, with 2 erosion maps. They are called differently, but when exported, they are 100% the same. And when I use the map as a mixing function in Vue (object parametric), it looks wrong. The masp are supposed to be sediments flows, but when used in Vue, it separates the terrain in two halves upper and lower halves, while the upper half does show some of the sediment, the lower half is wrong, material is applied to both rock and erosion.  The bmp, set to automatic or flat does the same.
I'll try and post some screengrabs later, might be easier for you to see what I mean.

If you use mixed materials, go to the Influence of Environment tab and uncheck "distribution of materials dependent on local slope, altitude and orientation". I think it is the cause of your problem.

Excellent image SilverBlade.
The movie was aired on French TV last Sunday.

I have had a similar problem with a scene that had a complex ecosystem and a dynamic one.

A preview render lasted 11 minutes, most of which spent calculating the dynamic ecosystem, while it only took 38 seconds in Vue 7.21.

The object looks great, but I am a bit more skeptical on the depth of field.

Which lens settings were you using?
Shallow depth of field occurs with long lenses and/or when the focus is very close. If you apply it when it is not the case, it still looks nice, but a bit odds.

I have had lots of bugs with V7.4 and a 8800 GTS board, including this one. I ultimately went back to 7.21.

Maybe try to push the instand draw/background draw quality to the max in the preferences?

I used it too with great results. Now using version 2.

Be aware, though that ImageSynth works better when used on certain types of textures. It may be very good to make tileable pebble textures, but a bit tougher to use if you need semi regular structures.

Also note that base images with strong lighting differences (incident lighting) are almost impossible to use.
 

Same problem here.

Models are displayed all greyed out in V7.4. No display of clouds.

When applying some options, V7.4 crashes the Windows display entirely. It even manages to crash the Photoshop CS4 display!

I made tests with Various NVidia display drivers, and had many troubles with some.

To summarize:
175.16 (Open GL 1.1): Vue 7.4 crashed upon loading (6.6 displays a warning)
175.19 (Open GL 2.1): Scene are displayed without textures Tests made yesterday night with these drivers and version 7.21 were far better with a full texture display. Vue 6.6 displays the scene properly.
185.85 (Open GL 3.0): Very unstable, improper display.

Worse still: I went back to the previous version and the display is the same in it!

Uninstalled, reinstalled: same problem.

It seems I saw a thread about performing a full uninstall, but I cannot remember where.

1. Overhangs, caves and tunnels indeed. With voxels or normal maps

Other features that already exist in Geocontrol 2

1. realistic erosion systems, ideally applied to procedural terrains
2. realistic terrain formation
3. material masks applied to specific terrain features: rocks, eroded areas, rivers
4. winding roads

I have played around with towers on terrain recently. One effective way to make sure an object is well placed is to work in two stages:

• place it roughly in the 4 view, using the displayed terrain as a reference (might not be accurate)
• create a specific camera. Center the object in it. Rotate around the object and make test renders of the junction.

Quote - I see a few answers with text:

"...6 GB or 8 GB memory for VUE..."

Is it a JOKE ???

This is far from being a joke. I have spent the afternoon trying to work with Vue 7 on a Laptop that has 4GB of ram under Vista 32. I had a good number of OOM (Out Of Memory) errors, while I had almost forgotten their existence with my 8 Gb 64 bit system.
If you want to work with large (2048+) terrains with multiple textures, use large imported meshes or do both at the same time, you need 6 to 8 GB of ram and a 64 bit or you can expect a wild ride.

I noticed, however, that Vue crashed after eating about 1.4 GB of ram, even if the system had some memory remaining. I wonder if there is a way to allot the normal 2 GB to Vue, either in Windows or in the Vue preferences. Have not found it.

This works on flat terrain. On mountainous ones, you need to add support for roads. Geocontrol 2 has a good ability to make roads over difficult terrain.

Found it yesterday. It is owned by Dax Pandhi, the Vue Beta tester already discussed here: http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2770599

A nice bookmark, especially as he seems to be wanting to add new tutorials regularly.

I have made another test with an image found at www.cgtextures.com.

I am still using displacement textures generated with CrazyBump on this one as well.

I have placed this mossy stone wall texture on my website. I included the diffuse and displacement textures. I used the 16bit displacement (found the option in Crazybump) so the file is in tiff format and quite heavy.

Quote - Offrench: CrazyBump can also create 16bit displacement maps out of a diffuse map, did you try it in Vue? Your 3rd example is very convincing.

I do not currently use the latest version of CrazyBump (mine is 1.05 I think), and have not found this option, but I will give it a try and further fine tune the texture to get the best possible looking result.