Klaas Nienhuis
Klaas Nienhuis, a 3d-generalist, projectmanager, programmer and a guy who figures stuff out.
Twitter updates
- @SketchFab i was wondering where that traffic came from! Thank's, this will help to convince my clients to start using this even more. 1 day ago.
- Our model of maison d'artiste on @sketchfab is picking up some crazy traffic lately: http://t.co/DF0gPodh @dpianimation #webgl 1 day ago.
- Had a great talk with @namshee about @gathercontent, our experience with it and ideas for the future 1 day ago.
- RT @DpiAnimation: DPI is kennispartner van @nrc! Lees ons artikel over #configurators & #masscustomization op het NRC-blog: http://t ... 4 days ago.
- @SketchFab sure, thanks for the link. 1 week ago.
- @SketchFab done already! Klaasnienhuis.nl Any plans for a private viewing environment 1 week ago.
- Maison d'artiste by klaasnienhuis http://t.co/DF0gPodh via @sketchfab @naimuseum 1 week ago.
- launch #drezzd http://t.co/SuVeZhru shirts. #3d content by @dpianimation #3dsmax #masscustomization #apparel #configurator 1 week ago.
Article archive
- May 2012 (1)
- March 2012 (1)
- February 2012 (11)
- January 2012 (3)
- December 2011 (4)
- November 2011 (4)
- October 2011 (4)
- September 2011 (4)
- August 2011 (3)
- July 2011 (1)
- June 2011 (1)
- March 2011 (2)
- February 2011 (3)
- December 2010 (2)
- November 2010 (1)
- September 2010 (8)
- August 2010 (1)
- July 2010 (3)
- June 2010 (2)
- April 2010 (1)
- March 2010 (1)
- February 2010 (1)
- January 2010 (2)
- November 2009 (2)
- May 2009 (1)
- October 2008 (2)
- September 2008 (1)
Renderitis is making progress
the rendersettings script is making steady progress. It’s turning out to be a rather lengthy operation. At the moment the tool is capable of storing all scriptable rendersettings for VRay and scanline. Adding support for other renderengines is just as well possible, but requires a bit of hand-labour. I’m planning on adding support for mental ray later on.
Let me show you what’s happening at the moment.
2010-01-03_183008
2010-01-03_183101
2010-01-03_183247
2010-01-03_183427
2010-01-03_183501
2010-01-03_183714
2010-01-03_183737
2010-01-03_183803
The basic function is storing rendersettings. The settings are stored in “groups”. A group is similar to a 3dsMax renderpreset in the sense that it contains rendersettings which can be called upon from disk. My settings are stored in an xml though and are thus open to inspection. Only settings for the renderengine are stored at the moment, so no renderelements. Settings which are not scriptable aren’t stored.
The user can add and edit groups. So you can store different sets of settings for different tasks: draft, production, lighting, quick, and so on. You can set up the system so that multiple users share a single xml-file. A specific user can be made “master”. Roughly said: a specialist creates the settings and the juniors use them but cannot alter them.
The settings can be applied and altered from within the script. Settings can also be recorded from the scene into a group.
The script supports the use of multiple xml-files. In our situation we have different teams for still images and animations. Settings between these teams differ greatly. To avoid confusion, these teams have separate xml-files with different masters. A user can switch between xml-files by pressing the buttons.
The settings are stored in an xml-file. Each setting and renderengine has a unique ID. This opens up the door to exchange settings. I’m planning to create an import/export module. Imagine e-mailing settings between users, or publishing your favourite settings on a forum.
I’m planning on finishing up some minor issues and then start testing it in a production environment. Once I’m happy with that I’ll add mentalRay. After that I might be able to publish the tool.