Octane path not working for Archive and Path editor[SOLVED] Tweet

[calus]

Hi Kai,

I investigated the issue and maybe find the solution to this topic :
viewtopic.php?f=28&t=53625&start=10

I discovered that these attributes are not recognized as file path by Maya:
octaneImageTexture.File
octaneAlphaImageTexture.File
octaneFloatTexture.File

as a consequence the File Path Editor can't work with these nodes
and the "Archive Scene" function in File menu doesn't work for them either.
SOLUTION:
At creation time these attributes should be tagged with the -usedAsFilename tag.

(As you are refactoring the octaneMaya nodes creation process, I think this information may be useful just now )

[k.a.schubert]

Hi calus,

as always your input is very useful!

[Jolbertoquini]

Hi Kai,

I investigated the issue and maybe find the solution to this topic :
viewtopic.php?f=28&t=53625&start=10

I discovered that these attributes are not recognized as file path by Maya:
octaneImageTexture.File
octaneAlphaImageTexture.File
octaneFloatTexture.File

as a consequence the File Path Editor can't work with these nodes
and the "Archive Scene" function in File menu doesn't work for them either.
SOLUTION:
At creation time these attributes should be tagged with the -usedAsFilename tag.

(As you are refactoring the octaneMaya nodes creation process, I think this information may be useful just now )

As I publish on the post with the file texture manager modified why not have something similar maybe...

[calus]

Hi Jo,

Yes this is a really nice tool and it is perfect to workaround the issue in the Itsallgoode9's use-case, but here I'm talking about the bug in the octane.file attribute that prevent builtin Maya functionalities to work with octane image nodes.

(by the way you forgot to add octaneAlphaImageTexture node and octaneFloatImageTexture node to the script, and also to modify in the description the name of the procedure, FileTextureManagerOCT instead of FileTextureManager, this may confuse Itsallgoode9 )

[Jolbertoquini]

Hi Jo,

Yes this is a really nice tool and it is perfect to workaround the issue in the Itsallgoode9's use-case, but here I'm talking about the bug in the octane.file attribute that prevent builtin Maya functionalities to work with octane image nodes.

(by the way you forgot to add octaneAlphaImageTexture node and octaneFloatImageTexture node to the script, and also to modify in the description the name of the procedure, FileTextureManagerOCT instead of FileTextureManager, this may confuse Itsallgoode9 )

Great!!

[calus]

Issue solved in plugin version 2.26.1 - 7.20.3