Octane / Lightwave error

[Godstrike]

I have a fairly heavy material in terms of high resolution texture maps.

At some point while working on it, Lightwave / Octane starts reporting the attached error message.

This happens randomly, and is not linked to a missing texture map as all the image being used are in the /images folder.

The error also does not identify what texture file is 'missing', only that '.0' texture file is missing.

The error tends to slow down Lightwave and Modeler to a crawl, and then eventually all links in the material are removed.

Has anyone seen this before, have ideas how to solve it?

[juanjgon]

Hi,

Somewhere in the scene you must have this ".0" texture file name, perhaps in a light or in a texture node. Can you send to me the scene with this problem to test it here?

Also this error should be seen only while loading the scene. Do you see it while working with the IPR?

Thanks,
-Juanjo

[Godstrike]

Hi Juanjo,

I have never used that name in any of the textures, which is weird -- the error just starts at some point.

I reduced the pixel size of all the textures and now the issue seems to have disappeared.

The scene is massive and the work under an NDA so I can't share it, I will try and recreate it with a personal job and send through.

Thanks
Carlo

[FrankPooleFloating]

GS, this happens when one inadvertently pops a character (or multiple, like in your case) into the Texture from file field, in the Octane Texture Image node, which I myself have accidentally done, when hitting the NumPad keys to maximize views... it would be wonderful if Juanjo could make this field so that it could only be populated by a path (read only, no write), generated from the button itself... Juanjo?

[juanjgon]

I'll check it, but I think that this is how the LW file widget works. I can't make the string field read only.

Thanks,
-Juanjo

[Godstrike]

Thanks for the insight FPF, will keep an eye out for that.