This has a bit to do with the parenting of the texture to the object,which is assigning a shader node,and then choosing the mode of the parenting; i.e. World Parametric for instance. What seperates the high-end applications from the more affordable hobbyist apps (besides price LOL)  is a LOT of programming which means more tools and more options to said tools.
Textures by nature are dependent on the "view" used to map the textures.World Parametric vs. Object Parametric for instance, will appear different in Vue.  Add motion and render an animation,and you have this come into play as a sort of texture swimming or artefact noise.The object keeps it's place, but the textures tend to stretch to fit the camera angle.Trust me, high end apps,like Maya or 3D Max, have this problem.I would try differing mapping nodes in Vue and render very short sequences and see what happens.I'm very new to Vue,and I'm still figuring out the mapping,but this holds true in most every 3D program that uses texture nodes.

Vue has grown tremendously since Vue4.It is becoming an application used by the large production houses for film work.E-On has brought these features to us at a very affordable price.Infinite or XStream is about 1/3 the price of 3D Max or Maya.Terragen has an awesome texture rendering engine,but it's still very hard to add plants,objects,etc Give E-On a little time and Vue will rival the high end applications one day.I'm sure rendering and mapping tools are always being looked at the folk at E-On as improvements for the next major build.Till then, just try differing modes and work with the bump mapping,too. I just went through this with mapping the Dead Tree I'd messed with in the plant editor recently.  Happy rendering!