Frequently Seen Errors for Houdini Users

Note:

A.     The platform will select the version automatically when the hip scene file was saved, or the higher version which is closest to the scene file version. For example, if it is save as houdini15.5.480 but it's not in the list, the platform will select the higher version which is closest to it, such as 15.5.523. The system only provides Production Build version.

B.     For project correlation variable reference, "$HIP" is advised for outside resources such as texture, cache, etc., or disk mapping and custom variable. Inform our Customer Service (TD) to set it if custom variable is needed.

C.    Houdini plugin setting such as otls, it's merely needed to new an otl or otls folder with relevant otls plugin, or put the otls's files into the customer's path of Fox Renderfarm account ID.

D.    For transfer-platform path mapping, if it's needed to render the files which are made in Linux or Unix OS in Windows, please be assure that all the project concerning contents are in the same root directory. Then inform our TD to set it.

1.     Analysis failed:

a.     Look up the analysis log to get the Houdini version. Check the path D:\PLUGINS\houdini to find out if there is the Houdini process file of this version. It means installation failure if there is not. Contact the TD to deal with it.

b.     It can be due to the hip file missing. Look up the analysis log to get the hip file location, check if the hip file exists, confirm the date and size with the customer's local file. Upload and analyze again if the size or date does not match.

2.     Render task failed:

a.     Re-upload the concerning texture or cache and analyze again if they don't exist.

b.     Observe the rendering process to find out if there are reading files process going on or cache overtime caused by network or storage problem. It often happens due to very large cache. Reducing the nodes number in one task can relieve this issue in a way.

c.     If it is necessary, open the relevant node to check its information such as whether the resources referred by the node exist or not, according the log.

3.     Incorrect render result:

     a.      Access the project directory to check whether the textures exist if there is prompt of some textures missing in the render log; upload the missing textures to render again if they are not in the directory. Light textures missing is usually the cause 


Frequently Seen Errors for Houdini Users

Note:

A.     The platform will select the version automatically when the hip scene file was saved, or the higher version which is closest to the scene file version. For example, if it is save as houdini15.5.480 but it's not in the list, the platform will select the higher version which is closest to it, such as 15.5.523. The system only provides Production Build version.

B.     For project correlation variable reference, "$HIP" is advised for outside resources such as texture, cache, etc., or disk mapping and custom variable. Inform our Customer Service (TD) to set it if custom variable is needed.

C.    Houdini plugin setting such as otls, it's merely needed to new an otl or otls folder with relevant otls plugin, or put the otls's files into the customer's path of Fox Renderfarm account ID.

D.    For transfer-platform path mapping, if it's needed to render the files which are made in Linux or Unix OS in Windows, please be assure that all the project concerning contents are in the same root directory. Then inform our TD to set it.

1.     Analysis failed:

a.     Look up the analysis log to get the Houdini version. Check the path D:\PLUGINS\houdini to find out if there is the Houdini process file of this version. It means installation failure if there is not. Contact the TD to deal with it.

b.     It can be due to the hip file missing. Look up the analysis log to get the hip file location, check if the hip file exists, confirm the date and size with the customer's local file. Upload and analyze again if the size or date does not match.

2.     Render task failed:

a.     Re-upload the concerning texture or cache and analyze again if they don't exist.

b.     Observe the rendering process to find out if there are reading files process going on or cache overtime caused by network or storage problem. It often happens due to very large cache. Reducing the nodes number in one task can relieve this issue in a way.

c.     If it is necessary, open the relevant node to check its information such as whether the resources referred by the node exist or not, according the log.

3.     Incorrect render result:

     a.      Access the project directory to check whether the textures exist if there is prompt of some textures missing in the render log; upload the missing textures to render again if they are not in the directory. Light textures missing is usually the cause 


Frequently Seen Errors for Houdini Users

Note:

A.     The platform will select the version automatically when the hip scene file was saved, or the higher version which is closest to the scene file version. For example, if it is save as houdini15.5.480 but it's not in the list, the platform will select the higher version which is closest to it, such as 15.5.523. The system only provides Production Build version.

B.     For project correlation variable reference, "$HIP" is advised for outside resources such as texture, cache, etc., or disk mapping and custom variable. Inform our Customer Service (TD) to set it if custom variable is needed.

C.    Houdini plugin setting such as otls, it's merely needed to new an otl or otls folder with relevant otls plugin, or put the otls's files into the customer's path of Fox Renderfarm account ID.

D.    For transfer-platform path mapping, if it's needed to render the files which are made in Linux or Unix OS in Windows, please be assure that all the project concerning contents are in the same root directory. Then inform our TD to set it.

1.     Analysis failed:

a.     Look up the analysis log to get the Houdini version. Check the path D:\PLUGINS\houdini to find out if there is the Houdini process file of this version. It means installation failure if there is not. Contact the TD to deal with it.

b.     It can be due to the hip file missing. Look up the analysis log to get the hip file location, check if the hip file exists, confirm the date and size with the customer's local file. Upload and analyze again if the size or date does not match.

2.     Render task failed:

a.     Re-upload the concerning texture or cache and analyze again if they don't exist.

b.     Observe the rendering process to find out if there are reading files process going on or cache overtime caused by network or storage problem. It often happens due to very large cache. Reducing the nodes number in one task can relieve this issue in a way.

c.     If it is necessary, open the relevant node to check its information such as whether the resources referred by the node exist or not, according the log.

3.     Incorrect render result:

     a.      Access the project directory to check whether the textures exist if there is prompt of some textures missing in the render log; upload the missing textures to render again if they are not in the directory. Light textures missing is usually the cause 


Frequently Seen Errors for Houdini Users

Note:

A.     The platform will select the version automatically when the hip scene file was saved, or the higher version which is closest to the scene file version. For example, if it is save as houdini15.5.480 but it's not in the list, the platform will select the higher version which is closest to it, such as 15.5.523. The system only provides Production Build version.

B.     For project correlation variable reference, "$HIP" is advised for outside resources such as texture, cache, etc., or disk mapping and custom variable. Inform our Customer Service (TD) to set it if custom variable is needed.

C.    Houdini plugin setting such as otls, it's merely needed to new an otl or otls folder with relevant otls plugin, or put the otls's files into the customer's path of Fox Renderfarm account ID.

D.    For transfer-platform path mapping, if it's needed to render the files which are made in Linux or Unix OS in Windows, please be assure that all the project concerning contents are in the same root directory. Then inform our TD to set it.

1.     Analysis failed:

a.     Look up the analysis log to get the Houdini version. Check the path D:\PLUGINS\houdini to find out if there is the Houdini process file of this version. It means installation failure if there is not. Contact the TD to deal with it.

b.     It can be due to the hip file missing. Look up the analysis log to get the hip file location, check if the hip file exists, confirm the date and size with the customer's local file. Upload and analyze again if the size or date does not match.

2.     Render task failed:

a.     Re-upload the concerning texture or cache and analyze again if they don't exist.

b.     Observe the rendering process to find out if there are reading files process going on or cache overtime caused by network or storage problem. It often happens due to very large cache. Reducing the nodes number in one task can relieve this issue in a way.

c.     If it is necessary, open the relevant node to check its information such as whether the resources referred by the node exist or not, according the log.

3.     Incorrect render result:

     a.      Access the project directory to check whether the textures exist if there is prompt of some textures missing in the render log; upload the missing textures to render again if they are not in the directory. Light textures missing is usually the cause