Octance absolute path not working

[Vyoor]

Absolute path in file output is not working. Octane is puting relative path to project's images directory before absolute path and trying to write images nowhere without any error.

For example:
X:/My_Project/images/Y:\Output_Images\output_file.###.png

Second problem is that it don't makes new output folders - they should be existing. If not the Octane is writing images nowhere again (no error). This is huge issue with incremental directory names.

Win 7, Win 10
GTX 780, GTX 1080 Ti
v 3.06.4 - 11.7
Maya 2017 Update 4

[BK]

Absolute path in file output is not working. Octane is puting relative path to project's images directory before absolute path and trying to write images nowhere without any error.

For example:
X:/My_Project/images/Y:\Output_Images\output_file.###.png

Second problem is that it don't makes new output folders - they should be existing. If not the Octane is writing images nowhere again (no error). This is huge issue with incremental directory names.

Hi Vyoor,

Please make sure to set project while working with Octane render for Maya and make sure no multiple instances of Maya are opened.
Have you set up the "Environment varibles" yet? if not - [ viewtopic.php?p=214980#p214980 ]


Also, make sure to use forward slash / to create a new output folder. For example: ...... -rd images/shot_10 closeup.mb

[Vyoor]

The problem is that I need to render frames to other location, outside of the project. And also I need to have scene name folder in file path so new folders every increment are necessary. It's required by our pipeline.

[calus]

Absolute path in file output is not working. Octane is puting relative path to project's images directory before absolute path and trying to write images nowhere without any error.

right, but this is not an Octane issue, Maya by default use a relative root render directory, but :

1 - In the "Project window" you can define an absolute path instead of the "images" folder:

2 - Alternatively you can override the relative path with command line batch render by using the -rd tag

Code: Select all

render -r octane -rd Y:\Output_Images\

Second problem is that it don't makes new output folders - they should be existing. If not the Octane is writing images nowhere again (no error).

Hum it works for me, we had this bug in old plugins but this is fixed :
If in "output file" I have test2/myscene then the "myscene" files are rendered in a "test2" folder created at render time at the root render directory.

If you noticed this issue with recent plugin can you share a sample scene with the problem ? (not supposed to happen)

[BK]

Thank you Calus !!

[BK]

The problem is that I need to render frames to other location, outside of the project. And also I need to have scene name folder in file path so new folders every increment are necessary. It's required by our pipeline.

Hi Vyoor,

Has the problem been solved? Please let us know

[Vyoor]

Hi!

Unfortunatelly not. After every save of the scene relative path appears in the filenamename prefix , it's forced by our pipeline i don't have control over it. Changing path in project window not working because it's still adding path to somewhere - it's impossible to clear it completely.
Octane is combining Path and Filename what make the output location not propper.



I just need to have the absolute path independent from the project location. Frames should be rendered exactly in the place indicated in the File name prefix.
My company is planning to introduce octane to our pipeline but this is the main barrier.

It's working without any issues in other renderers like Arnold, Redshift.

[calus]

Hi!

Unfortunatelly not. After every save of the scene relative path appears in the filenamename prefix , it's forced by our pipeline i don't have control over it. Changing path in project window not working because it's still adding path to somewhere - it's impossible to clear it completely.
Octane is combining Path and Filename what make the output location not propper.



I just need to have the absolute path independent from the project location. Frames should be rendered exactly in the place indicated in the File name prefix.
My company is planning to introduce octane to our pipeline but this is the main barrier.

It's working without any issues in other renderers like Arnold, Redshift.

If it works with Arnold and Redshift this is because both renderers have implemented an extra feature (but not the same way) to detect absolute path in the filename prefix and override the project image path,
but it's not a Maya built-in feature : you can check with the Maya Software renderer you'll have the exact same result as with Octane.
Your Pipeline TD should know that it's not the best practice to use the filename prefix as a way to set the image path,
one can't expect every renderer to have this same extra feature, there are cleaner ways to override render directory path with builtin mel/python command.

Nevertheless this would be a handy feature to implement in OctaneForMaya, but it's not a bug it's a feature request : https://render.otoy.com/requests/?qa=

[BK]

Thank you Calus, for your help !!

@ Vyoor,

Agreed with Calus, Octane is working exactly how Maya software renderer.

Please consider using the Project window to modify the render paths. Maya file name prefix parameters can be used to create subfolders and name of rendered images, for example: "<Camera>/<RenderLayer>/Draft_3_<Scene>_<RenderPass>"

Overriding these Relative paths with the Absolute path will be available in Octane after we finish our refactored Octane for Maya plugin.

Hope this help !!!

[Vyoor]

It's could be very hard to force this kind of changes in our pipeline but I will try waiting for refactored plugin.
Calus, BK, Thank You for help!