/opt/hfs20.0/bin/karma -V 5 test.usd
Found 466 posts.
Search results Show results as topic list.
Solaris and Karma » XPU stopped working after Houdini upgrade (605 to 653).
- ajz3d
- 466 posts
- Offline
Mirko, have you tried running an offline render with verbosity of 5 or higher, like Brians suggested in one of his posts? It should provide you with more detailed information than what you normally get from the Log Viewer.
Solaris and Karma » XPU stopped working after Houdini upgrade (605 to 653).
- ajz3d
- 466 posts
- Offline
briansHi Brians,
I've made this change to 20.0.685
When you get a chance, can you please test and let me know either way.
I removed manually created
/usr/lib/x86_64-linux-gnu/libnvidia-ml.so
symlink, restarted Debian (just in case), installed 20.0.685, and ran some XPU test renders from both: the GUI and the offline renderer. The problem seems to be fixed as there were no errors. OptiX kicked in and I had 99% load on the GPU.I'm still on nvidia-driver 550.54.15-1.
Solaris and Karma » XPU stopped working after Houdini upgrade (605 to 653).
- ajz3d
- 466 posts
- Offline
Great. Let me know once you implement the changes, so I can test them. Of course, I'll remove the manually created symlink beforehand. :P
Solaris and Karma » XPU stopped working after Houdini upgrade (605 to 653).
- ajz3d
- 466 posts
- Offline
Hard to say. I can only speculate, but I would definitely exclude the distro from the blame list, because the only thing I did before Optix stopped working in XPU is to upgrade Houdini from 20.0.605 to 20.0.653. No apt upgrades, no new nvidia-driver installations or anything like that. And, rolling back to Houdini 20.0.605 makes the Optix work again in XPU. Besides, I'm not using nvidia-driver from Debian's repositories, but the one from the upstream repo which Debian team has no control of.
I'd say it's most likely Houdini or NVIDIA. Brians said that they're loading a new driver binary now. I assume he had this
I'd say it's most likely Houdini or NVIDIA. Brians said that they're loading a new driver binary now. I assume he had this
libnvidia-ml.so
in mind. So maybe they're loading from the wrong path? It might also be that Houdini uses the correct path to dynamically link this library, but NVIDIA misconfigured their .deb packages and that's why the symlink to libnvidia-ml.so
wasn't created in /usr/lib/x86_64-linux-gnu
path when the nvidia-driver package was installed. Who knows? :/
Solaris and Karma » XPU stopped working after Houdini upgrade (605 to 653).
- ajz3d
- 466 posts
- Offline
/usr/lib/x86_64-linux-gnu/nvidia/current/
contains libcuda.so
as well as libnvidia-ml.so*
set of files.However,
/usr/lib/x86_64-linux-gnu/
contains libcuda.so
, but only libnvidia-ml.so.1
. I believe Houdini is checking this particular path, because after I created libnvidia-ml.so
as a symlink to /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1
, OptiX started working again.So yes, it's a problem with paths.
Edited by ajz3d - 2024年4月17日 07:38:13
Solaris and Karma » XPU stopped working after Houdini upgrade (605 to 653).
- ajz3d
- 466 posts
- Offline
Bingo.
But why does it complain that this library cannot be found? I have it inside
[20:16:57] KarmaXPU: Failed to load CUDA DSO [libnvidia-ml.so: cannot open shared object file: No such file or directory]
But why does it complain that this library cannot be found? I have it inside
/usr/lib/x86_64-linux-gnu/nvidia/current/
path. It's a symlink to libnvidia-ml.so.1
, which in turn is a symlink to libnvidia-ml.so.550.54.15
.
Edited by ajz3d - 2024年4月16日 14:46:26
Solaris and Karma » XPU stopped working after Houdini upgrade (605 to 653).
- ajz3d
- 466 posts
- Offline
Solaris and Karma » XPU stopped working after Houdini upgrade (605 to 653).
- ajz3d
- 466 posts
- Offline
Can you tell me which version of NVIDIA driver you are using? It was suggested to me by the support that I should upgrade to 550.67, though this version isn't available in upstream repository yet, so I cannot test this solution out.
Perhaps something was changed in XPU architecture between 605 and 653, and it now requires some functions that exist in newer GPU driver?
Perhaps something was changed in XPU architecture between 605 and 653, and it now requires some functions that exist in newer GPU driver?
Solaris and Karma » XPU stopped working after Houdini upgrade (605 to 653).
- ajz3d
- 466 posts
- Offline
Houdini Lounge » HOUDINI 20 INSTABILITY
- ajz3d
- 466 posts
- Offline
I can confirm this is indeed happening.
After this exception occurs, Houdini will repetitively keep on throwing another exception which it displays inside a Python Callback Error window. This happens on some actions.
Traceback (most recent call last):
File "/opt/hfs20.0.605/houdini/python3.10libs/viewerhandle/hudslider.py", line 957, in onKeyFrameEvent1
self.handleKeyFrameEvent(hudc.HANDLE_PARM1, event, kwargs)
File "/opt/hfs20.0.605/houdini/python3.10libs/viewerhandle/hudslider.py", line 976, in handleKeyFrameEvent
info[KEYFRAME].updateWidgetColor(kwargs["frame"], style_sheet=HUDSlider.BG_STYLE_SHEET)
File "/opt/hfs20.0.605/houdini/python3.10libs/viewerhandle/hudwidgets.py", line 378, in updateWidgetColor
self._background_color = self._updateBackgroundColor()
File "/opt/hfs20.0.605/houdini/python3.10libs/viewerhandle/hudwidgets.py", line 415, in _updateBackgroundColor
hcolor = self._target_parm.uiBackgroundColor()
File "/opt/hfs20.0.605/houdini/python3.10libs/hou.py", line 71279, in uiBackgroundColor
return _hou.Parm_uiBackgroundColor(self)
hou.ObjectWasDeleted: Attempt to access an object that no longer exists in Houdini.
Traceback (most recent call last):
File "/opt/hfs20.0.605/houdini/python3.10libs/hdefereval.py", line 155, in _processDeferred
result = code(*args, **kwargs)
File "/opt/hfs20.0.605/houdini/python3.10libs/viewerhandle/hudmanager.py", line 946, in onDeferInitWindow
self._displayWindow(win)
File "/opt/hfs20.0.605/houdini/python3.10libs/viewerhandle/hudmanager.py", line 982, in _displayWindow
win.updateActions()
File "/opt/hfs20.0.605/houdini/python3.10libs/viewerhandle/hudwindow.py", line 2163, in updateActions
if not hud_widget.hasKeyFrame(hou.frame()):
File "/opt/hfs20.0.605/houdini/python3.10libs/viewerhandle/hudslider.py", line 706, in hasKeyFrame
if info[KEYFRAME].hasKeyFrame(frame):
File "/opt/hfs20.0.605/houdini/python3.10libs/viewerhandle/hudwidgets.py", line 347, in hasKeyFrame
key_frames = self._target_parm.keyframes()
File "/opt/hfs20.0.605/houdini/python3.10libs/hou.py", line 69975, in keyframes
return _hou.Parm_keyframes(self)
hou.ObjectWasDeleted: Attempt to access an object that no longer exists in Houdini.
After this exception occurs, Houdini will repetitively keep on throwing another exception which it displays inside a Python Callback Error window. This happens on some actions.
Traceback (most recent call last):
File "/opt/hfs20.0.605/houdini/python3.10libs/viewerhandle/hudwidgets.py", line 451, in _onPlaybarEvent
if not self._target_parm or not len(self._target_parm.keyframes()):
File "/opt/hfs20.0.605/houdini/python3.10libs/hou.py", line 69975, in keyframes
return _hou.Parm_keyframes(self)
hou.ObjectWasDeleted: Attempt to access an object that no longer exists in Houdini.
Solaris and Karma » XPU stopped working after Houdini upgrade (605 to 653).
- ajz3d
- 466 posts
- Offline
It seems that after upgrading from 20.0.605 to 20.0.653 (production build) I have lost the ability to render with Karma XPU. There are no errors printed to stdout, but Log Viewer contains several errors and warnings (logs are in the attachment). HUD in the upper right corner of the viewport doesn't even mention OptiX. Same thing happens with the newest daily build (20.0.675).
I had to roll back to 20.0.605 where XPU still works.
My specs: Debian 12.5 (Bookworm), nvidia-driver/libnvoptix1 550.54.15-1 (upstream), RTX 3070.
Has anyone else experienced this problem?
I had to roll back to 20.0.605 where XPU still works.
My specs: Debian 12.5 (Bookworm), nvidia-driver/libnvoptix1 550.54.15-1 (upstream), RTX 3070.
Has anyone else experienced this problem?
Solaris and Karma » XPU and Ryzen's integrated GPU
- ajz3d
- 466 posts
- Offline
Solaris and Karma » XPU and Ryzen's integrated GPU
- ajz3d
- 466 posts
- Offline
I'm planning to purchase a laptop with an RTX 3050 and Ryzen CPU (6600H) which comes with an integrated GPU reportedly capable of some basic raytracing operations (Radeon 660M). Will the raytracing capability of the integrated GPU chip be utilized by Karma XPU at its current development state?
Houdini Learning Materials » Tips: how to setup Houdini's docs for comfortable reading.
- ajz3d
- 466 posts
- Offline
Oh, yes. For every dark theme lovers out there, Dark Reader is a must-have. There are very few things worse in mundane life than having one's eyes suddenly burned to charcoal by a sudden blast of whiteness, just because someone decided to set the background of a webpage to #FFF. For Houdini Docs, I keep the extension set to Dark/Dynamic.
Thanks for pointing out
Thanks for pointing out
$HFS/houdini/python3.10libs/houdinihelp/hstatic/scss/hpage.css
. About a year ago I started working on custom Stylus CSS for the online and local docs, inspecting and guessing selectors, in order to create a dark page stylesheet override which would work faster than Dark Reader's Dynamic mode, but it didn't occur to me to simply look for a CSS file inside $HFS
. This will make it much easier.
Technical Discussion » [SOLVED] How to change UV Edit pivot?
- ajz3d
- 466 posts
- Offline
Technical Discussion » [SOLVED] How to change UV Edit pivot?
- ajz3d
- 466 posts
- Offline
For the time being, my workaround is to edit UVs in world space as
I'll send an RFE regarding this issue.
P
and move P
data to uv
afterward. Somewhat ridiculous, but at least I can manipulate the pivot of each selected UV island.Edited by ajz3d - 2024年2月25日 16:29:13
Technical Discussion » [SOLVED] How to change UV Edit pivot?
- ajz3d
- 466 posts
- Offline
Has anybody found a way to change pivot location in the UV Edit SOP? "Insert" key, doesn't work, orientation picking only translates the selection, and modification of px, py and pz parameter doesn't have any effect whatsoever.
Edited by ajz3d - 2024年2月25日 16:29:31
Technical Discussion » File rules: rule index '1' invalid. There are only '1' rules
- ajz3d
- 466 posts
- Offline
When I attempt to create a new rule in Houdini's OCIO Editor I get the following error message:
What does it mean?
PS. I'm using a copy of
File rules: rule index '1' invalid. There are only '1' rules.
What does it mean?
PS. I'm using a copy of
cg-config-v2.0.0_aces-v1.3_ocio-v2.1.ocio
(from GitHub) in my OCIO envar and I have rw
access to this file.
Solaris and Karma » [SOLVED] Karma XPU: some UVs are rotated 90 degrees
- ajz3d
- 466 posts
- Offline
Okay I found the culprit. It turned out that I had two identical pieces of geometry stacked on top of each other, each with different UVs.
It seems that XPU uses slightly different Z priority than CPU and OpenGL do. Good to know.
It seems that XPU uses slightly different Z priority than CPU and OpenGL do. Good to know.
Solaris and Karma » [SOLVED] Karma XPU: some UVs are rotated 90 degrees
- ajz3d
- 466 posts
- Offline
I'm puzzled because I'm seeing this for the first time. I was rendering an asset with XPU and I noticed that some parts have UVs rotated 90 degrees. These areas are rendered correctly on Karma CPU, as well as OpenGL.
There's nothing unusual about the asset. Just a mid-poly object with UVs and MaterialX with some textures. No fancy configuration.
I will continue debugging the scene, as it's possible that I made a mistake somewhere. But meanwhile, I thought I'd ask if perhaps someone already encountered a similar issue and knows what might be causing it.
There's nothing unusual about the asset. Just a mid-poly object with UVs and MaterialX with some textures. No fancy configuration.
I will continue debugging the scene, as it's possible that I made a mistake somewhere. But meanwhile, I thought I'd ask if perhaps someone already encountered a similar issue and knows what might be causing it.
Edited by ajz3d - 2024年2月11日 19:42:17
-
- Quick Links