Alex Curtis wrote:
> Hi Guys,
>
> Right I have got the File IO part done (using k3d IO of course) -> Needs
> to be a bit more robust but will do for now.
>
> The next stage is getting a render (initializing an external render
> engine) done using a geometry object.
>
> Now I think the best way of doing this, is to create a new document (one
> you wont be able to play with). this document will set up with the
> geometry and camera specifics etc. Then k3d render facilities will be
> called using the document and the chosen render engine (rEngine
> selection bit done).
>
> Put simply can I do this.. create a new document? ... Is this the best
> way?.. I could go the root of creating render input files etc, but thats
> a lot of work to cover all k3d supported render engines. I may as well
> use stuff already provided.
Hi again!
You should evaluate performance. I guess you mean creating one document and
modifying it, but not creating a new document each time the user changes something.
What I would do is generating the material in the original document and hack the
render settings of the new document to used this material created. Instead of
trying to migrate the whole material to the new document. (well, i guess this
could by heavy on certain cases)
I don't know if you should hack the RenderManEngine node or the
AqsisRenderManEngine.
Let's see Tims opinion.
Cheers!
JoaquĆn
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development