(Open) [HOU-4616] Opacity Maps are culling geometries when using GPU or RTX

[leo_bao]

scene setup like this: I have copied bunch no thickness planes in front of a thickness geometry, but they were no interactive.

When I use GPU engine render, Or RTX engine render, I got this result:



planes are culling geometry that below them. No intersection with each other:



When I switch to CPU engine, Everything is fine:



And CPU mode does not work like GPU mode when using "setprimintrinsic" VEX function, base on result, GPU mode works as expected, And CPU mode looks like have some bugs. (Animation of leaves would delay lots of time), But when I open another houdini and load those files I saved in disk before, It works fine.. Strange behavior.
CPU mode would showing this warning, and GPU mode would not:

[viktor_angelov]

Hi leo_bao Thank you for sharing this with us! Could you please confirm if this happen only in this scene with this geometry or there are other scenarios as well?

What're the versions of Houdini ( Help > About Houdini ) and V-Ray ( V-Ray > About V-Ray ) that you are using?

What are your GPU drivers?

Do you get the same results with CUDA and RTX?

Is it correct to understand that there is a material applied on the geometry? If you remove it, will the issue disappear?

[leo_bao]

Hi leo_bao Thank you for sharing this with us! Could you please confirm if this happen only in this scene with this geometry or there are other scenarios as well?

What're the versions of Houdini ( Help > About Houdini ) and V-Ray ( V-Ray > About V-Ray ) that you are using?

What are your GPU drivers?

Do you get the same results with CUDA and RTX?

Is it correct to understand that there is a material applied on the geometry? If you remove it, will the issue disappear?

viktor_angelov
Could you please confirm if this happen only in this scene with this geometry or there are other scenarios as well?
Other scene also happened. When they did not cross each other, Geometry generated by this node "quixel_atlas_splitter" would cause culling (GPU mode, Both CUDA and RTX):




CPU is fine:


When they crossed each other(no "quixel_atlas_splitter" node), GPU mode(Both CUDA and RTX) would cause culling:



CPU mode would not:


What're the versions of Houdini ( Help > About Houdini ) and V-Ray ( V-Ray > About V-Ray ) that you are using?
20.5.445, 6.20.25[c690129c][c33e65e]

What are your GPU drivers?
566.36 Both Game Ready and Studio Driver - WHQL have been tested
566.14 Studio Driver - WHQL has been tested

Do you get the same results with CUDA and RTX?
Same

Is it correct to understand that there is a material applied on the geometry? If you remove it, will the issue disappear?
There is only a default vray material with an opacity texture applied on the geometry. I can't remove it, I have to connect an opacity texture to get it work.

[leo_bao]

And vray GPU for 3ds Max 2025 doesn't have this problem though

[viktor_angelov]

Hi leo_bao We are currently investigating the matter, however, it would be useful if you could share the scene with us so we can look into it.

Please, use V-Ray > Pack Scene

[leo_bao]

Hi leo_bao We are currently investigating the matter, however, it would be useful if you could share the scene with us so we can look into it.

Please, use V-Ray > Pack Scene

VRAY_RFE.rar viktor_angelov Here you go. If you need "quixel_atlas_splitter" node for debugging, please download it from here https://quixel.com/plugins/

[leo_bao]

viktor_angelov I have tested latest build: 6.20.25 0acf306_22839. But BUG still remains.

[viktor_angelov]

Hi leo_bao We managed to reproduce the issue. I have discussed it with the team and will log it into our system for future resolution. I will reach out if I have more information on the matter.

Thank you for taking the time to share this with us!

[viktor_angelov]

Hello leo_bao We have logged it into our system [HOU-4616] and will be looking into it.

[leo_bao]

Hello leo_bao We have logged it into our system [HOU-4616] and will be looking into it.

Hi viktor_angelov i am looking forward to it, hope next stable build could fix it.