CUDA error when using displacement on the GPU.

CUDA error when using displacement on the GPU.

Anonymous
Non applicable
3 479 Visites
10 Réponses
Message 1 sur 11

CUDA error when using displacement on the GPU.

Anonymous
Non applicable

I get this error on some scenes when using a Maya displacement shader on the GPU:

// Error: [gpu] an error happened during rendering : Unknown error (Details: Function "_rtContextLaunch2D" caught exception: Encountered a CUDA error: cudaDriver().CuEventSynchronize( m_event ) returned (700): Illegal address, file: <internal>, line: 0) //

I am using a RTX 2070 Super.

The error occurs on a scene basis, it will begin happening randomly as far as I can tell and doesnt occur all the time even with the exact same shader setup in a different.

The same scene on the CPU renders with no issue.

Ignoring displacement in the diagnostics doesn't stop the error. The image texture and/or displacement shader has to be disconnected in the node editor. The scene will render with the same shader network if the displacment is disconnected (Maya restart is required). Using Arnold subdivision works fine, its only displacement.

I have tried up and down grading the MtoA version as well as installing different Nvidia drivers (both game and studio editions).

I do get a fatal GPU error occasionally when updating a scene in the render view, maybe its related.

Cheers.

0 J'aime
3 480 Visites
10 Réponses
Replies (10)
Message 2 sur 11

Anonymous
Non applicable

I get the same error. I managed to track it down to specifically using cell noise to drive displacement. Regular noise works fine, but as soon as any path including cell noise gets used for displacement, I get this error and am unable to render.

I'm using an RTX 2080, with Houdini and Arnold 6.0.4.0 on Ubuntu 18.04.5.

0 J'aime
Message 3 sur 11

DeclanRussell
Autodesk
Autodesk

Hi Piers,

I tried to repro your crash. I just had a simple polygon sphere and used a cell noise as the displacement but did not experience the crash. Is there something extra I need to do to reproduce the crash, or better yet do you have a simple .ass file that I can use to repro?

Cheers,

Dec

0 J'aime
Message 4 sur 11

Anonymous
Non applicable

I experimented a bit more and found that there were a few more things in my material that were required in order for it to crash. I've attached a .hiplc that contains a minimal example. If any of the six nodes in the material are removed, the crash no longer occurs – this is true even though the two multiply nodes simply multiply the input by 1.

error.hiplc.zip

0 J'aime
Message 5 sur 11

DeclanRussell
Autodesk
Autodesk

Thanks for this repro, it was super helpful! I was able to reproduce the crash on my machine and also diagnose the issue. We have it logged internally as ticket #10050 for future reference. Unfortunately, I haven't currently come up with a good workaround. I'll keep you posted if I think of one.

0 J'aime
Message 6 sur 11

XtaaZ
Contributor
Contributor

Hi, the same happens to me on a scene that was perfectly working less than 24hours ago. If I ignore displacement, it's working, otherwise same error.

I tried both latest Game Ready and Studio driver, doesn't change anything.

0 J'aime
Message 7 sur 11

DeclanRussell
Autodesk
Autodesk

An update on this. We have a workaround to stop the crash that will be coming in the next bug fix release. The workaround essentially means that we disable autobump when this case pops up. This is far from ideal I know, but its better than a crash. A real fix will come when we move to OptiX 7.

0 J'aime
Message 8 sur 11

a_neilson
Explorer
Explorer

Having exact same issue with 3DS Max and RTX 3080.

Arnold: 4.2.2.20

NVIDIA: 360.89

[Arnold]: 00:04:14 7372MB ERROR | [gpu] an error happened during rendering : Unknown error (Details: Function "_rtContextLaunch2D" caught exception: Encountered a CUDA error: cudaDriver().CuEventSynchronize( m_event ) returned (700): Illegal address, file: <internal>, line: 0)




0 J'aime
Message 9 sur 11

thiago.ize
Autodesk
Autodesk

This is unfortunately a generic error message that could be triggered in many ways. Is this happening because of displacement, which should now be fixed? If it's a new problem, please post a new arnold answers question so we can make sure it gets the attention it deserves.

0 J'aime
Message 10 sur 11

Anonymous
Non applicable

I have also hit this problem when using Maya 2020 + Arnold 4.2.2. Arnold outputs a similar error message when my GPU memory is still clearly sufficient.

I don't know why Arnold don't like the height map I used. Would be great if anyone can give any workarounds. Arnold also needs to output a better error message.

0 J'aime
Message 11 sur 11

Anonymous
Non applicable

I was having a similar error trying to create scratches on glass. It just stopped rendering. I created a new scene in Maya and imported the old scene and it fixed it for me.

0 J'aime