|
»
« Return to Thread: LuxRender output module first results.
Re: LuxRender output module first results.
by Daniel Scott Matthews
::
Rate this Message:
On Sun, Jun 21, 2009 at 3:42 AM, Timothy M. Shead <tshead@...> wrote:
>
> Joe Crawford wrote:
> > On Sat, Jun 20, 2009 at 2:00 AM, Daniel Scott
> > Matthews<dsmatthews@...> wrote:
> >> Tim has whipped up another render output module.
> >>
> >> Example output can be seen here:
> >> http://www.k-3d.org/wiki/User:Dsmatthews/LuxRender
> >
> > Wow, that's really cool. I really want to try it. Thanks for showing
> > the example, and thanks to Tim for making the plugin.
> >
> > Daniel, did you have to do any crazy programming stuff to output with
> > Lux or can it be done using the plugin through the UI in k3d?
>
> Daniel has been doing a lot of the legwork for me, manually hacking the
> K-3D output to make it look good, then sending me the results so I can
> code the plugins to match (this is the type of collaboration I
> appreciate, BTW). I just caught-up with his latest round of changes, so
> yes, you can produce similar results using just the UI. See
> http://www.k-3d.org/wiki/LuxRenderEngine for notes.
>
> At the moment there's no material support (everything's a neutral matte
> surface), and I'm working to get the camera field-of-view to match K-3D.
> We have rudimentary support for disk, polhedron, and sphere primitives.
>
> Cheers,
> Tim
>
It is one advantage to being on the other side of the world, while you
sleep, I tweak. :-)
A good example of how globally distributed teams can operate to speed
up the code then test cycle.
Reading this, http://www.luxrender.net/wiki/index.php/Scene_file_format
has been very helpful. But some time you need to try a few different
settings across a range to get a feel for how they effect the final
image. I'd like to be able to automate that, take a scene and generate
multiple versions with incremental changes to variables. Two at a time
is the most that would be usable because you can look at the results
in a grid. These grids would be good for tweaking materials and camera
settings as well as providing documentation.
I may just script it in gedit.
------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development
>
> Joe Crawford wrote:
> > On Sat, Jun 20, 2009 at 2:00 AM, Daniel Scott
> > Matthews<dsmatthews@...> wrote:
> >> Tim has whipped up another render output module.
> >>
> >> Example output can be seen here:
> >> http://www.k-3d.org/wiki/User:Dsmatthews/LuxRender
> >
> > Wow, that's really cool. I really want to try it. Thanks for showing
> > the example, and thanks to Tim for making the plugin.
> >
> > Daniel, did you have to do any crazy programming stuff to output with
> > Lux or can it be done using the plugin through the UI in k3d?
>
> Daniel has been doing a lot of the legwork for me, manually hacking the
> K-3D output to make it look good, then sending me the results so I can
> code the plugins to match (this is the type of collaboration I
> appreciate, BTW). I just caught-up with his latest round of changes, so
> yes, you can produce similar results using just the UI. See
> http://www.k-3d.org/wiki/LuxRenderEngine for notes.
>
> At the moment there's no material support (everything's a neutral matte
> surface), and I'm working to get the camera field-of-view to match K-3D.
> We have rudimentary support for disk, polhedron, and sphere primitives.
>
> Cheers,
> Tim
>
It is one advantage to being on the other side of the world, while you
sleep, I tweak. :-)
A good example of how globally distributed teams can operate to speed
up the code then test cycle.
Reading this, http://www.luxrender.net/wiki/index.php/Scene_file_format
has been very helpful. But some time you need to try a few different
settings across a range to get a feel for how they effect the final
image. I'd like to be able to automate that, take a scene and generate
multiple versions with incremental changes to variables. Two at a time
is the most that would be usable because you can look at the results
in a grid. These grids would be good for tweaking materials and camera
settings as well as providing documentation.
I may just script it in gedit.
------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development
« Return to Thread: LuxRender output module first results.
| Free embeddable forum powered by Nabble | Forum Help |
