|
|
thanks, that's what i'll try. i'll let you guys know how it goes.
Fabian BRAU wrote:
> This is excatly what I said :) And now with the triscan macro
> we can do udo very easily and quite accurately :)
>
> Fabian.
>
> >
> > Ryan,
> >
> > Why not change the pov files to inc files, then make a UDO file for each of
> > your inc files. The UDO file is very simple to create. I have several inc
> > files that I use in this manner. I use them for parallel-ray spotlights and
> > many architectual objects that I use often.
> >
> > ryan constantine wrote:
> >
> > > here's the situation, i'm creating a complex model (over 200 primitives
> > > so far) and i would like to save the individual parts as .inc files
> > > instead of .pov files. of course, i have already been saving those
> > > parts as objects instead of scenes within moray, but how can i get moray
> > > to #include a previously saved object instead of adding it to the
> > > scene? does merge object automatically add it to the scene? is there
> > > another way to add an object to a scene? if it's in the docs, point the
> > > way.
> > >
> > > the main reason i want to have the .inc files is for distribution. some
> > > of the parts are so complex that nobody will want to mess with them
> > > anyway and putting them in the main scene file gets really messy! plus,
> > > i only named major components so everything minor is cylinder136,
> > > cube078 etc.
> > >
> > > also, is there a way to take advantage of povray's programming elements
> > > within moray or will i have to do that by hand after model creation?
> > > thanks,
> > > ryan constantine
Post a reply to this message
|
|