You are not logged in.

#1 2016-01-10 18:35:22

Registered: 2016-01-07
Posts: 29

Preparing a scene for rendering

When rendering it is normal that something could go wrong, but if you follow these simple rules you increase your odds of avoiding issues by quite a margin.

  • Scene files - should be saved in .lws format - version from 11.6.3  to newest one

  • Project folder - should be used. All needed assets should be in correct place (.lwo files in \Objects\, textures in \Images\ etc) - Please always use relative paths (Objects\MyObject.lwo) instead of absolute paths (like C: Project1\Objects\MyObjetc.lwo).

  • Spaces signs in objects, scenes, assets name should be changed to "_" as Lightwave is making a lot of troubles with network rendering & spaces

  • Saving animation switch -  should be OFF -  we are rendering to frames, not animations

  • If there are dynamics/particle systems used in the scene, cache file should be created for them. Otherwise, we will calculate caches on our side, and add extra $ for it to final billing

  • Radiosity / GI setup - should be prepared for multi - machines rendering in both render engines - LightWave & Kray

  • If the scene needs radiosity / GI caching before rendering - please calculate .radiosity files and connect them to the scene before sending the project to farm

  • Plugins - we are supporting a lot of Lightwave plugins & add-ons, however, if you are using some extra add-ons - please send info to us. We will check for plugin availability

  • Additional outputs - we are supporting all kind of external Lightwave outputs - main output, compositive buffer output, PSD Manager output, EXR Trader output. Also, Kray buffers are supported

  • Kray - we are supporting Kray renderer for Lightwave. All Kray features are supported

Remember that we are here to help you so if you are not sure about something just ask us

Version 003

Last edited by Mike (2017-02-14 13:37:17)


Board footer

Powered by FluxBB