It seems Octane has an issue loading textures from certain paths. Near as I can tell, it doesn't like folder names with periods in the prefix, for example: "..NEW". The file name and path display fine in the RGB Image type, but no image will show in the render.
This is the path I was having issues with: "D:\Textures\..NEW\ROCK_02-Chalkstone\Color.jpg"
Max has no issue loading and rendering the same texture.
Bug with texture paths
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Hi,
This is an interesting issue. Do you find that this also occurs with when using the Octane Standalone? This issue may be a limitation of 3ds Max, but I will take a look into duplicating this issue.
If this is indeed an issue with the plugin specific (as opposed to Octane or 3DS Max), I will expand troubleshooting from there.
Cheers,
Azen
This is an interesting issue. Do you find that this also occurs with when using the Octane Standalone? This issue may be a limitation of 3ds Max, but I will take a look into duplicating this issue.
If this is indeed an issue with the plugin specific (as opposed to Octane or 3DS Max), I will expand troubleshooting from there.
Cheers,
Azen
-
senorpablo
- Posts: 163
- Joined: Sun Jun 28, 2015 2:52 am
Azen,
Thank you for your response. I do not believe it is an issue with Max. The native render and iRay have no issue with the very same file path.
The standalone version will not load that path either. In fact, the error box lists the file path with the two folders truncated. It seems like Octane is interpreting the ".." as a DOS/UNIX recursive path, rather than as a string.
"D:\Textures\..NEW\ROCK_02-Chalkstone\Color.jpg"
becomes:
"D:\ROCK_02-Chalkstone\Color.jpg"
Thank you for your response. I do not believe it is an issue with Max. The native render and iRay have no issue with the very same file path.
The standalone version will not load that path either. In fact, the error box lists the file path with the two folders truncated. It seems like Octane is interpreting the ".." as a DOS/UNIX recursive path, rather than as a string.
"D:\Textures\..NEW\ROCK_02-Chalkstone\Color.jpg"
becomes:
"D:\ROCK_02-Chalkstone\Color.jpg"
- Octane path error.jpg (16.33 KiB) Viewed 3248 times
Hi,
I see. The issue is with Octane, rather than specific to the plugin. These kind of issues cannot be resolved by the plugin developers, so I will raise the issue with the core Octane dev team instead.
Worst case scenario, you may need to revise how you store your images. This issue doesn't come up too often, so I will see if there are better resolutions for you. There may be a system/drive setting on your computer that needs changing - for example, if I recall correctly, some file path issues have been known to arise from weirdly configured language settings (e.g. accessing from a computer set to Russian language settings from a computer set to English).
One question: is your D: a remapped drive on your computer or an external?
Cheers,
Azen
I see. The issue is with Octane, rather than specific to the plugin. These kind of issues cannot be resolved by the plugin developers, so I will raise the issue with the core Octane dev team instead.
Worst case scenario, you may need to revise how you store your images. This issue doesn't come up too often, so I will see if there are better resolutions for you. There may be a system/drive setting on your computer that needs changing - for example, if I recall correctly, some file path issues have been known to arise from weirdly configured language settings (e.g. accessing from a computer set to Russian language settings from a computer set to English).
One question: is your D: a remapped drive on your computer or an external?
Cheers,
Azen
The bug is in the file name class of Octane dealing with relative paths etc.. Will be fixed with the next release.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra