Hello,
I’m using Vray4 houdini with a lot of fun in windows.
Now i’m switching to linux ubuntu and i’m trying to make vray work with houdini
I’ve houdini 18.0.348 on the last ubuntu 19
I’ve download the last nightly build for vray . The installer one for linux.
The install is fine.
the i create a Json to put on packages folder with this inside
Installer already creates the json file (just make sure “Houdini packages” parameter is pointing to the “packages” subdirectory not Houdini install root!), you don’t need to create any other files yourself. This may be the reason of the crash.
Second reason may be build version mismatch. It’s never guaranteed that it’ll work with any build. It may work, but if there were some API changes it may crash and it means we need to create VFH builds specifically for that Houdini build (that doesn’t include daily builds, only production).
I’ve find your json file. I’ve replaced the mine by your. but it’s crash again.
I’m using the last production build houdini 18.0.348 . Maybe i need to wait you do the nightly for this production houdini build ?
> I’ve find your json file. I’ve replaced the mine by your. but it’s crash again.
Replaced like removed and moved the settings to your file?
You can’t have multiple packages loading the same stuff.
That’s why I recommend just to leave the installer file.
Could you start Houdini from console that check for errors / some crash info?
i’ve create a package folder in /home/ghiom/houdini18.0/packages and this is where i put my json file and i copy you json here.
Your json file is in /opt/hsf18.0.287 , but my houdini release is not 287 but 348.
This make your json file in this folder not readed, that why i’ve copy it in my own folder for easy use.
when i’m starting houdini with terminal ( it’s what you name console ? )
ghiom@ghiomwork:/opt/hfs18.0/bin$ ./hindie
ghiom@ghiomwork:/opt/hfs18.0/bin$ cat: /sys/devices/virtual/dmi/id/board_{vendor,name,version}: Aucun fichier ou dossier de ce type
No LSB modules are available.
sh: 1: ethtool: not found
sh: 1: ethtool: not found
sh: 1: ethtool: not found
[2020/Jan/17|09:46:19] VFH | Info| * Build number:5609 hash:87bfc3a from 16 Jan 2020 03:02
sh: 1: xterm: not found
and after houdini is on my screen, i can render with redshift, but not vray. it’s close houdini when it’s try to render.
> Your json file is in /opt/hsf18.0.287 , but my houdini release is not 287 but 348.
That’s why I’ve written in the previous message : “just make sure “Houdini packages” parameter is pointing to the “packages” subdirectory not Houdini install root!”
Installer has “Houdini packages” parameter, by default it’ll point to the default install location of houdini with the version of the build used to make that build.
So, you just need to point it to your installation, not the default directory.
So, what will be written in the console after you hit render?
Could u pls also run “./hindie -foreground” (this will not detach houdini process from the console).
I’m pretty sure there are some library dependencies missing or library mismatch.
ghiom@ghiomwork:/opt/hfs18.0/bin$ ./houdini -foreground
cat: /sys/devices/virtual/dmi/id/board_{vendor,name,version}: Aucun fichier ou dossier de ce type
No LSB modules are available.
sh: 1: ethtool: not found
sh: 1: ethtool: not found
sh: 1: ethtool: not found
[2020/Jan/17|14:29:33] VFH | Info| * Build number:5609 hash:87bfc3a from 16 Jan 2020 03:02
[2020/Jan/17|14:31:58] VFH | Info| * V-Ray 4.30.01
21219: Fatal error: Segmentation fault (sent by pid -24)
Saving application data to /tmp/houdini_temp/crash.untitled.ghiom_21219.hiplc
Crash log saved to /tmp/houdini_temp/crash.untitled.ghiom_21219_log.txt
and the log.txt :
Crash report from ghiom; Houdini FX Version 18.0.348 [linux-x86_64-gcc6.3]
Uptime 156 seconds
Fri Jan 17 14:32:09 2020
Caught signal 11
@bdancer Hi, just to say it’s work with the today nightly build. Just one thing, i’ve downloaded the install one, but when it was unarchived, it’s just a bin file. So, i’ve download the other one , create my folder and Json file like i want and everything is ok..
Nice job, thanks you
Just FYI, this is basically the same as the .exe under Windows. You can execute it from a terminal - you may need to first give it execution permissions with “chmod +x path/to/file”.
