Backburner – Issue with Include Maps optionIssueThere is a potential issue when submitting Net Render jobs with the Include Maps option in 3ds Max 2010 and 3ds Max Design 2010. You may encounter this problem when submitting 3ds Max or 3ds Max Design 2009 scene files for render in 3ds Max or 3ds Max Design 2010. The maps may not be packaged correctly when submitting the render and the render may fail when submitted by the Backburner manager.
The issue may be apparent under the following conditions:-
1. You have started Backburner Manager and Backburner Monitor on the render manager and started Backburner Server on the client machines you wish to submit the renders to. Backburner Manager, Monitor and Server can be launched from:-
Start>Programs>Autodesk>Backburner
2. On the machine Backburner manager is running on, you have opened the scene file in 3ds Max 2010 or 3ds Max Design 2010, opened the Render Setup dialog (F10) and from Common tab>Render Output selected the Net Render option. This is as shown in screenshot below:- 
3. You have opened the Network Job Assignment dialog window by selecting the Render button from the Render Setup (F10) Window (shown above). In the Network Job Assignment dialog window you have connected by selecting Connect button to the Manager that is already running from step 1 above.
4. From the Network Job Assignment dialog window, under Options section- you have enabled the Include Maps option to package all referenced maps in the scene. This option is shown in the screenshot below:- 
5. You have chosen Submit from the network Job Assignment dialog window to submit the render through Backburner.
Result: The render may not complete on the render servers as expected. You may receive an error similar to the screenshot below on the render server suggesting that there is a missing map file that has caused the render to fail:- SolutionThis can happen when you submit 3ds Max 2009 scene files for render through Net Render in 3ds Max 2010. The scene files appear to have broken references to map files that would normally not break the Net Render in 3ds Max 2009. The missing map files in the scene would not normally be needed for the render as they are not assigned to any objects in the scene. An example of the error you may see when opening such scene file in 3ds Max 2009 or 3ds Max 2010 can be seen below:- As mentioned above, this issue has only been confirmed by users when testing with 3ds Max 2009 scene files in 3ds Max 2010. Creating a new scene file from scratch with similar setup in 3ds Max 2010 or 3ds Max Design 2010 does not show the issue.
To resolve the issue you may wish to consider the following options:-
Remove any references to missing maps in the 3ds Max 2009 scene file before submitting render through 3ds Max 2010 with Include Maps option
To do this, you should check the Material Editor (M shortcut) for any references to maps that are no longer stored in the correct directory. You may wish to remove any references to these Maps from the material editor or to create dummy texture files on the system that are named the same in same directory to resolve the errors. This solution should allow you to submit the Net Render successfully through 3ds Max 2010 with Include Maps option without receiving the missing maps error from Backburner server.
When the render has been successfully submitted to the server machines with Include Maps option: The packaged map files should be archived in a .Zip file and sent across the network to the following directory prior to render:-
C:\Documents and Settings\YOUR_USER_NAME\Local Settings\Application Data\backburner\ServerJob
Do not use Include Maps option when submitting Net Render through 3ds Max 2010
The Include Maps option in Network Job Assignment dialog window is a quick and easy way to package and send all necessary map files to each render node when using Backburner.
If you are unable to work-around the issue as described above when using Include Maps option- You may wish to consider de-selecting this option and instead either:-
- Set up a shared directory for the maps on the network that all machines can access.
- Duplicate the maps directories referenced from the scene file across all machines. To do this, please confirm the path to the maps from the scene file and create duplicate directories that are named the same and where the maps will be copied to for each local Backburner server machine used for rendering.
Please note: This solution may be preferable for most users to using the Include Maps option. Network rendering will be slower when using Include Maps option, due to the increased time taken to package and transfer all necessary map files across the network for render.
|
Support – Terms of UseAUTODESK DOES NOT GUARANTEE THAT YOU WILL BE ABLE TO SUCCESSFULLY DOWNLOAD OR IMPLEMENT ANY SERVICE PACK OR WORKAROUND, OR ANY OF THE TIPS, TRICKS, EXAMPLES OR SUGGESTIONS OUTLINED IN ANY AUTODESK PRODUCT SUPPORT TECHNICAL DOCUMENTS. TECHNICAL DOCUMENTS, SERVICE PACKS AND WORKAROUNDS ARE SUBJECT TO CHANGE WITHOUT NOTICE TO YOU. AUTODESK PROVIDES TECHNICAL DOCUMENTS, SERVICE PACKS AND WORKAROUNDS "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL AUTODESK OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF DATA, OR LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, THAT MAY OCCUR AS A RESULT OF IMPLEMENTING ANY SERVICE PACK OR WORKAROUND, OR ANY SUGGESTION OUTLINED IN ANY AUTODESK PRODUCT SUPPORT TECHNICAL DOCUMENT, EVEN IF AUTODESK OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. | 
