All 3Delight plug-in ins can export NSI files. These files can be rendered either locally or the cloud. Sequences of NSI files can be exported as well, with some plug-ins (such as 3Delight for Houdini) having the ability to factor out static geometries from the animation into a separate NSI file to drastically reduce the required storage.
...
Let's go through an example for the variable insertion method. Let: let's say you declared the following environment variables on your system or inside your 3D application:
Environment Variable | Value |
---|---|
NSI_PATH_TEXTURE | C:\textures |
NSI_PATH_IMAGES | C:\images |
PROJECT | Devoir1 |
Then, during the NSI export, the following exported paths will be transformed substituted as such in the NSI file:
Original PathResult | Exported Path (in NSI file) |
---|---|
C:\textures\JoshuaLeatherJacket.jpg | ${NSI_PATH_TEXTURES}\JoshuaLeatherJacket.jpg |
C:\images\output\render.exr | ${NSI_PATH_TEXTURES}\output\render.exr |
C:\images\${PROJECT}\grid.exr | ${NSI_PATH_TEXTURES\${PROJECT}\grid.exr |
...