Community
Arnold for 3ds Max
Rendering with Arnold in 3ds Max using the MaxtoA plug-in.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

GPU rendering error(s)

3 REPLIES 3
Reply
Message 1 of 4
Mahagar
1054 Views, 3 Replies

GPU rendering error(s)

Hello, I have a scene I work on in Maya 2020 and Arnold 5.0 GPU. Yesterday everything worked fine while I was lookdeving the scene until some point when I suddenly got GPU fatal error, please restart application. It happened without me adding any new texture or tweaking the render samples. Just like that. So this morning when I opened it again, I am unable to render anymore, because after few iterations (meaning rendering actually starts) it will say Render Aborted. My console displays this:


00:00:02 900MB | log started Wed Nov 10 08:15:06 2021

00:00:02 900MB | Arnold 7.0.0.0 [47ab20b9] windows clang-10.0.1 oiio-2.3.2 osl-1.12.0 vdb-7.1.1 clm-2.0.0.235 rlm-14.1.3 optix-6.6.0 2021/10/07 01:16:30

00:00:02 900MB | 1 x Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (8 cores, 16 logical) with 65337MB

00:00:02 900MB | NVIDIA driver version 472.39 (Optix 60801)

00:00:02 900MB | GPU 0: NVIDIA GeForce RTX 2080 @ 1710MHz (compute 7.5) with 8192MB (7157MB available) (NVLink:0)

00:00:02 900MB | Windows 10 (version 10.0, build 19042)

00:00:02 900MB | soft limit for open files changed from 512 to 2048

00:00:02 900MB |

00:00:02 900MB | [color_manager_ocio] default ocio.config found in C:\Program Files\Autodesk\Arnold\maya2020\bin\..\ocio\configs\arnold\config.ocio

00:00:02 900MB | loading plugins from C:\Program Files\Autodesk\Arnold\maya2020\bin\..\plugins ...

00:00:02 901MB | alembic_proc.dll: alembic uses Arnold 7.0.0.0

00:00:02 901MB | cryptomatte.dll: cryptomatte uses Arnold 7.0.0.0

00:00:02 901MB | cryptomatte.dll: cryptomatte_filter uses Arnold 7.0.0.0

00:00:02 901MB | cryptomatte.dll: cryptomatte_manifest_driver uses Arnold 7.0.0.0

00:00:02 901MB | synColor_shaders.dll: color_manager_syncolor uses Arnold 7.0.0.0

00:00:03 925MB | usd_proc.dll: usd uses Arnold 7.0.0.0

00:00:03 925MB | loaded 6 plugins from 4 lib(s) in 0:00.14

00:02:43 11643MB WARNING | unable to create log file C:/Users/adria/Desktop/log.1.*: Invalid argument

