|
From: Dan Z. <que...@ma...> - 2007-03-30 00:58:47
|
On Mar 29, 2007, at 5:42 PM, James Walker wrote: > Dan Zinngrabe wrote: > >> 1. Style? >> 2. View Hint (this is how it was traditionally done with plug-in >> renderers in QD3D) > > It's my understanding that a view hints object is basically a way of > wrapping up, for 3DMF storage, information that would exist > elsewhere at > run time. For example a view hint can record the clear image > color, but > at run time the draw context object knows the clear image color. > > I'm leaning toward an object property on the renderer. I don't > envision > a great need to use it for some objects and not others. > -- > James W. Walker, Innoventive Software LLC > <http://www.frameforge3d.com/> > It's something that was renderer-specific back in the QD3D days. A good example would be material properties for one of the LightWork renderers, that sort of things was stored in ViewHints and could thus be saved in a 3DMF edited or viewed with that renderer. Since the per- pixel lighting would still be pretty much renderer-specific, using the ViewHints makes some sense to me. |