Scene Keyword not replacing correctly

[nogardvfx]

When rendering with a scene file named like "name__##.ma" (notice two underscores), the keyword <SCENE> in "File Name Prefix" gets replaced by "name" instead of "name__##". For example, if my scene is called "testOutputName__01.ma", the <SCENE> gets replaced with "testOutputName" but I'd like it to use "testOutputName__01" instead. Is this intended? I'm using vray 3 btw. Is there a way to get the actual output directory? I'm currently using python code:

cmds.renderSettings(layer="masterLayer", fullPath=True, firstImageName=True

which gives me "testOutputName__01" instead of "testOutputName".

This doesn't seem to happen when there's just one underscore or when there are letters followed by the two underscores.

Cheers,
-Chris

[svetlozar.draganov]

It seems it works fine here:


What is the exact versions/service pack of V-Ray/Maya/OS?
A step by step instructions how to reproduce the issue would be very helpful also.

[Morbid Angel]

Is that under linux?

[nogardvfx]

Yup. I'll get all the info.
-Chris

[nogardvfx]

I'm using vray 3.05.04.25245_2015 with Maya 2015 on Centos 6. I'm rendering this via maya's Render from the command line. More info here - http://knowledge.autodesk.com/suppor...-line-htm.html

When I render from Render > Render Current Frame in Maya UI, it works fine. But when I run this from the shell:

Render -s 1 -e 1 -b 1 -rl masterLayer -r file -rd /path/to/maya/project -preRender 'loadPlugin vrayformaya.so;' /path/to/maya/scenes/testOutputName__01.ma

It takes out the "__01" in the output image. Is this the case on your side?

Thanks

[svetlozar.draganov]

Thank you very much for the clarification.
We managed to reproduce the issue - we will log it into our system and we will let you know when we have some updates about it.

[nogardvfx]

Just checking to see if there is any update. This is holding up some development on our end.

Cheers,
-Chris

[svetlozar.draganov]

The issue is with high-priority and we already have a developer looking into it.
We'll let you know as soon as we have some updates about it.

[nogardvfx]

Great thank you very much.

Cheers,
-Chris

[svetlozar.draganov]

This issue has been fixed for the next official service pack.

[ivaylo.ivanov]

It's in the stable 3.0 nightly also.