Problem summary
The LookFileOverrideEnable node has the "userLocation" that can be customized.
Within the LookFileManager supertool this is not exposed. When you enter the node ( Ctrl + LClick the node ) and set changes to a user-specified location within the LookFileOverrideEnable node, the look override breaks.
It appears the merge node is not taking on the attribute "lookfileMap".
Adding it as a preferredInputAttributes variable solves this and enables the overridden material to be rendered.
Customer reported version
katana.2.6v4
Customer reported platform
centos7
Steps to reproduce
1) Setup your Look File scene: ( download attached file or follow example screenshot):
2) Enter your LookFileManager node ( Ctrl + Middle Click the node )
3) Within the LookFileOverrideEnable node, set locationForMaterials to 'user-specified' and userLocation to '/looks' :
4) Exit the SuperTool and preview render the scene at the PrmanGlobalStatements node.
Result: The object will not have the overridden material file.
Workaround
1) Follow the reproduction paths above up to Step 3
2) Enter the Merge node and set showAdvancedOptions to Yes.
3) Add the following to the preferredInputAttributes attribute: ( name: lookfileMap , index: 1 )
4) Exit the SuperTool and preview render the scene at the PrmanGlobalStatements node.
Result: The overridden material will be rendered as expected.
Reproduced by support
This bug has been reproduced in:
Katana2.6v4 - Windows 7 - CentOS6.9
Katana2.6v1 - Windows 7 - CentOS6.9
Katana2.5v7 - Windows 7 - CentOS6.9
Katana2.5v1 - Windows 7 - CentOS6.9
Katana2.1v6 - CentOS6.9
Katana2.1v1 - CentOS6.9
Katana2.0v1 - CentOS6.9
Earliest version tested
- This issue appears to be in all versions of the product Expected behaviour
User-specified look file locations should work when enabled within a LookFileManager node
Actual behaviour
User-specified look file locations do not work when enabled within the LookFileManager SuperTool, render uses default values.
