Maya Render Setup Displacement override

[seandunderdale]

Hey guys,

Im having an issue disabling specific displacement control nodes in Maya's Render Setup. Usually Id add the object / vrayDisplacement to a collection and drag and drop the attributes I want to override. However it seems I cant drag and drop the "none" attribute to switch off displacement calc.

The other option is to right-click on "none" and select "create absolute override" but my experience in Maya 2017 is that this generally creates a non-functioning AOV collection which is not deletable, and also doesn't even register the override. This then requires a restart or a Maya crash is right around the corner.

Any thoughts or workarounds? Such a simple thing really.

Im using Vray 3.6 and Maya 2017.

[oglu]

override the texture with black or gray color if you have a 16bit map...

[seandunderdale]

Does that disable any calculation / render time overhead? Id have thought the mesh would still be getting subdivided and displacement calculated, but it just has no extrusion.

Ive also found that I cant override Vray sun "enabled / disable" in Render Setup too.

We have tested the "absolute override" in a new scene, and found it does work for disabling the displacement, so I dont know what it is about working on a scene that causes it to start creating the error producing AOV collection that cant be deleted.

[seandunderdale]

What I've found so far is that with the renderer set to Arnold or Maya software, it will let me create an override for the displacement value "none".

But if I switch renderer to Vray, and try to repeat that override, it creates an AOV with "vrayDisplacement1" collection. But this override hasnt been applied and if I try to delete any of it, as mentioned before, Maya will crash shortly after.

[yolov]

I thought we fixed the problem with the non-deletable collection with 3.60.02. If you're not running this version, I'd recommend updating to the latest one available, which is 3.60.03 and trying again.
I can't really reproduce the problem that you're describing here on my end. If you could make a video capture that shows the steps, it would be of great help to us. Thanks in advance.

[seandunderdale]

Sorry! we are using 3.52.02

[yolov]

Ah, OK. Could you try with 3.60.03 just in case, I think this one in particular was fixed there.