-
Notifications
You must be signed in to change notification settings - Fork 2
Tips
This page contains a list of potentially useful tips for new users, that we couldn't figure out where else to list. Please feel free to suggest things we should add to this list.
We maintain a list of current issues pertaining to the toolbox, using gitHub's issues feature. Reading this is a good idea, to get a sense of what may be broken, what we're planning, and how you could help with development of the software.
RenderToolbox3 does not contain any error checking that would prevent users from setting loose a rendering process that would fill the disk. This is true. We are not sure how likely this is to occur, but if you are new to rendering you might keep an eye on the sizes of the files you are generating. One reason the software does not contain such error checking is that we don't know how to predict easily the likely size of a rendering's output from an analysis of the input. If you have a good idea about how to do this, let us know by adding a comment to this issue. As a workaround, if you are worried about this, you might consider setting RTB's output to a disk drive that does not contain the system for your computer. That way, if it fills up your system will not crash.
Here is a page about doing procedural 3D modeling with Python driven Blender
It turns out 3D modelers and Physically based renderers disagree in important ways about what is an "area light". You can still use area lights with RenderToolbox3, and it's not that hard. But you do have to think about it. So here is a page with Advice for Area Lights.