Bugs / Features still missing or missing answers!! [SOLVED]

[cea]

Hi,

Earlier this year I posted a bugs / missing features + questions on the forum.
A lot of them has gone unanswered, a few has been cleared up but mostly strange been ignored...

I have +20 new bugs/missing features on my list, but I won't bother writing them down and posting them if they are going to like last time.

So I will try again (under the bug section) since there has been more focus on Maya development the last few weeks, which is nice

viewtopic.php?f=28&t=52220

Especially no. 2) is a real pain at the moment, 15.000 frames and every frame has .####_passes.exr postfix. Remove the "passes" for the love of god or give an options for it - NO COMPOSTING / FRAME VIEWER SOFTWARE WANTS THAT!!!

[calus]

About the "_passes" filename suffix problem, I confirm this is the worst bug currently in Octane for Maya.

[calus]

Oh I get it !
Octane for maya use the default filename template from Octane Standalone:

standaloneTemplate.jpg (23.47 KiB) Viewed 5875 times

Except in Standalone we can change this dumb template.

Kai, if you read this Topic, a quick Fix for this major bug is to replace in the code the default filename template from "%n_%f_%p.%e" to "%n_%p_%f.%e".
(Hopefully this is not hard-coded in the SDK, if this is the case please tell me, I'll ask for a fix in standalone section)

But what was thinking the standalone team with this default template, did they already render a image sequence ?

[k.a.schubert]

Do you guys still want to use the Maya naming scheme in the Render Settings?
Which one do you use in this case?
Its not in the SDK, so I can change it directly.

Got the answer from ceas post.

[calus]

Very nice to read you can take care of this one Kai.

I sum up the problem here :
When you render a composite EXR sequence "_passes" is added at the the end of the file name, between the frame number and the extension for example:
name_0001_passes.exr

But every sequence player or postpro software need to have the frame number at the end of the file name just before the extension to accept an image sequence, for example :
name_passes_0001.exr

By the way the problem is the same with the pass files from a non composite EXR, for example :
name_0001_diffuse.exr should be name_diffuse_0001.exr to be usable.

Cea suggest to supress the "_passes" suffix totally but not sure it's possible as it might also suppress the pass name for passes when you render non composite EXR wich is needed.
So I suggest to simply put the pass name before the frame number, not after. In Standalone template language this would be "%n_%p_%f.%e".

But if you think suppressing the pass name is a better solution, for non composite EXR, pass files should be written in a specific sub-folder, if not they will overwrite themselves as they will have the same name.

Calus.

[k.a.schubert]

Suffix Problem is fixed in new version, see here 7.23

If there is still any bug here, please tell me asap.

[calus]

The update works nicely as long as we let the "file name prefix" field empty as by default "(not set; using scene name)" .
(though, "_ALLpasses" could be just "_ALL" for composite EXR).

But it's broken as soon as we need to define a name or a path either using Maya tokens or writing them in "file name prefix". In this case, batch rendering only output one frame with a wrong file-name.

[k.a.schubert]

I'm looking into the problem with "Render settings/Common/File Output/File name prefix" right now.

Edit: Fixed and build on the way.

[calus]

Don't know how familiar you are with "File name prefix" attribute in maya but I take the opportunity to push an idea about it which may be useful for later.

here is an example:

http://help.autodesk.com/view/MAYAUL/20 ... 599D4AE91E

this is really powerful and production proven, specially when dealing with thousands of images and tens of cameras, passes and maya render layers.
We can define here names and sub-folders, writing and using Maya Token keywords.

All render Token Keyword are not usefull/supported by octane. <renderPass> and <renderPassGroup> (maya software render specific), <renderPassType> (mental-ray specifique).
But maya API apparently allows to define custom Token keywords, we could define for example <PASS> which would give the octane pass name, e.g :
for myscene.mb "File name prefix" : <SCENE>/<PASS>/<SCENE>_<PASS> this would write every pass file for a non composite EXR in a sub-folder using the pass name, e.g : images/myscene/diffuse/myscene_diffuse.EXR

(again, not directly relative to our problem here but viewing this as a possible(or not) longer-term change may influence how you deal with our current issue)

[calus]

Edit: Fixed and build on the way.

haha that was quick ! thanks !!