Karma XPU in Vulkan viewport less responsive than opengl

   1788   18   4
User Avatar
Member
94 posts
Joined:
Offline
Does anyone notice thats karma XPU with Vulkan viewport its less responsive than karma XPU with opengl viewport?

in heavy scenes you can easly notice that.


***my OS its windows 11
Edited by habernir - 2024年8月22日 01:59:44
User Avatar
Member
163 posts
Joined: 1月 2015
Offline
Yes. Switched back to OpenGL for now.

If you want to switch back, it can be done in prefrences and with a environment variable.
User Avatar
スタッフ
513 posts
Joined: 5月 2019
Offline
Others have found this too
https://www.sidefx.com/forum/topic/92993/ [www.sidefx.com]
https://www.sidefx.com/forum/topic/92993/#post-428314 [www.sidefx.com]

Its been bug-reported and internal investigations are underway
User Avatar
Member
94 posts
Joined:
Offline
brians
Others have found this too
https://www.sidefx.com/forum/topic/92993/ [www.sidefx.com]
https://www.sidefx.com/forum/topic/92993/#post-428314 [www.sidefx.com]

Its been bug-reported and internal investigations are underway
Ok thanks for this info

Soo we need to wait to the next stable point release.
User Avatar
スタッフ
513 posts
Joined: 5月 2019
Offline
habernir
Soo we need to wait to the next stable point release.

If its an NVidia issue it could take a while. We'll keep you up to date on this ticket as things progress
User Avatar
Member
47 posts
Joined: 9月 2018
Offline
To me Vulkan viewport it's not only less responsive while Karma XPU is rendering but it hangs the whole programs for several seconds from time to time, totally unusable, switching to OGL fixed the issue, I was surprise.

This is happening even with the latest Studio Nvidia Drivers on Linux
Edited by terry_williams - 2024年8月23日 09:06:28
User Avatar
Member
102 posts
Joined: 4月 2017
Offline
I also switched back to OpenGL

You can try the heavy scene in (Caldera data set from Call of Duty®: Warzone™) from Activision:
https://github.com/Activision/caldera [github.com]

Try to grab the USD file e.g. from:
/caldera/map_source/prefabs/br/wz_vg/mp_wz_island/map_airfield/building_set_a.usd

And see how it perform.
User Avatar
Member
162 posts
Joined: 11月 2016
Offline
The responsiveness is even less if you have a multi view, I submitted an RFE about this few weeks ago, you might want to add more info to that ticket:

SideFX Support Ticket: #155456
Bug#139821

Cheers!
User Avatar
Member
378 posts
Joined: 4月 2018
Online
cdordelly
The responsiveness is even less if you have a multi view
Yes, if you're rendering with XPU, do not switch to a multi view. It will basically make Houdini unusable. It won't crash it, but it will make it so slow that it might as well have crashed. I've also submitted the bug report on this, hopefully a fix will come soon.
User Avatar
スタッフ
513 posts
Joined: 5月 2019
Offline
eikonoklastes
Yes, if you're rendering with XPU, do not switch to a multi view. It will basically make Houdini unusable. It won't crash it, but it will make it so slow that it might as well have crashed.

Does this bug still happen if using OpenGL? (instead of Vulkan)

Just wondering if this is related to the OpenGL vs Vulkan thing

thanks!
User Avatar
Member
31 posts
Joined: 10月 2022
Offline
yeah, it seems that the bug is resolved.
With OpenGL, everything works smoothly, but only one viewport displays materials correctly.
In the second viewport, the materials turn black.
User Avatar
スタッフ
513 posts
Joined: 5月 2019
Offline
Antti1999
yeah, it seems that the bug is resolved.

Which bug do you mean?
AFAIK there are two bugs mentioned in this forum chain

1) karma XPU with Vulkan viewport its less responsive than karma XPU with opengl viewport?
2) if you're rendering with XPU, do not switch to a multi view. It will basically make Houdini unusable.

and I don't think either are fixed yet

Antti1999
With OpenGL, everything works smoothly, but only one viewport displays materials correctly.
In the second viewport, the materials turn black.

Ahhh ok. So OpenGL doesn't work with multiple displays anyway, so we can't really test

thanks
User Avatar
Member
31 posts
Joined: 10月 2022
Offline
So, the OpenGL multi view isn’t lagging and crashing anymore that’s what I meant.

Previously, when you split the viewport into two, (I don’t mean two displays, just creating two scene views) using one for XPU and the other for scene manipulations, there were frequent random crashes. Now, I haven’t been able to make it crash at all.

