Hi guys,
My apology for the late response.
@ Ciboulot - thank you so much for your feedback. Just to make the new workflow clear, we would start putting up small videos tutorial to help understand more about new features and changes.
Here is a quick little video of
Image Plane .
MAYA RENDER LAYERS and OVERRIDE
It seems it's' working with the recent and the previous branch. Would you please share us a sample scene?
MOTION VECTOR 2D PASS
This works correctly too.. we would try to upload a video on MB and MV 2D pass later this week.
REMAP TEXTURE NODE, GRADIENT TEXTURE (When would it be possible to get simple u ramp, v ramp, circle ramp, radial ramp, etc.) & SHADOW CATCHER ATTRIBUTE
Maybe these features are more related to SA feature request.
But, still, no visual feedback in the attribute editor?
Do you mean the color visual feedback or in IPR render? Try using ORBX material> Octane Gradient node.
Also, there is a workaround to use Maya's U,V, Circle, Radial etc.. or any Maya texture using the Octane Image texture node>"Baking Input pin" to bake Maya texture on the fly.
Please note, using this feature would impact the speed of your workstation.
BUGS
1. Could you please send me a sample of the Maya render layers with more details?
2. Try to enable "Pre-multiplied Alpha" from the "Imager" node and see if this fix the issue.
3. Visibility is working when we are using Maya HIDE/SHOW in viewport render. or is it something else?[/b]
"Error: file: C:/Program Files/Autodesk/Maya2016.5/scripts/others/createMayaSoftwareCommonGlobalsTab.mel line 36: setParent: Object 'commonTabColumn' not found."
- This is confirmed as Maya bug. It would not affect anything during the production workflow.
MOTION BLUR
Actually, there are only two new parameters in OFM "samples per frame" settings in both global and object's settings to smooth the motion blur and "The shutter time(%of frames)" from the Motion blur section.
Also, the Object settings Samples per frames can be used to override the global settings.
RENDERER NOT RESPONDING
Not sure if anyone has encountered the same issue? Please let us know if this happens with this release.
Cheers