db&w documentation wiki

finest software | finest docs

User Tools

Site Tools


exrtrader2018:workflow

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
exrtrader2018:workflow [2017/05/12 14:55]
lightwolf [General workflow options]
exrtrader2018:workflow [2018/07/30 15:08] (current)
lightwolf
Line 1: Line 1:
 ====== General workflow options ====== ====== General workflow options ======
-{{ :private:exrtrader2017:workflow_options.png?nolink|}}+{{ exrtrader2018:workflow_options.png?nolink|}}
 ===== Save in Layout ===== ===== Save in Layout =====
  
Line 15: Line 15:
 ===== Store all Buffers (F9) ===== ===== Store all Buffers (F9) =====
  
-exrTrader can display all buffers using a built-in image viewer after an initial render with exrTrader applied to the scene. The amount of memory required depends on the amount of buffers as well as the Preview Scale.+exrTrader can display all buffers using a built-in image viewer after an initial render with exrTrader applied to the scene. The amount of memory required depends on the amount of buffers, the image size as well as the Preview Scale.
  
 By default, only the selected buffers are stored in memory for the preview. If you wish to assess all buffers, this option will request all available buffers from LightWave 3D during a render and store them in RAM. By default, only the selected buffers are stored in memory for the preview. If you wish to assess all buffers, this option will request all available buffers from LightWave 3D during a render and store them in RAM.
  
 This option is only effective for a single frame render (F9), since it can slow down final renders dramatically in some cases. This option is only effective for a single frame render (F9), since it can slow down final renders dramatically in some cases.
- 
-The exception here is the Ambient Occlusion buffer, since it triggers a separate render pass. If you wish to preview this buffer in VIPER, it needs to be explicitly enabled. 
  
 This setting has no effect when rendering on a render node. This setting has no effect when rendering on a render node.
Line 31: Line 29:
  
 This percentage defines how much the buffers are scaled down for preview purposes only. Since they will all be stored in memory after render, they can use a few GBs given a large amount of buffers and high render resolution. This percentage defines how much the buffers are scaled down for preview purposes only. Since they will all be stored in memory after render, they can use a few GBs given a large amount of buffers and high render resolution.
 +
 +===== Output Path =====
 +This defines the base path for all written images. You can either use the path defined by LightWave 3D or select your own.
 +
 +You can only select an output path if **Use Prefs Render Path** is not activated.
 +===== Use Prefs Render Path =====
 +
 +If you select this option, exrTrader will use the output file defined in the Lightwave3D render globals.
 +
 +This option is quite important if used across a render farm in conjunction with the OpenEXR Dummy Saver, described later in this manual.
 +
 +<- presets| ^| ^ viewer|->
exrtrader2018/workflow.1494593756.txt.gz · Last modified: 2017/05/12 14:55 by lightwolf