OTOY Forums

Hello. From time to time, I have crashes because of the way octane reads some images (in any case, as I understand it for now). Bugreport in the attachment. If you save the image, or just rename it, the octane reads the image wonderfully. But if you immediately rename it back, then the bug returns, and there are no invalid characters in the name.
Now I have crashes when using the texture with the name "rock-02_200cm_color_8k", and
"rock-02_200cm_color_8k_1" [in same folder] - no problem
"rock-02_200cm_color_8k_copy" [in same folder] - no problem
if you rename the copy back to the original - crashes.
Everything would be fine, re-saving is often not a problem, but the inconstancy of this error from time to time causes some concern.
I would be very grateful if someone would suggest a solution, because in other way if you rename textures in libraries every time, the paths will break in other projects.

Version and OS? It can read any filenames with any character set. Are you sure that your pathname is not too long?

win 10, cinema 4d r19 . I try it on Octane 2019.1.1 and Octane 2019.1.2 - same result.
It is interesting that transferring 3 texture maps (of which diffuse and normal had a reading problem) to another folder (project folder) - for diffuse this solved the problem and for the normal map it did not. Only the re-saving of the normal map with Photoshop helped. I put a normal map to the post, (the version that I haven’t read) maybe it will help to find the problem.
__
Path_1 : "G:\Res\tex\Substance_Store_RDT_Collection\RDT_ONE_2_7\ROCK-02\" (where it original was)
Path_2 : "D:\Work\Commercial\[Repeateble]\Avrora\19_10_25_Block_1_2\c4d\tex\" (project folder)

What's your driver?

440.97

What happens if you try with latest studio driver? 431.86
Select CLEAN install option

I can check as soon as I finish with active projects, tentatively this is the end of the week. So far, I just re-saved that image, but if we will find some solution for the future, it will be wonderful. Therefore, I will definitely double-check this on other versions of drivers, only at the moment where it will not harm work.

I never seen an issue like you described so why I ask you to try different drivers.

Hey. I just tested on latest version Octane and 441.08 driver - all works perfect