Frequently Seen Errors for Redshift Users

Our desktop client is strongly recommended for the user to submit render tasks. 

1.     Analysis failed:

a.     Look up the analysis log and check the version details of Redshift, then go to D:\PLUGINS\MAYA\REDSHIFT and see if the program file of the same Redshift version exists. If not, it means the copying and installing failed, please contact the customer service.

b.     Confirm the Redshift version with the user and check if it is the same version used for analysing. If not, please ask customer service to review and install.

 

2.     Render task failed:

a.     Open the render log and check if any texture, cache or agent file is missing. If yes, please upload the missing files and try again. The missing textures quoted inside the RS agent are easily being ignored.

b.     Pay attention on the proceeding activities in the nods during rendering. It could happen that it has been fetching resources like reference, hair cache, RS overtime due to internet connection or storage problems. Also, this could be due to proceeding capacity of the internet and storage.

c.     A Redshift render requires ray tracing of large scales of computing which usually causes a long time. The stress could be eased by reducing the amount of nods rendering at the same time.

d.     Internal aborted by the renderer, largely due to too high render setup parameters and the hardware failed to accomplish the whole rendering process. Please open the file and check the render settings, meanwhile, be aware if the settings of illumination of lights and the shadow sample rate are too high.

4.png

5.png     


2.png

                             

6.png

e.     Some project requires Maya to load plugins before loading the file; Such as: the plugin opiumPipe of OF3D project

f.      Failure occurs when the output file name involves in a space.

image.png

g.     Some error may occur because of the "renumber frames" option is selected.

7.png

h.     Note: A render camera must be selected in the render settings in advance.
image.png

i.      The mel setting before and after the rendering may cause errors, please clear it up.
QQ图片20170816181516.png


3.     Incorrect render result:

a.     Look up the render log and check if any texture missing notification could be found.

Notification found: open the scene folder and see whether or not the texture exists;

Notification not found: Suggest the client to upload the textures and try again.

It commonly happens the illumination texture is missing that causes incorrect of the render results.


Frequently Seen Errors for Redshift Users

Our desktop client is strongly recommended for the user to submit render tasks. 

1.     Analysis failed:

a.     Look up the analysis log and check the version details of Redshift, then go to D:\PLUGINS\MAYA\REDSHIFT and see if the program file of the same Redshift version exists. If not, it means the copying and installing failed, please contact the customer service.

b.     Confirm the Redshift version with the user and check if it is the same version used for analysing. If not, please ask customer service to review and install.

 

2.     Render task failed:

a.     Open the render log and check if any texture, cache or agent file is missing. If yes, please upload the missing files and try again. The missing textures quoted inside the RS agent are easily being ignored.

b.     Pay attention on the proceeding activities in the nods during rendering. It could happen that it has been fetching resources like reference, hair cache, RS overtime due to internet connection or storage problems. Also, this could be due to proceeding capacity of the internet and storage.

c.     A Redshift render requires ray tracing of large scales of computing which usually causes a long time. The stress could be eased by reducing the amount of nods rendering at the same time.

d.     Internal aborted by the renderer, largely due to too high render setup parameters and the hardware failed to accomplish the whole rendering process. Please open the file and check the render settings, meanwhile, be aware if the settings of illumination of lights and the shadow sample rate are too high.

4.png

5.png     


2.png

                             

6.png

e.     Some project requires Maya to load plugins before loading the file; Such as: the plugin opiumPipe of OF3D project

f.      Failure occurs when the output file name involves in a space.

image.png

g.     Some error may occur because of the "renumber frames" option is selected.

7.png

h.     Note: A render camera must be selected in the render settings in advance.
image.png

i.      The mel setting before and after the rendering may cause errors, please clear it up.
QQ图片20170816181516.png


3.     Incorrect render result:

a.     Look up the render log and check if any texture missing notification could be found.

Notification found: open the scene folder and see whether or not the texture exists;

Notification not found: Suggest the client to upload the textures and try again.

It commonly happens the illumination texture is missing that causes incorrect of the render results.