ERROR | [polymesh] /PROPS/group29/Aset_stone_rough_S_ufllcisva_00_LOD2/Aset_stone_rough_S_ufllcisva_00_LOD2Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_stone_rough_S_ufllcisva_01_LOD2/Aset_stone_rough_S_ufllcisva_01_LOD2Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_nature_rock_S_vbuxda0iw_00_LOD1/Aset_nature_rock_S_vbuxda0iw_00_LOD1Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_stone_rough_S_ufllcisva_03_LOD2/Aset_stone_rough_S_ufllcisva_03_LOD2Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_nature_rock_S_vbuxda0iw_02_LOD1/Aset_nature_rock_S_vbuxda0iw_02_LOD1Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_stone_rough_S_ufllcisva_00_LOD3/Aset_stone_rough_S_ufllcisva_00_LOD3Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_stone_rough_S_ufllcisva_01_LOD3/Aset_stone_rough_S_ufllcisva_01_LOD3Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_stone_rough_S_ufllcisva_03_LOD3/Aset_stone_rough_S_ufllcisva_03_LOD3Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_nature_rock_S_vbuxda0iw_00_LOD2/Aset_nature_rock_S_vbuxda0iw_00_LOD2Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_nature_rock_S_vbuxda0iw_02_LOD2/Aset_nature_rock_S_vbuxda0iw_02_LOD2Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_stone_rough_S_ufllcisva_00_LOD4/Aset_stone_rough_S_ufllcisva_00_LOD4Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_stone_rough_S_ufllcisva_01_LOD4/Aset_stone_rough_S_ufllcisva_01_LOD4Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_nature_rock_S_vbuxda0iw_00_LOD3/Aset_nature_rock_S_vbuxda0iw_00_LOD3Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_stone_rough_S_ufllcisva_03_LOD4/Aset_stone_rough_S_ufllcisva_03_LOD4Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_stone_rough_S_ufllcisva_00_LOD5/Aset_stone_rough_S_ufllcisva_00_LOD5Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_nature_rock_S_vbuxda0iw_02_LOD3/Aset_nature_rock_S_vbuxda0iw_02_LOD3Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_stone_rough_S_ufllcisva_01_LOD5/Aset_stone_rough_S_ufllcisva_01_LOD5Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_stone_rough_S_ufllcisva_03_LOD5/Aset_stone_rough_S_ufllcisva_03_LOD5Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_nature_rock_S_vbuxda0iw_00_LOD4/Aset_nature_rock_S_vbuxda0iw_00_LOD4Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_nature_rock_S_vbuxda0iw_02_LOD4/Aset_nature_rock_S_vbuxda0iw_02_LOD4Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_nature_rock_S_vbuxda0iw_02_LOD5/Aset_nature_rock_S_vbuxda0iw_02_LOD5Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_stone_rough_S_ufllcisva_00_LOD6/Aset_stone_rough_S_ufllcisva_00_LOD6Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_stone_rough_S_ufllcisva_01_LOD6/Aset_stone_rough_S_ufllcisva_01_LOD6Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_nature_rock_S_vbuxda0iw_00_LOD5/Aset_nature_rock_S_vbuxda0iw_00_LOD5Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_stone_rough_S_ufllcisva_03_LOD6/Aset_stone_rough_S_ufllcisva_03_LOD6Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

ERROR | [polymesh] /PROPS/group29/Aset_nature_rock_S_vbuxda0iw_02_LOD6/Aset_nature_rock_S_vbuxda0iw_02_LOD6Shape: incorrectly defined UV coordinates, missing either uvlist or uvidxs

00:02:59 15397MB | [color_manager] using color manager of type "color_manager_syncolor"

00:02:59 15397MB | [color_manager] rendering color space is "scene-linear Rec 709/sRGB" with declared chromaticities:

00:02:59 15397MB | r(0.6400, 0.3300) g(0.3000, 0.6000) b(0.1500, 0.0600) and w(0.3127, 0.3290)

00:02:59 15399MB |

00:02:59 15399MB | rendering image at 1920 x 817, 5 AA samples

00:02:59 15399MB | AA samples max 50

00:02:59 15399MB | AA adaptive threshold 0.03

00:02:59 15399MB | AA sample clamp <disabled>

00:02:59 15399MB | diffuse samples 2 / depth 1

00:02:59 15399MB | specular samples 2 / depth 1

00:02:59 15399MB | transmission samples 2 / depth 1

00:02:59 15399MB | volume indirect samples 2 / depth 1

00:02:59 15399MB | total depth 10

00:02:59 15399MB | bssrdf samples 2

00:02:59 15399MB | transparency depth 10

00:02:59 15399MB | node initialization done in 0:00.00 (multithreaded)

00:02:59 15399MB | updating 2314 nodes ...

00:02:59 15399MB | node update done in 0:00.00 (multithreaded)

00:02:59 15399MB | [gpu] GPU update done in 0:00.000

00:02:59 15399MB | [aov] parsing 2 output statements ...

