Render Guide for Redshift Users

Render Guide


As one of the plugins of Maya, Redshift follows the same orders and settings as every other plugin of Maya. Please be more aware of setting the current version before rendering.

And for more details, please refer to the user guides of both Maya desktop client render guide and Maya web-submission render guide.


Content of this Text:

1. Default Render Task Conventions

2. Redshift Client APP Instruction

3. Tips for a Redshift Project Preparation

 

1. Default Render Task Conventions

a. The latest software update package is used as a default, the service pack of Maya for instance. It is a compatible default when a user submits a render of Maya2015 sp6 while the nodes on the farm have Maya2015 sp6 installed. For any further inquiries, please contact our customer service team.

b. We have the default render setting on the platform as having one frame per node, in order to make the single-task (files) acquires more nodes during rendering.

Before a render starts, Redshift creates its special selective textures, of which the cache takes longer. So, suppose a render task involves in 50 frames. Given by the rule of one frame per node, we would have 50 nodes rendering this task at the same time and create the texture caches 50 times. But if we had two frames per node and 25 nodes for this 50-frames task, the time for creating the caches would reduce a half. Meanwhile, it would save the rest 25 nodes left for other render tasks.

Overall, the second option works better with both efficiency and productivity. In other words, we can decide the number of frames per node for render by the time it takes, which commonly set as 2-5 frames per node.


Note: An additional instruction is required for this setting.

 

2. Redshift Desktop Client Instruction

a. Select a node with both internet connection and the same software and plugin environment as the one for the project making.

b. Install the desktop client.

c. Set the relevant versions of both software and plugins. Please consult the customer service for the required but unlisted plugins.

 image.png                                              

 

3. Tips for a Redshift Project Preparation

a. Detailed software version info for the project: e.g. Maya 2016 extension 1 sp6.

b. Detailed plugin version info: e.g. mtoa 1.2.2.1, shave 8.0v26, etc.

c. Required drive mapping: e.g. Z mapping.

d. Required Variable mapping: e.g. Variable mapping for maya $AK47: //10.50.1.110/hellokitty/ak47…

e. Project path mapping: e.g. //10.50.1.110/hellokitty/ak47, path mapping on server: 10.50.242.6/inputdata/…

f.  Whether forcing to load plugins is required when opening the file.

g. Brief description for the project directory.

h. Setting the same project path when submitting a task is required when an absolute path is used during the project making. Particularly, a fixed map path is suggested in the operation of an agent or cache.

 

 

 

 


Render Guide for Redshift Users

Render Guide


As one of the plugins of Maya, Redshift follows the same orders and settings as every other plugin of Maya. Please be more aware of setting the current version before rendering.

And for more details, please refer to the user guides of both Maya desktop client render guide and Maya web-submission render guide.


Content of this Text:

1. Default Render Task Conventions

2. Redshift Client APP Instruction

3. Tips for a Redshift Project Preparation

 

1. Default Render Task Conventions

a. The latest software update package is used as a default, the service pack of Maya for instance. It is a compatible default when a user submits a render of Maya2015 sp6 while the nodes on the farm have Maya2015 sp6 installed. For any further inquiries, please contact our customer service team.

b. We have the default render setting on the platform as having one frame per node, in order to make the single-task (files) acquires more nodes during rendering.

Before a render starts, Redshift creates its special selective textures, of which the cache takes longer. So, suppose a render task involves in 50 frames. Given by the rule of one frame per node, we would have 50 nodes rendering this task at the same time and create the texture caches 50 times. But if we had two frames per node and 25 nodes for this 50-frames task, the time for creating the caches would reduce a half. Meanwhile, it would save the rest 25 nodes left for other render tasks.

Overall, the second option works better with both efficiency and productivity. In other words, we can decide the number of frames per node for render by the time it takes, which commonly set as 2-5 frames per node.


Note: An additional instruction is required for this setting.

 

2. Redshift Desktop Client Instruction

a. Select a node with both internet connection and the same software and plugin environment as the one for the project making.

b. Install the desktop client.

c. Set the relevant versions of both software and plugins. Please consult the customer service for the required but unlisted plugins.

 image.png                                              

 

3. Tips for a Redshift Project Preparation

a. Detailed software version info for the project: e.g. Maya 2016 extension 1 sp6.

b. Detailed plugin version info: e.g. mtoa 1.2.2.1, shave 8.0v26, etc.

c. Required drive mapping: e.g. Z mapping.

d. Required Variable mapping: e.g. Variable mapping for maya $AK47: //10.50.1.110/hellokitty/ak47…

e. Project path mapping: e.g. //10.50.1.110/hellokitty/ak47, path mapping on server: 10.50.242.6/inputdata/…

f.  Whether forcing to load plugins is required when opening the file.

g. Brief description for the project directory.

h. Setting the same project path when submitting a task is required when an absolute path is used during the project making. Particularly, a fixed map path is suggested in the operation of an agent or cache.

 

 

 

 


