When you import Vue terrain objects or plants,etc, which renderer is used?
Thanks for this info. I was wondering how this could be done using the G buffer but I preferred using EXR as opposed to RPF - but you've answered that obstacle.In general, our workflow was to output a beauty pass in Lightwave (or Vue) to EXR with all the useful buffer goodies you can embed in the format (depth, motion vectors, etc.,) and then render the scene again in Vue with all lighting options disabled, and outputting to RPF to get the coverage channel, which can be used to anti-alias the Material ID, Object ID and Depth buffers. After rendering was completed, we used Fusion to merge the RPF data with the EXR--the reduces the file size overhead significantly because you can use lossless compression for all the channels within an EXR, and speeding up your comps (especially over a network.)
Yes, for us, version 8 was where it really took off for full 3D environments. Prior to that, we mainly used Vue for matte paintings. Since version 8, Vue just kept getting better and better.
This was probably my favorite use of Vue on a Box job:
I think we were using version 9 for this one. I set up some of the Vue environments on this job but most of the real heavy lifting is Ken Wilder's work.
Yes, the Box used Vue on a handful of jobs in the Box. the 'Rancor in the Wild' from Star Wars Kinect is another notable.
(We did the opening sequence in Vue and LW--most of the rest of this clip was done in engine. A couple of other shots in the 'documentary' were pulled from other pre-rendered LW footage we did for the game but no Vue there.)
Yeah, we've got Onyx TreePro - bough it (I think) in 2000. I've been asking them to have animation export - simple object export like they have for their Bamboo module - but they've never implemented it. I know they've got something like it for Max using TreeStorm, but they can't bring themselves to do it for the standalone modules. Object export for a sequence would be clunky, but still better than what they've got.Just to be clear, the very first tree you see in that segment was modeled using Onyx Tree and LightWave Modeler. Onyx is an ancient tree modeling program and the interface really suffers for it, but I still use it from time to time when I need to create a good 'physically correct' tree model quickly. The fruit was modeled and shaded in Lightwave and I think I used Random Cloner to populate it on the twigs of the tree. That was pretty much the end of my contribution to that segment.
Thanks for this info. I was wondering how this could be done using the G buffer but I preferred using EXR as opposed to RPF - but you've answered that obstacle.
I've been wrestling with purchasing Vue again - we stopped at Vue6sStream - but Vue11 seems to be working better with better flicker controls and integration. I'm still debating on whether to save a little cash and go the Infinite route or go all the way with xStream. Decisions, decisions.
Yeah, I remember the previous thread about this. It IS reprehensible!I've been generally very impressed with e-on software right up to version 11 when they decided to bait and switch with the licensing. It's really, really aggravating that you now effectively rent any network nodes (anything that gets a floating license, it seems). The license server now has a fixed one-year license that is only maintained if you keep up with maintenance (339 USD) or pay them an annual renewal fee (199 USD). Without that, you'll be dead in the water. It's reprehensible, and adds risk if e-on close up shop - you'll be dead in the water with no way to keep running. Also, even under maintenenace you'll need to pay to upgrade each and every render node install as well (it used to be that maintenance would cover everything and you'd have perpetual licenses - now it's the maintenance fee of 339 USD plus n * 30 USD or so for 'n' render nodes to keep everything up to date). That 30 USD per node doesn't sound much until you realise that only the node-locked host application is able to avoid the time-bombed annual expiration; you're renting everything else based on the lifespan of the license server.
I'm so pissed off by this, that I'm struggling to recommend Vue unless you can make serious money of it (to the point where the doubling or more of the maintenance or upgrade costs are a minimal concern) or that you can do everything on a single node-locked machine that isn't subject to the license expiration.