VRay Optix Error with GPU rendering of one specific texture/object

[katarzyna_kobyliska1]

Hi
I'm having an issue with GPU rendering of one specific material (or rather texture file).
First vray was stuck on building light cache. After I figured out what was causing the issue, I created a new material, added the same texture (it's a jpg file), no reflection or anything, just to test.
Now I'm getting vray optix error: [VUtils::VOptix::OptixPipelineWrapper::launchForOOC] 7900: OptiX error encountered in vray_optix7.cpp[333]. Error Code 7900

Any other material, its fine. CPU rendering is ok, but obviously slower. I tested it in empty file - it renders fine.
How is ti possible?

Halfway through writing this, I realized I accountered the same problem with the same object (it's a simple rectangular painting) before - it is reused in this new file.
I fixed it there by deleting the entire thing and making a new model. This time this doesn't fix the problem. I imported the fixed model form the older project and it worked for w while, but it's again back to being stuck on building light cache.
If I hide the object or delete material, render works fine.


I'm working with NVIDIA RTX A4000, Window 11, driver ver. 511.65.


Edit: Ok, now nothing is working.
Memory, CPU and GPU usage is minimal while this all happens.

[Muhammed_Hamed]

Hi katarzyna_kobyliska and welcome to the forums,

Please update your drivers to 512.59, you can find the latest recommended driver in the GPU page near the top
7900 error is usually related to running out of GPU memory, but here it might be related to something else
Could you please upload the problematic geometry and texture for us, or a simplified version of your file. We need to be able to reproduce this on our side
On another note, bad geometry can crash GPU rendering(not CPU) if it has some Ngons or overlapping faces. This is normal to happen, we will be able to tell you why it crashes

Have a great day!

Best,
Muhammed

[katarzyna_kobyliska1]

Hi! Thank for your reply.
The model is not mine so I can't exactly send it to you. I'm just visualizing it for the client. It reuses same elements from the previous project that I remember having problems, too.
I updated drivers, but it didn't change anything. It's something within the model itself. Right now I'm experiencing endless light cache building on another scene completely.
First the scene works fine. It's only after I change something - material reflectivity, bump, etc - that its suddenly generates problems.But it's not consistent.
Eg. Just now I opened the file, tested with material override. Worked fine. Tested without it - worked fine. Changed the orientation of one texture - and I am back to being stuck on light cache building.


If the render works fine with material override, does it mean it IS a material issue? Or can it be a geometry issue as well?

Checking system usage while light cache is building: GPU memory (16GB) at 50%, CPU not used (i9 11th Gen), co-memory (32GB) not used. Basically, the only thing changing is GPU memory jumping form ~40% to ~50%. And that's it.

PS. I can't quit the vray render while this happens. Is there a way to do it without killing the Sketchup process in Task Manager??
Thanks,
Kate

Edit: I attached the texture file that's the cause. I can't render, when the object with the material using this file (generic material with this bitmap in diffuse), is in frame.
But I tried it with new file and it was rendering ok.

[Muhammed_Hamed]

If the render works fine with material override, does it mean it IS a material issue? Or can it be a geometry issue as well?

It could be a geometry issue still, depending on topology GPU rendering might have a hard time with it. If it has Ngons with many edges for example

PS. I can't quit the vray render while this happens. Is there a way to do it without killing the Sketchup process in Task Manager??

No, we will try to improve this in future

I attached the texture file that's the cause. I can't render

We need a version of the file that crashes, to be able to reproduce on our side. This texture works just fine
One tip is to check your geometry, make sure there is no overlapping faces or floating points. It is also expected that CPU doesn't crash on the same model, it uses different algorithms for rendering

Best,
Muhammed