Create Scene Text and Log files:

This will create a text log file if all the rendered frames in this format:
File,Computer,Start FF,End FF,No. CPUs,Hrs.,Min.,Sec

DESCRIPT.ION file for output images

This will create a 'ACDSee™' description file of all the frame images created

Create separate RenderNode:

This will create a Debug log file for each RenderNode (for debugging only)

Create Program Trace Log (Bcontrol.xxx):

This will create a Trace log file (for debugging only)

Max Log size (MBytes):

Maximum size of Megabytes that the Bcontrol log file can reach

back to top
 

Verify Rendered Frames (Images) Global Default:

This will set the default setting to verify rendered frame images. BNR will confirm the image frame is more than zero bytes.

Re-Render Bad Frames:

After all the Frames have been rendered - or tried to be rendered, BNR will look for frames that didn't get rendered - and render them.

Check Targa Format:

Use this to check the image frames that are the Targa Format. BNR will check the file size then the Targa header.

Final Scan for Frames:

Just to make sure all the Frame images will be scanned again to confirm they are found - if some are not found - BNR will render these frames.

back to top

 

Notify if Started Scene is not Rendering within 90 Mins:

This will email a notification message warning that Scenes have not been started yet
This might be used to make sure all the rendernodes are working correctly

Check for Hung Render Nodes Every 90 mins:

This will kill a Rendernode that has not send a message after the number of mins selected . Warning! During Rendering - the RenderNodes - don't send any messages - so make sure the number of Mins is greater than the maximum time a render can take! f you don't know the render time - then don't use this feature.

Shutdown RenderNode after 5 errors:

This will Disable the RenderNode after the number of Errors.  Please check the Rendernode/Scene Messages Tab for a description of the errors.
Once you know why the Rendernode is not working - you will need to reset the errors by using the right click context menu.

Stop Scene Rendering after 5 errors:

This will Disable the Scene after the number of Errors.  Please check the Scene Messages Tab for a description of the errors.
Once you know why the Rendernode is not working - you will need to reset the errors by using the right click context menu.

Heartbeat nodes:

Use this to Ping the RenderNodes - Warning this could create a lot of ping traffic on your network.

back to top

 

AutoLoad Scene Scan:

This will enable the option for BNR to scan the 'autoload' for scenes to be loaded and rendered.

LW Scene Object Checking:

With this enabled the Controller and Clients will check Lightwave Scenes to make sure the 'Plugins' in the config file and the Objects in the Scene file can be found.

New LW Shell per Scene:

This will force a new LWSN shell when rendering Lightwave Scenes. This will help clear the LWSN.

AutoUpdate the Client Software on Initial connection

This cause the Clients to update themselves if a New version of the Controller is found.  Otherwise you will need to select the 'File->Update Clients' option.

Send Email as HTML:

This will enable HTML email instead of text email

Show System Events:

This will display internal BNR system messages when this is enabled. Mostly used for debugging new features.

DHCP Client Names:

If the BNR Clients are on a DHCP network - then enable this. This will make sure the Rendernodes will reconnect by Name only not Name and IP Address. Sometimes DHCP network will change the IP Address of the clients.

LW Load Limit - Max Scene loads at one time:

Use this to Limit the number of Lightwave 'Load' commands that will be running at one time . This is used to help decrease the Network Traffic.

Force stop on Lightwave Scenes:

When a scene is Stopped - BNR will wait for the RenderNodes to finish rendering the current frame they are on. If you enable this option - BNR will STOP the rendernode and lose the current rendering frame.

Remove Lightwave Spreadsheet Data:

This will remove the Lightwave Spreadsheet data from the lws Scene file that can sometimes cause the LWSN to crash.

Started Scene emails limited to 50:

Use this to limit the number of emails you will receive per Scene.



Disable Start Scene Confirmation:

This will turn off the 'Scene Check' dialog after you select start scene.

Start Scene - Check frames:

With the 'Disable Start Scene Confirmation'- you can select if you want BNR to check for frames before the scene is started.


First use Rendernodes Above Mhz 1000:

This will make BNR use Higher Processors first when rendering.

back to top