This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
private:exrtrader2017:workflow [2017/05/12 14:40] – created lightwolf | exrtrader2018:workflow [2018/07/30 15:08] (current) – lightwolf | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== General workflow options ====== | ====== General workflow options ====== | ||
+ | {{ exrtrader2018: | ||
===== Save in Layout ===== | ===== Save in Layout ===== | ||
Line 7: | Line 7: | ||
Images will always be saved by exrTrader when rendering in Layout. | Images will always be saved by exrTrader when rendering in Layout. | ||
- | ==== Only Sequences (F10) (requires at least LightWave 3D V9.5) ==== | + | ==== Only Sequences (F10) ==== |
Images will only be saved by exrTrader if the current render is a sequence render (F10) | Images will only be saved by exrTrader if the current render is a sequence render (F10) | ||
Line 15: | Line 15: | ||
===== Store all Buffers (F9) ===== | ===== Store all Buffers (F9) ===== | ||
- | exrTrader can display all buffers using VIPER after an initial render with exrTrader applied to the scene, this requires up to 42MB of memory. | + | exrTrader can display all buffers using a built-in image viewer |
- | By default, only the selected buffers are stored in memory for VIPER. If you wish to assess all buffers, this option will request all available buffers from LightWave 3D during a render and store them for the VIPER preview. | + | |
+ | 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 enabled as well. | + | |
- | This setting has no effect | + | This setting has no effect |
===== Show Buffers Preview... ===== | ===== Show Buffers Preview... ===== | ||
- | This button opens or closes | + | This button opens or closes the built-in image viewer. |
- | Post-apply Display Gamma (not available | + | |
- | If you check this control then exrTrader will apply the Display Gamma setting to the main RGB buffer after exrTrader has processed and exported the buffers. | + | |
- | This allows you to view a render with gamma correction in the LightWave | + | |
- | This option is not available in LightWave 10.0 and higher due to the availability of a colour management system to enable a “proper” linear work flow. | + | |
===== Preview Scale ===== | ===== Preview Scale ===== | ||
+ | |||
+ | 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|-> |