List of Known Arnold 6.3.4 Solaris Bugs + QOL Suggestions for Next Update

[jwkimXJ5XR]

I first want to thank the team for fixing so many bugs in the recent release, you guys are seriously awesome!
Just to highlight a few persisting bugs that I have encountered even after updating as well as some suggestions for QOL features for the next updates: 

Overall Rendering Bugs

1. Arnold does not render in ACEScg colourspace unless render product type is 'arnold'

2. Cryptomattes do not work unless render product type is 'arnold'

3. MPlay rendering does not work with the 'arnold' render product type

4. Nuke does not recognize RGBA as lowercase rgba unless product type is set to 'arnold'

5. Directories / folders will not be automatically generated when rendering with 'arnold' product type

6. Camera motion blur does not work properly when the camera of the scene is a sublayer of the usd file being

rendered. (If the camera was created in a different scene and imported as a .usd the camera motion blur seems to not work, same goes for the associated motion vector AOVs. This happens regardless of using the motion blur node or not)

7. Rendering will become unstable and buggy when multipart and autocrop are turned on at the same time in the render settings while using 'arnold' render product type

8. Cryptomattes not supported in GPU rendering (Probably a missing feature more than a bug, just wanted to mention in case)

Dome Light Bugs

1. Dome light hdri does not display in the background viewport renders in Houdini 20.5

2. Dome light colourspace is not correct unless the HDRI is specifically exported in Raw colourspace ( Karma will for example recognize HDRIs in Linear Rec. 709 (sRGB) which most available HDRIs exist in, Arnold does not. )

QOL Suggestions:

1. Let us pick a file instead of inputting the File Name path manually

- In Karmas case there is a file picker for the Output Picture parameter. This would be an awesome change for the Arnold Render Settings node as well, seeing as currently we have to create the path manually:

- To fix this it would be as easy as to change the parameter type from a simple 'String' to a 'File' but it would be nice to have this be implemented in the official node. 

2. Have the Camera Resolution be automatically recognized from the chosen render camera

- To use Karma as an example again:

- Karma automatically will recognize the aspect ratio of the camera while still being able to adjust the overall image resolution manually. It also lets us choose to use a manual resolution independent of the render camera. At the moment there is no such options for Arnold which makes the initial aspect ratio we set the camera to be rendered useless. 

Would love if other users could post some reoccurring bugs or suggestions for features in the comments of this post!

[tom_minor-arnold]

Hey,

Thanks for spending the time to compile a detailed list, I appreciate it!

Here's a list of most of the tickets (a couple are missing, we'll update the thread again soon):

Overall Rendering Bugs

1. Logged as HTOA-2753
2. Logged an investigation ticket as HTOA-2754, but we're currently unsure if this is possible yet
3. Logged as HTOA-2755
4. Logged as usd#2115

5. Logged as HTOA-2756

7. Logged a new ticket as HTOA-2757 specifically for the instability during rendering, but there's also an existing ticket - HTOA-2308 (kick crash with autocrop and non standard dataWindowNDC in Houdini) which sounds similar
8. GPU cryptomatte is logged as ARNOLD-11042

Dome Light Bugs

1. Already logged as HTOA-2712, this is a known issue on SideFX's side.
This only happens in the Vulkan viewport, so a workaround is to temporarily switch to the OpenGL viewport (Edit > Preferences > 3D Viewports)
2. Logged as HTOA-2758

QOL Suggestions

1. Good spot, logged as HTOA-2759 (Add a file picker to 'Output Picture' on Arnold Render Settings)
2. Logged as HTOA-2760 (Automatically set resolution from camera in Arnold Render Settings)

Thanks!

Tom

[rachid_1]

Hi
Dome light AOV light Group is broken

and this is not SideFx's issue, Hope you can log this as a bug!
Thanks

[jwkimXJ5XR]

Thank you so much for all your efforts!

An additional bug that I encountered:

9. GPU Rendering will not render out Deep images ( DeepEXR driver ). It seems to render, but no images are written out to disk. 

[francoislord]

I would like to add one to these.

In the Arnold Render Settings LOP, several parameters cannot be deactivated. When you render out several passes which all share a single Render Settings lop, and then you just want to override one parameter (say the File Name), you have to also override the resolution, the driver, the product type, etc.

All parameters should be deactivatable.