Thanks for the hint! After messing around a bit, I found a solution in 3d Coat. When exporting an object, there is an option at the bottom of the dialog box named: create padding. It fills all the gaps between the texture islands. This solves the problem.

Quote - It'll have GPU rendering, why not use those thousand of graphic cores? lol

Or real time rendering like in computer games. (like Crysis-Sandbox, for example)

Crysis Sandbox vill render everything in real time, like nice water waves, wind etc. so I'm looking forward that Vue implements such a render environment...at least for preview rendering!

I started a thread with that suggestion a few years ago. The answer from E-On was "we do not have the same number of developers". 

Otherwise, realistic terrain erosion (like Geocontrol or World Machine) would be nice. A coherent water system with rivers or lakes would be interesting too.

Plant Factory was a promising app, but now that E-On has announced the pricing, it suddently looks less interesting.

http://www.theplantfactory-tech.com/index.php?post/2013/06/03/Plant-Factory-%E2%80%93-Product-Lineup%2C-Pricing-and-Pre-Release

Quote - A high level Bryce work would be an average Vue one...

I am not sure this is true. It depends on the scene. 

I think there are still things that Bryce do better than Vue in some specific aspects such as reflexive, metallic or water surfaces. It has a very clean antialiasing on these and they look very nice.

I am a long time brycer (started with v2.1 back in 1996) and it took me some time to give Vue a real try.

I tried Vue 1.2, then 3 and could not get past a few tests. I was used to Bryce and the Vue interface looked ugly and unintuitive in comparison. On top of that, it was quite buggy compared to Bryce and some features had obviousely been copied on Bryce.

I started using Vue with V6, mainly because Bryce had not been developed for a long time and lacked essential things such as soft shadows, realistics skies and ground vegetation. 
I got used to Vue and rarely looked back since then.

A few years ago, I did a feature comparison based on Bryce 6 vs Vue 7.
http://www.virtual-lands-3d.com/bryce-vs-vue.html

Many things have changed in Vue since then. The viewport previews are much better since V8 and the flickering I talk about is almost gone. The terrain editor is better (though I still feel the Bryce one was excellent)

Some things are still the same though, but the number of unique features of Bryce (those Vue does not have) has continued to dwindle.

One thing though. I considered myself an expert user of Bryce, having delved in the Real World Bryce 4 books and tried to overcome its weaknesses in every way I could. I used light arrays to make soft shadows, custom objects to make grass, HDRI skies from photographs, terrains to model objects. Bryce is easy to learn and you can ultimately feel you can master it.
On the contrary, Vue is becoming more and more a 3DSMax like product, with loads of features everywhere and loads of numerical values you have to tweak, test, tweak, test to get results that many times are far from what you would expect.
Even following excellent tutorials like Dax Pandhi's for instance, does not guarantee you will get the same results.

You waste considerable time with Vue (I feel) because of this. As much time as I lost in Max tweaking render parameters in Mental Ray.

The manual is in the same league as the one of Max: it describes every function individually, but you don't learn what every slider does in practice.

Vue has a classical interface with loads of unhidden math. The Bryce interface was made by Kai Krause and the teams of Metacreations who pushed useability to its very limits, hiding the figures and letting the user play with it.

This has to be kept in mind as well as the price difference that is now enormous.

Maybe it is based on the same technology as ecosystems. 
That would be flexible, but not useable for smoke or water.

Terrain erosion "à la" Geocontrol would be nice.

A new plant editor (maybe outside of Vue) enabling the creation of plants from scratch.

Realistic water flow simulation.

And... well...

this: http://www.youtube.com/watch?v=Z7B3HnukQVQ

or this: http://www.youtube.com/watch?v=glNhizU1by8

or this: http://www.youtube.com/watch?v=MYVREWkYIr4

or even this: http://www.youtube.com/watch?v=uhm3JYX2h_k

And I don't need it to be in realtime.

Strange that different users have different default focal lenghts.

Mine is 35mm and I supposed this was the general default.

Try to set it at 17mm and you will get the same perspective distortion as with a camera lens... without barrel distortion, chromatic aberration or the awful lack of sharpness you get in real life!

E-On has apparently set up an automatic process that creates a new build every once in a while (apparently on a weekly basis) and posts the update to subscribed users with the list of bugs corrected.

Also, I have kept updates since build 10501339 and they are labeled as Release Candidates and not beta.

When creating selectors in Geocontrol, do you preview them (in red) before creating them?

Also, for selectors to work in Vue, you need: 

• either a terrain material that is set to "object parametric"
• or a distribution material whose projection is "from above"

Also, if you are using the method Shawn detailed, set the map size to 1.01, otherwise you will get problems at its edges. Also set your distribution map sizes to 1.01 to match the terrain size.

Which build of Geocontrol are you using?
I found the latest one (54) to be quite buggy and am still happily using build 36. 

If you have doubts about the files you generate, try some of the 3d terrains I provide on my website. 

It does not seem to be ONLY a problem of bump map settings.

Look more closely at the arms or leg of V4: the bump map is not properly aligned (or, more likely, oriented) with the character.

Check which version of OpenGL you have installed with GLView

With my former gaming video board (GTX 260), sometimes OpenGL would not work at all. GLView would announce that I had only OGL 1.1 installed, whereas the drivers should have installed OGL 3.

If there is something wrong with OGL, I would suggest to remove video drivers entirely (I use Driver Sweeper) and then reinstall the latest version, downloaded from Nvidia.

RAM is useful for rendering if you have some dynamic ecosystems in your scene.

In that case, you will notice that Vue will increase the amount of RAM used at the beginning of your render, when creating the dynamic ecosystems. 

I made my "Mad Gorges" (http://www.cornucopia3d.com/focus/OlivierFfrenchFocus.php?intro) scene in Vue 7 and was barely able to work on it with 8 gigs of RAM.
I can no longer render it in V8, 9 or 10 because I do not have enough RAM to handle the dynamic ecosystem. When rendering, Vue eats up all the available memory, which forces my PC to swap and reduces it to a crawl.

Vue 10 Infinite now is a rather stable version of Vue. 
I use a Quad Core with Win 7 64 and 8 gigs of Ram.

Most of the crashes I have experienced were due to:

• display problems with my former video card. The display driver would sometimes stop to work and leave me with a black screen  
  Hopefully these are gone with my new Quadro 2000 card.
• large ecosystems. When I populate large terrains with dynamic or classic ecosystems, I sometimes go beyond what my system can take and Vue eats all available memory, which reduces my PC to a crawl.
  e-On should perhpaps add some feature that stops processes that do this when it reaches 95% of the available memory?

Apart from that, Vue 10 renders very fast and has some interesting features.
 

Dylan Cole has made a few tutorial DVDs for landscape matte mainting.

http://www.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Daps&field-keywords=dylan+cole&x=0&y=0

But these are probably mostly dedicated to Photoshop work.