Render Guide for Redshift Users

Render Guide


As one of the plugins of Maya, Redshift follows the same orders and settings as every other plugin of Maya. Please be more aware of setting the current version before rendering.

And for more details, please refer to the user guides of both Maya desktop client render guide and Maya web-submission render guide.


Content of this Text:

1. Default Render Task Conventions

2. Redshift Client APP Instruction

3. Tips for a Redshift Project Preparation

 

1. Default Render Task Conventions

a. The latest software update package is used as a default, the service pack of Maya for instance. It is a compatible default when a user submits a render of Maya2015 sp6 while the nodes on the farm have Maya2015 sp6 installed. For any further inquiries, please contact our customer service team.

b. We have the default render setting on the platform as having one frame per node, in order to make the single-task (files) acquires more nodes during rendering.

Before a render starts, Redshift creates its special selective textures, of which the cache takes longer. So, suppose a render task involves in 50 frames. Given by the rule of one frame per node, we would have 50 nodes rendering this task at the same time and create the texture caches 50 times. But if we had two frames per node and 25 nodes for this 50-frames task, the time for creating the caches would reduce a half. Meanwhile, it would save the rest 25 nodes left for other render tasks.

Overall, the second option works better with both efficiency and productivity. In other words, we can decide the number of frames per node for render by the time it takes, which commonly set as 2-5 frames per node.


Note: An additional instruction is required for this setting.

 

2. Redshift Desktop Client Instruction

a. Select a node with both internet connection and the same software and plugin environment as the one for the project making.

b. Install the desktop client.

c. Set the relevant versions of both software and plugins. Please consult the customer service for the required but unlisted plugins.

 image.png                                              

 

3. Tips for a Redshift Project Preparation

a. Detailed software version info for the project: e.g. Maya 2016 extension 1 sp6.

b. Detailed plugin version info: e.g. mtoa 1.2.2.1, shave 8.0v26, etc.

c. Required drive mapping: e.g. Z mapping.

d. Required Variable mapping: e.g. Variable mapping for maya $AK47: //10.50.1.110/hellokitty/ak47…

e. Project path mapping: e.g. //10.50.1.110/hellokitty/ak47, path mapping on server: 10.50.242.6/inputdata/…

f.  Whether forcing to load plugins is required when opening the file.

g. Brief description for the project directory.

h. Setting the same project path when submitting a task is required when an absolute path is used during the project making. Particularly, a fixed map path is suggested in the operation of an agent or cache.

 

 

 

 


Render Guide for Redshift Users

Render Guide


As one of the plugins of Maya, Redshift follows the same orders and settings as every other plugin of Maya. Please be more aware of setting the current version before rendering.

And for more details, please refer to the user guides of both Maya desktop client render guide and Maya web-submission render guide.


Content of this Text:

1. Default Render Task Conventions

2. Redshift Client APP Instruction

3. Tips for a Redshift Project Preparation

 

1. Default Render Task Conventions

a. The latest software update package is used as a default, the service pack of Maya for instance. It is a compatible default when a user submits a render of Maya2015 sp6 while the nodes on the farm have Maya2015 sp6 installed. For any further inquiries, please contact our customer service team.

b. We have the default render setting on the platform as having one frame per node, in order to make the single-task (files) acquires more nodes during rendering.

Before a render starts, Redshift creates its special selective textures, of which the cache takes longer. So, suppose a render task involves in 50 frames. Given by the rule of one frame per node, we would have 50 nodes rendering this task at the same time and create the texture caches 50 times. But if we had two frames per node and 25 nodes for this 50-frames task, the time for creating the caches would reduce a half. Meanwhile, it would save the rest 25 nodes left for other render tasks.

Overall, the second option works better with both efficiency and productivity. In other words, we can decide the number of frames per node for render by the time it takes, which commonly set as 2-5 frames per node.


Note: An additional instruction is required for this setting.

 

2. Redshift Desktop Client Instruction

a. Select a node with both internet connection and the same software and plugin environment as the one for the project making.

b. Install the desktop client.

c. Set the relevant versions of both software and plugins. Please consult the customer service for the required but unlisted plugins.

 image.png                                              

 

3. Tips for a Redshift Project Preparation

a. Detailed software version info for the project: e.g. Maya 2016 extension 1 sp6.

b. Detailed plugin version info: e.g. mtoa 1.2.2.1, shave 8.0v26, etc.

c. Required drive mapping: e.g. Z mapping.

d. Required Variable mapping: e.g. Variable mapping for maya $AK47: //10.50.1.110/hellokitty/ak47…

e. Project path mapping: e.g. //10.50.1.110/hellokitty/ak47, path mapping on server: 10.50.242.6/inputdata/…

f.  Whether forcing to load plugins is required when opening the file.

g. Brief description for the project directory.

h. Setting the same project path when submitting a task is required when an absolute path is used during the project making. Particularly, a fixed map path is suggested in the operation of an agent or cache.