Tralen

Greetings, I have a conventional null and bone hierarchy, using the default nodes provided by Houdini. I would like to replace them, however, with my own HDAs, that have the same exact internal structure, one for bones, another for nulls. The reason is that I want to add extra parameters and scripting to the nulls and bones, and it is easier to do it on HDAs. So far, I haven't seen any difference in performance, but I fear that it will drop, once the size of the hierarchy increases. Is that a valid concern? That a default node will outperform a HDA with identical internal structure, for the sole reason of this being a HDA? Thanks in advance.

Yes, I changed the board in the worst possible time. The updates that broke everything on Arch were all recent and I was out of pace with what was happening on the Ubuntu side. Still, I got an iso of Ubuntu 16.04.3 and managed to get Houdini running. I'm glad I didn't return the board because AMD is at least doing a lot of investment in open source, even if their release cycle lags so much. It took them two months to release the driver for 16.04.4 (released just now), so I don't expect the driver for 18.04 to come so soon. Thanks for the input and the sarcasm.

Thank you, Luke, this settles the situation then. It is ironic that I moved to Arch, some years ago, exactly because the proprietary drivers for my old card were dropped from Ubuntu and the rest, the only way to get Houdini running with it was to install the driver from the AUR. Well, for anyone trying to install the drivers on Arch, the situation is hopeless. The 4.9-kallsyms kernel builds properly, but mesa won't. It needs to link against a particular version of llvm, but is unable to build with it, so simply downgrading it won't help. To compound the problem, the last update to glibc breaks everything, and downgrading it requires downgrading gcc and gcc-libs which can pretty much break the whole system. The AUR maintainers of the driver and the patched mesa seem unresponsive, which can be expected since the community is satisfied with the open source driver performance (for games). I migrated the system to Ubuntu 18.04, and found the situation even worse. With the proprietary drivers, I'm not even able to login. I'm at a loss. Thanks for any assistance. Edit: It seems the proprietary driver only works with Ubuntu 16.04. I think I will return the board, get a nvidia and go back to Arch.

Well, for now, I'm still motivated enough to try. I would rather not change my home setup from Arch, which has been working for many years. Can you confirm that the closed source driver is necessary for Houdini? I'm trying to verify if I did something wrong when I uninstalled the old driver, I should at least be able to run Houdini with HOUDINI_OGL_CORE_PROFILE=1, with very poor quality. Thank you, Luke.

You are exactly right, I had copied the wrong file. Thank you, trandzik.

Greetings, I'm an old time Houdini user, but never posted here before. I'm currently facing issues on getting Houdini working at home, where I updated an old HD 6950 to a RX 560. I used the closed source fglrx driver and the setup worked perfectly, but now, I'm at a loss on how to deal with the new amdgpu driver. The closed source amdgpu-pro seems impossible to work, it requires a special kernel, which I was able to build, a special version of mesa, which again I managed to build, and manual editing of the PKGBUILD, because it refers to a version of the driver that is no longer available. Even after all the steps, I still can't get OpenGL to work, glxinfo fails to find anything at all. On the other hand, Houdini doesn't seem to work with the open source driver, so I ask if anyone is able to use Houdini with an AMD board on Arch, and if you can provide any assistance. Thank you.

Greetings, Adding the file to dsolib still required the use of LD_PRELOAD. Is there anything else I need to do?