00:02:59 15399MB | [aov] registered driver: "arv_display" (driver_arv)

00:02:59 15399MB | [aov] * "RGBA" of type RGBA filtered by "defaultArnoldFilter/gaussian_filter" (gaussian_filter)

00:02:59 15399MB | [aov] * "object" of type NODE filtered by "_renderViewDefault/closest_filter" (closest_filter)

00:02:59 15399MB | [aov] done preparing 4 AOVs for 2 outputs to 1 driver (0 deep AOVs)

00:02:59 15283MB | starting render ...

00:02:59 15283MB | [gpu] building scene and compiling shaders ...

00:02:59 15283MB | [gpu] building scene and compiling shaders done in 0:00.000

00:03:00 15436MB | 0% done -- estimated remaining time = 3740.0s

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

GPU 0 had 7157MB free before rendering started and 312MB free when crash occurred

GPU errors are sometimes due to a GPU not having enough remaining free memory. To see if this is what happened here, try simplifying your scene or running on a GPU with more free RAM to see if it solves the crash. Otherwise, upgrading to the latest nvidia gpu driver and Arnold core (available from www.arnoldrenderer.com) might fix the crash

00:03:02 15508MB | render done


Now, I can see that log mentions possibility of running out of memory, but my question is HOW the heck it would it eat all my GPU memory - my scene textures certainly dont take up 8GB... And yes, they are tx'd. I was very cautious about this when building the scene and I kept reusing the same textures all over with just different aiColorCorrect nodes to get a different look out of it in order to minimize the amount of texture files I need to actually load.

Im also aware of some meshes are throwing UV error in the log, but issue happens even if I delete them from scene.

If I understand correctly, for Arnold GPU to launch rendering, it needs to load all the textures into the GPU VRAM and since my rendering actually starts, I would say it is not the VRAM then..? Besides of that, the log says GPU had 312MB free when crash occured.. which is not a lot, but its not 0 either.


If anyone would be able to help with the problem it would be really appreciated.

Tags (2)
Labels (2)
3 REPLIES 3
Message 2 of 4
Stephen.Blair
in reply to: Mahagar

312MB isn't a lot. When I had a GPU with just 4GB, I could hardly render anything.

If you can do a CPU render, we can check how much memory is used for geometry, subdiv, and displacement.

Or, enable Ignore Textures and do a GPU render, to see how much GPU memory is used just for that.



// Stephen Blair
// Arnold Renderer Support
Message 3 of 4
Mahagar
in reply to: Mahagar

Thank you for your answer.

If I enable Ignore Textures and do GPU render, it renders all right. I just fail to see where I can find the actual memory conspumption (I have Debug selected in Render Settings and look at console). in Render Settings - System - Manual Device Selection it says 4292 MB free, but what I noticed is that everytime I open the scene, the number differs a lot so I dont know how reliable this information is. For example, I now uncheck Ignore Textures and it gives me an error

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

GPU 0 had 5812MB free before rendering started and 342MB free when crash occurred

GPU errors are sometimes due to a GPU not having enough remaining free memory. To see if this is what happened here, try simplifying your scene or running on a GPU with more free RAM to see if it solves the crash. Otherwise, upgrading to the latest nvidia gpu driver and Arnold core (available from www.arnoldrenderer.com) might fix the crash //

I would roughly estimate that all my textures used in scene take up max few hundreds of MBs on HDD, so how come it would eat so much of VRAM in Maya... especially when yesterday the same scene did work...

Also what I noticed is even when I do a fresh boot of my computer and open nothing but Maya, it will show only around 6 GB of VRAM free out of 8192MB.. so roughly 2GB are gone right away and I dont know why

Message 4 of 4
shavale
in reply to: Mahagar

@Stephen Blair What could be the solution for the below error 

incorrectly defined UV coordinates, missing either uvlist or uvidxs:

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

Post to forums  

Autodesk Design & Make Report