Env var in file path ? Tweet

[fantome]

Hi guys ,
i see that this feature has been requested, but i haven't find a proper solve for now:
viewtopic.php?f=28&t=55580
i would like to know if it is possible to define at some place in maya or in windows, Local env var that could be use in file path both in hypershade and in the material orbx texture files.
i try to use the File path Editor to modify the path, but it look that it can't read octane loaders ?

i have just do the repath of every maps of 25 shaders this afternoon after we migrate to a new server and that was boring.
Especially when you know that in houdini, a simple $TEXTURE path modification would have do the job in 5seconds.

Cheers

[fantome]

after further investigation it looks that :

This is working properly with Maya standard image loader and Arnold :

Note that it looks that windows doesn't allow envar concatenation.
- you can just have %MY_VAR1%\my_path\image.png
- this doesn't look to work %MY_VAR1%\%MY_VAR2%\image.png
Env var access does work, you just need to modify it to update texture location, but this is kinda redundant with the Maya File Path Editor wich already work with arnold.

- >BUT you can't use env var with octane image file loader in hypershade :

this will not work in octane. It looks that the loader is not able to understand env var.

-> You also can' t use env var at all in standalone or in maya orbx material the browser does understand %MY_VAR1%\my_path\, but it doesn't store it in the file name, it just replace everything by the full path.

-> Same issue with Maya File Path Editor which doesn't look to work with octane orbx nodes, it does look to works with octane file loader.

it looks that you can only do that manually if you use the orbx material.
i think env var path are a must have feature for any serious pipeline.
that would be great to have them
Cheers

E

[BK]

Hi guys ,
i see that this feature has been requested, but i haven't find a proper solve for now:
viewtopic.php?f=28&t=55580
i would like to know if it is possible to define at some place in maya or in windows, Local env var that could be use in file path both in hypershade and in the material orbx texture files.
i try to use the File path Editor to modify the path, but it look that it can't read octane loaders ?

i have just do the repath of every maps of 25 shaders this afternoon after we migrate to a new server and that was boring.
Especially when you know that in houdini, a simple $TEXTURE path modification would have do the job in 5seconds.

Cheers

Hi Fantome,

Thank you so much for this.
We have created a feature request in our internal ticket system.

Hope we can implement it in future releases.

Regards

[fantome]

Thanks for your answer BK. however the fact that octane loader is working with path texture editor is great.

[BK]

Thanks for your answer BK. however the fact that octane loader is working with path texture editor is great.

hi Fantome,

Thank you so much! do you mean Octane loader as ORBX material?
We were confirmed the environment variables in paths is supposed to request to our Octane engine team.
Would you please post this request into our Feature request page https://render.otoy.com/requests/?

Cheers

[fantome]

Thanks BK for your feedback and the great support !

Yes the path texture editor work with octane image loader but it doesn't work when you use the orbx material and the standalone UI loaders.

BUT i have encounter weird behavior and bug with the texture path editor recently. like many features Autodesk do, they are only working half.
if you don't have a very clean naming conventions the editor mix everything and plug the wrong maps. to be sure you don't have bad suprise it's better to do per material texture folder, and replace the path per material, you are 100% sure that maya will not do some magic stupidity in your back.

I have fill the request
https://render.otoy.com/requests/?qa=62 ... ile-loader

Thanks again for your time.
Cheers
E

[JimStar]

I have fill the request
https://render.otoy.com/requests/?qa=62 ... ile-loader

You should have opened it in a Standalone section if you expect the engine team ever noticed it, not in Maya section.
As Bikram already mentioned - this is a lack of support of this at Octane engine level, nothing to do with plugins...

[fantome]

Thanks JimStar i have updated the RFE to standalone.