Community
Arnold for Maya Forum
Rendering with Arnold in Maya using the MtoA plug-in.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

After update '[aov] cannot convert AOV "object" to type "RGB"' Causes crash

6 REPLIES 6
Reply
Message 1 of 7
michael_hansen
435 Views, 6 Replies

After update '[aov] cannot convert AOV "object" to type "RGB"' Causes crash

Can anyone help?


[Arnold]: 00:00:52 6809MB ERROR | [aov] cannot convert AOV "object" to type "RGB"


I keep receiving this error after updating the Arnold renderer from 4.x to 5.0. The render window will pop up, or the Arnold render view will pop up but it'll immediately disappear and then crashed the second time. This is a huge problem because I met a really pivotal point. If anybody could help me out that would be great!

Tags (2)
Labels (2)
6 REPLIES 6
Message 2 of 7

Do you have a custom AOV named "object" ?
That will conflict with the built-in "object" AOV, which is of type NODE



// Stephen Blair
// Arnold Renderer Support
Message 3 of 7
Anonymous
in reply to: michael_hansen

Hi, this always happens with Arnold 7, in 3ds max. No way for me to start a render with object or shader aovs.


Also simply doing:

1 - start 3ds, empty project.

2 - draw a cube (or what you want)

3 - open aovs tab, click on "new exr", then add/drag object OR shader aovs in

4 - start render

5 - always aborts with: "ERROR | [aov] cannot convert AOV "object" to type "RGB"

(or the "shader" one)

Message 4 of 7

What are you doing with those AOVs? They are built-in AOVs of type NODE.
The Arnold Render View uses the Object AOV for picking.



// Stephen Blair
// Arnold Renderer Support
Message 5 of 7

@Luca Frizzarin Even though you have the same problem it's great to know that somebody out there is having the exact same issue as I am.


The only thing I could do to solve this issue, because it's similar to Luca's, was to strip off the newest version of Arnold renderer, it was something in the 5.0 area and it was necessary to drop it back down to the 4.0 version.


@Stephen Blair I don't have a custom AOV name the object. The only once I'm using are a custom for ambient occlusion otherwise all the others are default. Is there a way I can double-check but I don't have an AOV name the object? I'm going through the AOV menu and there's no such thing there. I'm not really sure what to do if I want to update, I don't know if it has to do something with my version of 3D Studio Max which is updated to the newest build, but I reset the software and everything but I would still get the same crash during each render. I kind of want to snapshot my build info on my secondary machine to see if I can recreate the error but I don't really have the time at the moment because there's a deadline coming up. But if you have any other ideas please let me know, this is very weird.

Message 6 of 7
Stephen.Blair
in reply to: Anonymous

I guess you are not Arnold Render View? That doesn't abort.

object and shader are built-in AOVs that are NODE type (not RGB), so they can no longer be used an RGB AOVs.



// Stephen Blair
// Arnold Renderer Support
Message 7 of 7

So, this happens only with older scenes, not with new scenes?


The Arnold Render View uses the object AOV for object picking. ActiveShade and Production don't do that.

If you don't have any AOVs listed in the AOV manager, then no AOVs should be rendered.

You can see the AOVs in the Arnold log:

maxtoa-arnold-log-aovs.png


Maybe you can remove all the geometry from a scene and upload that?



// Stephen Blair
// Arnold Renderer Support

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report