Forum Moderators: wheatpenny, TheBryster
Vue F.A.Q (Last Updated: 2024 Oct 26 8:50 am)
I, too, am a LightWaver. I have just ordered VP and will certainly conduct a lot of experiments, especially in the areas you highlight, since they are of critical importance to me. I'll post my findings. There is, of course, also the option of using RLA/RPF compositing, but I'd rather avoid that. The process usually takes longer and the cost of a good compositing program is rather hefty..for my wallet, anyway :( Unless LightWave can act as compositor? Hmmm... Btw, in the product description it says: "Complex geometries [trees] are automatically unwrapped with minimum distortion and exported complete with all UV mapping and texturing information in a format that can be read by other 3D applications. You can adjust the level of detail in the exported geometries and texture maps." (Note to self - buy a BIG harddrive) Brgds
I had to cut the files in several zips, sorry.
These files will only stay on my site until September 24, because I have not anough space to keep it longer.
Guitta
The tree's texture map is 54 by 12573 pixels(!), and it's a BMP, meaning 256 colors. No wonder, then.. :)
You can get the sphere looking proper by loading the bump map as a reflection map and inverting it. Yeah, it's a workaround.
With these renderspeeds it looks like I'll have to composite the shots, rather than rendering them all-in-one. I hope LightWave is up to it..
One suggestion. If you have Lightwave 7 (I forget if this works in 6). Go to the transparency layer of the tree and copy that texture. Go to object properties/render for the tree and click on clip map. Paste the texture you copied, making sure anti-aliasing is off. Use that texture and delete the transparency texture that you originally copied from. Why Vue uses uses transparency for the leaves of the tree as opposed to a clipping map is beyond me. It might have something to do with exporting to a pre 7.0 format (Xfrog does the same thing). But doing it this way created renders that take a LONG time. Try it as a clipping map and see how fast it now renders. Also in those exported objects that Guitta posted there are a few maps that are NOT used, They seem be used in the transparency layer of the objects though they don't do a thing. Remove them. I mean what kind of transparency would the land have..or the ground.
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
I recently purchased Vue-4 (now 4.12). I'm also a LightWave-7.5c user. Vue Pro (VP) looks interesting. Are there any examples of VP scenes loaded and rendered in LightWave (LW). The reason that I'm asking, is that many of the new features in VP, I can already do in LW. About the only really unique thing that Vue does is terrain generation and terrain texturing. Assuming that exported VP terrains and textures import into LW, are VP's procedural textures retained as procedurals or are they converted to image maps ? If the textures are converted to maps, how close are they to the original Vue renders, when rendered in LW ?. I've exported terrains and textures out of Bryce-4 and they load fine into LW. The problem is in the texturing. When rendered in LW, the Bryce exported image maps don't look much like the Bryce-rendered images, no matter what resolution that I export the maps. I guess that's my concern. If VP can't do any better than Bryce (for exported terrains and textures), then it's not much use to me. Any feedback is appreciated Knuck