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 documentation: permissions
Renderitis documentation
Renderitis has been designed to be used for individuals and in studios with multiple users. This gives you the possibility to use a single preset within a team. Sharing rendersettings is pretty easy when renderitis has been setup correctly. By default the script works fine for either individuals or teams, but you can streamline the script for teams even more. This is done by setting permissions for specific users. There are three roles: manager, art director and user. Each role gives access to specific parts of the script.
Setting permissions is done based on username. This is by no means meant to be a watertight and secure system. It’s just a way to make sure the right people can mess with the presets.
Adding permissions
You can only add or edit permissions if you have the manager role. Renderitis by default has no permissions set. This means that it accepts any user as manager. It’s sensible to set at least one user as manager before you create any other permission. If you somehow lose access to some functions you can edit the xml-file to alter the permissions. If there’s at least one permission stored, any other user is considered to have a user-role.
Use permissions to streamline working in a studio
It's a good idea to give at least one user the manager-role
Now the manager role is locked to user klaas
Add more permissions
Studio setup
A studio setup normally has a manager and an art director. The manager can create preset-files and setup permissions. This is more of a technical role. The art director can create and edit presets. This role focuses on the quality of the rendersettings. Any other user has a user-role. The user-role can browse and apply presets, but not edit them.
A studio setup uses a manager and an art director
Remove users and permissions if needed.