As for materials randomly turning black (Labs - reset viewport triggers this too), I’ve found a temporary solution. I create a second material, 'usd_preview_material,' and set its Purpose to 'Preview Render' when assigning it to the object.
Edited by Antti1999 - 2024年8月28日 06:33:16
User Avatar
Member
548 posts
Joined: 8月 2014
Offline
terry_williams
To me Vulkan viewport it's not only less responsive while Karma XPU is rendering but it hangs the whole programs for several seconds from time to time, totally unusable, switching to OGL fixed the issue, I was surprise.

This is happening even with the latest Studio Nvidia Drivers on Linux
Terry, can you open dmesgand see if these hangups are caused by CTX SWITCHtimeouts?

[Aug24 12:55] NVRM: Xid (PCI:0000:01:00): 109, pid='<unknown>', name=<unknown>, Ch 00000039, errorString CTX SWITCH TIMEOUT, Info 0x4c019

More in this thread [www.sidefx.com].
User Avatar
Member
182 posts
Joined: 2月 2017
Offline
Antti1999
So, the OpenGL multi view isn’t lagging and crashing anymore that’s what I meant.

Previously, when you split the viewport into two, (I don’t mean two displays, just creating two scene views) using one for XPU and the other for scene manipulations, there were frequent random crashes. Now, I haven’t been able to make it crash at all.

As for materials randomly turning black (Labs - reset viewport triggers this too), I’ve found a temporary solution. I create a second material, 'usd_preview_material,' and set its Purpose to 'Preview Render' when assigning it to the object.

The material issue has not been fixed since H20.
User Avatar
Member
378 posts
Joined: 4月 2018
Online
brians
eikonoklastes
Yes, if you're rendering with XPU, do not switch to a multi view. It will basically make Houdini unusable. It won't crash it, but it will make it so slow that it might as well have crashed.

Does this bug still happen if using OpenGL? (instead of Vulkan)

Just wondering if this is related to the OpenGL vs Vulkan thing

thanks!
Sorry, I only just got a chance to test this. Here is what I see:

- With the OpenGL viewport enabled:
- when rendering with either Karma CPU or XPU:
- Houdini is very responsive in the multi view.

With the Vulkan viewport enabled:
- when rendering with Karma CPU:
- Houdini is responsive in multi view, but a lot slower than with OpenGL. There is a noticeable lag when trying to interact with viewport handles, and everything feels a bit slower and laggier than with OpenGL.

- when rendering with Karma XPU:
- Houdini is basically unusable in multi view. It freezes immediately and takes several seconds to respond to any action, and then continues to remain in that state until I disable the renderer or kill Houdini.

Here are some specs:
- Houdini 20.5.332 - Py3.11
- Pop! OS 22.04 LTS
- 128 GB RAM
- AMD Ryzen 9 5950x
- Nvidia RTX 3090 Ti
User Avatar
Member
47 posts
Joined: 9月 2018
Offline
Hi, I uploaded a video showcasing this issue, Vulkan vs Opengl while the rendering is going, this is only happening with XPU and I also noticed the snappiness of the renderer is way better in OpenGL.


PD: There are timestamps in the description.


@ajz3d - I ran the command in Sudo but I couldn't find in the log anything related to "SWITCH TIMEOUT" the only line related to NVRM said: " NVRM: loading NVIDIA UNIX x86_64 Kernel Module 555.58.02 Tue Jun 25 01:39:15 UTC 2024"
Edited by terry_williams - 2024年8月29日 13:03:01
User Avatar
Member
548 posts
Joined: 8月 2014
Offline
I switched back to OpenGL two weeks ago and the program feels much more responsive. Random crashes are also much, much less frequent than what I had been experiencing with Vulkan viewport. I'm currently working primarily in Copernicus, so with OpenGL viewport I'm missing some COP features that are available in Vulkan (like "Tile Vis: 3", for instance), but even that is better than having to restart Houdini dozens of time a day. I hope that Vulkan stability and performance will be progressively improved within future 20.5.x minor versions, so we don't have to wait until 21.0. After all, it was decided to make Vulkan Houdini's default viewport renderer, and while I don't expect it to be faster than OpenGL (as it's probably more complex), I think it should at least offer stability similar to OpenGL.

terry_williams
@ajz3d - I ran the command in Sudo but I couldn't find in the log anything related to "SWITCH TIMEOUT" the only line related to NVRM said: " NVRM: loading NVIDIA UNIX x86_64 Kernel Module 555.58.02 Tue Jun 25 01:39:15 UTC 2024"
Thanks for checking, Terry.
User Avatar
Member
31 posts
Joined: 10月 2022
Offline
  • Quick Links