Frequently Seen Errors for Redshift Users

Our desktop client is strongly recommended for the user to submit render tasks. 

1.     Analysis failed:

a.     Look up the analysis log and check the version details of Redshift, then go to D:\PLUGINS\MAYA\REDSHIFT and see if the program file of the same Redshift version exists. If not, it means the copying and installing failed, please contact the customer service.

b.     Confirm the Redshift version with the user and check if it is the same version used for analysing. If not, please ask customer service to review and install.

 

2.     Render task failed:

a.     Open the render log and check if any texture, cache or agent file is missing. If yes, please upload the missing files and try again. The missing textures quoted inside the RS agent are easily being ignored.

b.     Pay attention on the proceeding activities in the nods during rendering. It could happen that it has been fetching resources like reference, hair cache, RS overtime due to internet connection or storage problems. Also, this could be due to proceeding capacity of the internet and storage.

c.     A Redshift render requires ray tracing of large scales of computing which usually causes a long time. The stress could be eased by reducing the amount of nods rendering at the same time.

d.     Internal aborted by the renderer, largely due to too high render setup parameters and the hardware failed to accomplish the whole rendering process. Please open the file and check the render settings, meanwhile, be aware if the settings of illumination of lights and the shadow sample rate are too high.

4.png

5.png     


2.png

                             

6.png

e.     Some project requires Maya to load plugins before loading the file; Such as: the plugin opiumPipe of OF3D project

f.      Failure occurs when the output file name involves in a space.

image.png

g.     Some error may occur because of the "renumber frames" option is selected.

7.png

h.     Note: A render camera must be selected in the render settings in advance.
image.png

i.      The mel setting before and after the rendering may cause errors, please clear it up.
QQ图片20170816181516.png


3.     Incorrect render result:

a.     Look up the render log and check if any texture missing notification could be found.

Notification found: open the scene folder and see whether or not the texture exists;

Notification not found: Suggest the client to upload the textures and try again.

It commonly happens the illumination texture is missing that causes incorrect of the render results.


Frequently Seen Errors for Redshift Users

Our desktop client is strongly recommended for the user to submit render tasks. 

1.     Analysis failed:

a.     Look up the analysis log and check the version details of Redshift, then go to D:\PLUGINS\MAYA\REDSHIFT and see if the program file of the same Redshift version exists. If not, it means the copying and installing failed, please contact the customer service.

b.     Confirm the Redshift version with the user and check if it is the same version used for analysing. If not, please ask customer service to review and install.

 

2.     Render task failed:

a.     Open the render log and check if any texture, cache or agent file is missing. If yes, please upload the missing files and try again. The missing textures quoted inside the RS agent are easily being ignored.

b.     Pay attention on the proceeding activities in the nods during rendering. It could happen that it has been fetching resources like reference, hair cache, RS overtime due to internet connection or storage problems. Also, this could be due to proceeding capacity of the internet and storage.

c.     A Redshift render requires ray tracing of large scales of computing which usually causes a long time. The stress could be eased by reducing the amount of nods rendering at the same time.

d.     Internal aborted by the renderer, largely due to too high render setup parameters and the hardware failed to accomplish the whole rendering process. Please open the file and check the render settings, meanwhile, be aware if the settings of illumination of lights and the shadow sample rate are too high.

4.png

5.png     


2.png

                             

6.png

e.     Some project requires Maya to load plugins before loading the file; Such as: the plugin opiumPipe of OF3D project

f.      Failure occurs when the output file name involves in a space.

image.png

g.     Some error may occur because of the "renumber frames" option is selected.

7.png

h.     Note: A render camera must be selected in the render settings in advance.
image.png

i.      The mel setting before and after the rendering may cause errors, please clear it up.
QQ图片20170816181516.png


3.     Incorrect render result:

a.     Look up the render log and check if any texture missing notification could be found.

Notification found: open the scene folder and see whether or not the texture exists;

Notification not found: Suggest the client to upload the textures and try again.

It commonly happens the illumination texture is missing that causes incorrect of the render results.