Binary search, or perhaps rather the bisection method, is one of those algorithms taught at the IT university which one might think is limited only to IT, but then he quickly realizes that it makes life easier outside the computer world. It's especially helpful when your grandmother asks you to hang her window curtains.
Kind of a poor attempt of a joke from my side, but those who did this activity (hanging curtains with millions of rusty clothespins) will know what I'm talking about.
Found 474 posts.
Search results Show results as topic list.
Houdini Indie and Apprentice » Best practices for tweaking simulations?
- ajz3d
- 474 posts
- Offline
Solaris and Karma » XPU stopped working after Houdini upgrade (605 to 653).
- ajz3d
- 474 posts
- Offline
Mirko, it seems to me that Fedora uses different paths to store NVIDIA libraries than Debian does. But it's the same path problem, where
You can ping the support using my bug report #151421. Because manually creating a symlink or copying a file is just an improvised solution, which may hit you back on the nearest system or nvidia-driver upgrade. Unless you remember to remove the symlink/file before initiating the process.
libnvidia-ml.so
isn't in the same place as libcuda.so
.You can ping the support using my bug report #151421. Because manually creating a symlink or copying a file is just an improvised solution, which may hit you back on the nearest system or nvidia-driver upgrade. Unless you remember to remove the symlink/file before initiating the process.
Edited by ajz3d - April 30, 2024 20:18:51
Houdini Lounge » Instamat did it
- ajz3d
- 474 posts
- Offline
Just to add to my post, I'm disappointed and very sad that MaterialMaker, TextureLab, FilterJS, Symbinode, Imogen and probably other libre procedural texturing projects that I'm not even aware of, didn't get much traction, judging by their most recent commit dates. Procedural texturing is a huge gap in libre DCC software that needs to be filled up ASAP. Most, if not all, of those programs, made by extremely talented people, now appear to be abandoned. I guess the problem is funding, because it's most definitely not the lack of skill.
There's almost a similar thing with libre node-based raster editors, on which I've been waiting for ages now. I know of two currently under development. We have Gimel Studio with the last commit a year ago, so probably it's been abandoned, because one year in CG software is a huge gap. Fortunately, the development of Graphite continues (https://github.com/GraphiteEditor/Graphite) and I hope its authors will not run out of steam.
There's almost a similar thing with libre node-based raster editors, on which I've been waiting for ages now. I know of two currently under development. We have Gimel Studio with the last commit a year ago, so probably it's been abandoned, because one year in CG software is a huge gap. Fortunately, the development of Graphite continues (https://github.com/GraphiteEditor/Graphite) and I hope its authors will not run out of steam.
Edited by ajz3d - April 30, 2024 20:09:08
Houdini Lounge » Instamat did it
- ajz3d
- 474 posts
- Offline
Carlos_Rivadulla
Has anyone else envisioned a Houdini material authoring workflow that integrates SOP+VOP+COP like this?
I did. In my dreams and wishful thinking. Maybe with COP3 nodes we will get it. That is, if they ever MATerialize.
Anyway, that's the first time I hear of this software, but it looks promising. I guess it aims to be a replacement for Substance Designer, and thank God for that, because I want a divorce with Adobe. I have an aversion to megacorporations, so you have just made my day a very happy one, dear Carlos. Hopefully Abstract's next step will be some kind of InstaPainter program, just to mock Adobe.
I'd like to try this software out, but I am unable to determine whether they have already made it available to GNU/Linux users or not. On their website in one blog post from January they promised that GNU/Linux support will be introduced in 2024. Other than that post, there's nothing more than silence regarding this subject and I couldn't find any information about software requirements on their site. There's no way of finding this out, other than registering first in an attempt to download the program, which of course I won't do, unless I'm sure it will work on my workstation. They really should post some information about requirements for potential customers.
Technical Discussion » Controlling Attribute from Map
- ajz3d
- 474 posts
- Offline
This SOP uses point UVs. You can drop a UV Project SOP before Attribute From Map, set it to points instead of vertices, and then manipulate it into desired position, angle and scale.
Houdini Indie and Apprentice » How to pin the viewer info window?
- ajz3d
- 474 posts
- Offline
You can try using the Log Viewer pane. There's an (i) icon in the top left corner of this pane, with which you can connect to various logging sources in the program. However, those colored messages displayed in Houdini status bar will not show up (for example, those generated by
Note that the pane won't display past logs from sources it wasn't connected to when the log entry was created.
hou.ui.setStatusMessage
), unless the tool or script also redirects them to standard output.Note that the pane won't display past logs from sources it wasn't connected to when the log entry was created.
Edited by ajz3d - April 29, 2024 19:23:28
Technical Discussion » Point cloud: Where does this web-like pattern come from?
- ajz3d
- 474 posts
- Offline
Solaris and Karma » XPU region render blurry textures
- ajz3d
- 474 posts
- Offline
Solaris and Karma » XPU stopped working after Houdini upgrade (605 to 653).
- ajz3d
- 474 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.
/opt/hfs20.0/bin/karma -V 5 test.usd
Solaris and Karma » XPU stopped working after Houdini upgrade (605 to 653).
- ajz3d
- 474 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
- 474 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
- 474 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
- 474 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 - April 17, 2024 07:38:13
Solaris and Karma » XPU stopped working after Houdini upgrade (605 to 653).
- ajz3d
- 474 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 - April 16, 2024 14:46:26
Solaris and Karma » XPU stopped working after Houdini upgrade (605 to 653).
- ajz3d
- 474 posts
- Offline
Solaris and Karma » XPU stopped working after Houdini upgrade (605 to 653).
- ajz3d
- 474 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
- 474 posts
- Offline
Houdini Lounge » HOUDINI 20 INSTABILITY
- ajz3d
- 474 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
- 474 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
- 474 posts
- Offline
-
- Quick Links