Hi guys
we have a problem here for setting texture path for OctaneImageTexture node.
In our texture path we use an environment variable into that like this: $PROJECT_PATH/final/textures/barrel_001_color.tif
In maya's file node this works fine and show us the texture, but in OctaneImageTexture this path does not work fine.
There is any idea? this is force to us. The problem is with the Environment variable or Octane read texure paths in another way?
thanks in advance.
Environment Variables in texture path
Moderator: JimStar
- k.a.schubert
- Posts: 137
- Joined: Mon Feb 22, 2016 2:52 am
This feature has been requested by another user as well,
when redoing the texture nodes, I can bring it in...
when redoing the texture nodes, I can bring it in...
In V2 the OctaneImageTexture.file attribute is not recognized by maya as a file path(lacking the usedAsFilename tag ), just as a string attribute,
so I think that's why Maya can't use its builtin autoExpand fonctionnalities with this attribute as it does with Maya node fileTextureName attributes.
Ideas from the top of my head to workaround this (but depends how these pathes are set):
1/
- create your own AEtemplate.mel for the OctaneImageTexture node template with a corrected File attribute.
(also I think there's other ways to override only the template for this attribute, but woud have to do some research)
2/
- Add an extra string attribute to every OctaneImageTexture node (but using usedAsFilename tag), write Path in this extra attribute and connect it to the to the File attribute.
3/
- Expand the OctaneImageTexture.file pathes with "pre render mel" and put them back wth "post render mel" but doesn't work for IPR I think
4/
- As it's only about $PROJECT_PATH you could just use relative path without env variable, and add your specific pathes to "sourceimage" in every local workspace.mel, or add them to the virtual worspace at render time with the workspace command.
so I think that's why Maya can't use its builtin autoExpand fonctionnalities with this attribute as it does with Maya node fileTextureName attributes.
Ideas from the top of my head to workaround this (but depends how these pathes are set):
1/
- create your own AEtemplate.mel for the OctaneImageTexture node template with a corrected File attribute.
(also I think there's other ways to override only the template for this attribute, but woud have to do some research)
2/
- Add an extra string attribute to every OctaneImageTexture node (but using usedAsFilename tag), write Path in this extra attribute and connect it to the to the File attribute.
3/
- Expand the OctaneImageTexture.file pathes with "pre render mel" and put them back wth "post render mel" but doesn't work for IPR I think
4/
- As it's only about $PROJECT_PATH you could just use relative path without env variable, and add your specific pathes to "sourceimage" in every local workspace.mel, or add them to the virtual worspace at render time with the workspace command.
Pascal ANDRE