Houdini and Fedora 26

Forums Technical Discussion Houdini and Fedora 26

10703 13 4


vakont: Member; 9 posts; Joined: 11月 2013; Offline

2017年7月16日 12:40

Hello everyone,

Does anyone have experience with Houdini 16 on Fedora?

I am simply trying to decide where I will settle the workstation to place the Indie version I'm headed for & CentOS had some issues with the OpenGL, thus delivering only 12-14fps on an RX480 8GB (which lost a benchmark to an old 580GTX in Unigine Heaven 4.0, if you believe it or not).

I have tried to install it, but get various errors and the UI doesn't fire up. If anyone has any idea, I could post up a few logs.

Thank you!

System:
Fedora 26
Intel Core i7 - 970 - 6 core @ 3.2GHz
24GB DDR3 RAM
Gigabyte OC AMD RX480 8GB DDR5
Decklink Monitor
3xSSD system


vakont: Member; 9 posts; Joined: 11月 2013; Offline

2017年7月22日 13:54

Ok, I actually had a bit of luck. After going through the CUDA/OpenCL and especially Java installation, I was able to load it up. However, every time I try to add a node or execute something from the shelf, I get the same response below:

Any ideas what more dependencies I may need?

Python 2 & 3 are installed. Perhaps needs extra libraries?

Thank you all!

Attachments:
Screenshot from 2017-07-22 20-53-46.png (732.9 KB)


Michael Rochefort: Member; 6 posts; Joined: 12月 2013; Offline

2017年7月22日 15:41

You shouldn't have to install any extra libraries, they should have been included in the Houdini install. DCC's package their own Python libraries/interpreters to my knowledge, as they often add custom modules.

It's been a while since I've played around with Houdini, but my first instinct would be to either reinstall or reset my config and see if things work (life lessons from Maya and Modo).


vakont: Member; 9 posts; Joined: 11月 2013; Offline

2017年7月23日 11:01

In general, the crashes vary, but when it produces a crash report, it's the following:

Unknown App Version 16.0.671 [linux-x86_64-gcc4.8]
Uptime 0 seconds
Sun Jul 23 17:57:34 2017
Caught signal 11

Traceback from 14578 ThreadId=0x7f6cf50e5d00
AP_Interface::coreDumpChaser(UTsignalHandlerArg) <libHoudiniUI.so>
AP_Interface::si_CrashHandler::chaser(UTsignalHandlerArg) <libHoudiniUI.so>
signalCallback(UTsignalHandlerArg) <libHoudiniUT.so>
UT_Signal::UT_ComboSignalHandler::operator()(int, siginfo*, void*) const <libHoudiniUT.so>
UT_Signal::processSignal(int, siginfo*, void*) <libHoudiniUT.so>
__funlockfile <libpthread.so.0>
PyList_SetSlice <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
Py_InitModule4_64 <libpython2.7.so.1.0>
PyImport_ImportModuleLevel <libpython2.7.so.1.0>
_Py_Mangle <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyEval_CallObjectWithKeywords <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
Py_InitModule4_64 <libpython2.7.so.1.0>
PyImport_ImportModuleLevel <libpython2.7.so.1.0>
_Py_Mangle <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyEval_CallObjectWithKeywords <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
Py_InitModule4_64 <libpython2.7.so.1.0>
PyImport_ImportModuleLevel <libpython2.7.so.1.0>
_Py_Mangle <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyEval_CallObjectWithKeywords <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
Py_InitModule4_64 <libpython2.7.so.1.0>
PyImport_ImportModuleLevel <libpython2.7.so.1.0>
_Py_Mangle <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyEval_CallObjectWithKeywords <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
Py_InitModule4_64 <libpython2.7.so.1.0>
PyImport_ImportModuleLevel <libpython2.7.so.1.0>
_Py_Mangle <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyEval_CallObjectWithKeywords <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
Py_InitModule4_64 <libpython2.7.so.1.0>
PyImport_ImportModuleLevel <libpython2.7.so.1.0>
_Py_Mangle <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyEval_CallObjectWithKeywords <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
_PyImport_LoadDynamicModule <libpython2.7.so.1.0>
Py_InitModule4_64 <libpython2.7.so.1.0>
PyImport_ImportModuleLevel <libpython2.7.so.1.0>
_Py_Mangle <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyEval_CallObjectWithKeywords <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
Py_InitModule4_64 <libpython2.7.so.1.0>
PyImport_ImportModuleLevel <libpython2.7.so.1.0>
_Py_Mangle <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyEval_CallObjectWithKeywords <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
Py_InitModule4_64 <libpython2.7.so.1.0>
PyImport_ImportModuleLevel <libpython2.7.so.1.0>
_Py_Mangle <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyEval_CallObjectWithKeywords <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PY_CompiledCode::evaluateUsingDicts(PY_Result::Type, void*, void*, PY_Result&) const <libHoudiniUT.so>
PY_CompiledCode::evaluate(PY_Result::Type, PY_Result&) const <libHoudiniUT.so>
PYrunPythonStatements(char const*, PY_EvaluationContext*) <libHoudiniUT.so>
PYrunPythonStatementsAndExpectNoErrors(char const*, char const*, PY_EvaluationContext*) <libHoudiniUT.so>
BR_HelpManager::initializeHelpServer() <libHoudiniUI.so>
BR_HelpManager::BR_HelpManager(bool) <libHoudiniUI.so>
FUSE_HelpManager::FUSE_HelpManager(FUSE_App&) <libHoudiniAPPS3.so>
FUSE_App::FUSE_App(char const*) <libHoudiniAPPS3.so>
FUSE_HoudiniBinariesApp::createApplication(int&, char const**) <libHoudiniAPPS3.so>
OPUI_MainApp::initApplication(UI_Manager*, int, char const**) <libHoudiniAPPS2.so>
main <libHoudiniUI.so>
__libc_start_main <libc.so.6>
_start <houdini-bin>


vakont: Member; 9 posts; Joined: 11月 2013; Offline

2017年7月24日 17:56

It's been a while since I've played around with Houdini, but my first instinct would be to either reinstall or reset my config and see if things work (life lessons from Maya and Modo).

Ah… the days of Maya. Now those have been a really long time ago and I do remember inventing the term “render-crash” back then. It seems they're still building on the old core of the application, adding stuff that it can barely handle correctly. I do remember creating really complex curves there and waiting on a 2-3sec lag for the application to follow my clicks. When I tried the same on Houdini, it stormed through it like I had some kind of super-computer.

In any case, I do agree on the deleting the config folders. I tried it and it worked for a bit. Until it couldn't save or exit later on. It would seem that -for some reason- it wasn't agreeing with my 381 version of the nVidia drivers (I changed system as AMD's drivers have no support for Wayland), even though all OpenCL & Cuda were available.

So, I had to eventually switch to OpenSUSE Tumbleweed. Kind of risky, but Houdini does work there. Though I may have to install a newer driver version than the Long Term Support one (375.66), since I'm experiencing Lattice deformation artifacts, even when the deformation applies.

Thank you for the recommendation! If only it could work longer term. :-)


Michael Rochefort: Member; 6 posts; Joined: 12月 2013; Offline

2017年7月24日 19:26

So, I had to eventually switch to OpenSUSE Tumbleweed. Kind of risky, but Houdini does work there. Though I may have to install a newer driver version than the Long Term Support one (375.66), since I'm experiencing Lattice deformation artifacts, even when the deformation applies.

That's interesting. I run 375.66 on CentOS 7 and pretty much all of my apps run fine. I'm surprised it's not working on Fedora, I've built up a habit whenever working with NVIDIA drivers where I enable FullCompositionPipeline and ForceFullCompositionPipeline in the X Server settings (You'll need sudo to write to Xorg). Other than that just set PowerMizer to Prefer Maximum Performance and on each login run `nvidia-settings -l` to load the config. You might need to activate coolbits though, simple enough.

Over in the Redshift forums it was discovered that 381.xx was unstable for us, so maybe there's some weird CUDA/OpenGL bug in that branch. I've only ever used the LTS drivers.

Another Redshift/Houdini user, Varomix, also recently upgraded from CentOS to F26 and his system is running perfectly fine.

Edited by Michael Rochefort - 2017年7月24日 19:28:12


vakont: Member; 9 posts; Joined: 11月 2013; Offline

2017年7月24日 21:21

Michael Rochefort
That's interesting. I run 375.66 on CentOS 7 and pretty much all of my apps run fine. I'm surprised it's not working on Fedora, I've built up a habit whenever working with NVIDIA drivers where I enable FullCompositionPipeline and ForceFullCompositionPipeline in the X Server settings (You'll need sudo to write to Xorg). Other than that just set PowerMizer to Prefer Maximum Performance and on each login run `nvidia-settings -l` to load the config. You might need to activate coolbits though, simple enough.

Over in the Redshift forums it was discovered that 381.xx was unstable for us, so maybe there's some weird CUDA/OpenGL bug in that branch. I've only ever used the LTS drivers.

Another Redshift/Houdini user, Varomix, also recently upgraded from CentOS to F26 and his system is running perfectly fine.

That was interesting indeed. And the moment I was able to finally get Cuda up and running. Houdini was the only one refusing to work. And it could be that I wasn't using the LTS drivers. However, nVidia just released their new LTS drivers, the 384.59, which I just installed on OpenSUSE. Only a day too late after my switching. Oh well. I do miss the “dnf” (I know it's funny), but this distro -I dare say- is actually faster and smoother on the graphics. I wasn't expecting it to be honest.

Cuda and OpenCL appear to be working correctly. However, they do have a web where you can install the Cuda toolkit, depending on the nVidia driver you're running, which is quite convenient. On other stuff, I'm slowly getting around to learning the edges, being mostly an Ubuntu Studio user (and spending a few weeks with CentOS & Fedora).

And it would seem my lattice issue is mainly because of the current Houdini build, as you can see in the attachment. It tends to grab and move un-selected points… but the initial effect with the lines popping out was… electrifying!

Thank you again for the tip on the nVidia! I learn something new every day (and when I thought Wayland negated Xorg). It could definitely come in handy, as OpenSUSE is “orbiting” the RPM family, so they are pretty close. :-)

Attachments:
Screenshot from 2017-07-25 04-03-01.png (538.4 KB)


aditiavfx: Member; 3 posts; Joined: 9月 2014; Offline

2017年8月1日 10:02

Hi all,

It seems I also cannot run Houdini on Fedora 26. I try both production build 671 and 633, and they are fails.

Below the crash logs.

Crash report from aditia; Unknown App Version 16.0.671 [linux-x86_64-gcc4.8]
Uptime 0 seconds
Tue Aug  1 20:57:56 2017
Caught signal 11

Traceback from 15232 ThreadId=0x7f61643d2d00
AP_Interface::coreDumpChaser(UTsignalHandlerArg) <libHoudiniUI.so>
AP_Interface::si_CrashHandler::chaser(UTsignalHandlerArg) <libHoudiniUI.so>
signalCallback(UTsignalHandlerArg) <libHoudiniUT.so>
UT_Signal::UT_ComboSignalHandler:perator()(int, siginfo*, void*) const <libHoudiniUT.so>
UT_Signal::processSignal(int, siginfo*, void*) <libHoudiniUT.so>
__funlockfile <libpthread.so.0>
je_arena_dalloc_bin_locked (arena.c:1897)
je_tcache_bin_flush_small (tcache.c:127)
je_tcache_event_hard (tcache.c:39)
PyList_Sort <libpython2.7.so.1.0>
PyTuple_Size <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyFloat_FromDouble <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyCode_New <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyWeakref_NewRef <libpython2.7.so.1.0>
PyType_IsSubtype <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyFloat_FromDouble <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyCode_New <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyAST_obj2mod <libpython2.7.so.1.0>
PyCode_NewEmpty <libpython2.7.so.1.0>
PyMapping_HasKeyString <libpython2.7.so.1.0>
PyNumber_Or <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
Py_InitModule4_64 <libpython2.7.so.1.0>
PyImport_ImportModuleLevel <libpython2.7.so.1.0>
_Py_Mangle <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyEval_CallObjectWithKeywords <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
Py_InitModule4_64 <libpython2.7.so.1.0>
PyImport_ImportModuleLevel <libpython2.7.so.1.0>
_Py_Mangle <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyEval_CallObjectWithKeywords <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
_PyImport_LoadDynamicModule <libpython2.7.so.1.0>
Py_InitModule4_64 <libpython2.7.so.1.0>
PyImport_ImportModuleLevel <libpython2.7.so.1.0>
_Py_Mangle <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyEval_CallObjectWithKeywords <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
Py_InitModule4_64 <libpython2.7.so.1.0>
PyImport_ImportModuleLevel <libpython2.7.so.1.0>
_Py_Mangle <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyEval_CallObjectWithKeywords <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
Py_InitModule4_64 <libpython2.7.so.1.0>
PyImport_ImportModuleLevel <libpython2.7.so.1.0>
_Py_Mangle <libpython2.7.so.1.0>
PyObject_Call <libpython2.7.so.1.0>
PyEval_CallObjectWithKeywords <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
PyImport_ExecCodeModuleEx <libpython2.7.so.1.0>
_PyImport_LoadDynamicModule <libpython2.7.so.1.0>
Py_InitModule4_64 <libpython2.7.so.1.0>
PyImport_ImportModuleLevel <libpython2.7.so.1.0>
_Py_Mangle <libpython2.7.so.1.0>
PyEval_EvalFrameEx <libpython2.7.so.1.0>
PyEval_EvalCodeEx <libpython2.7.so.1.0>
PyEval_EvalCode <libpython2.7.so.1.0>
PY_CompiledCode::evaluateUsingDicts(PY_Result::Type, void*, void*, PY_Result&) const <libHoudiniUT.so>
PY_CompiledCode::evaluate(PY_Result::Type, PY_Result&) const <libHoudiniUT.so>
PYrunPythonStatements(char const*, PY_EvaluationContext*) <libHoudiniUT.so>
PYrunPythonStatementsAndExpectNoErrors(char const*, char const*, PY_EvaluationContext*) <libHoudiniUT.so>
BR_HelpManager::initializeHelpServer() <libHoudiniUI.so>
BR_HelpManager::BR_HelpManager(bool) <libHoudiniUI.so>
FUSE_HelpManager::FUSE_HelpManager(FUSE_App&) <libHoudiniAPPS3.so>
FUSE_App::FUSE_App(char const*) <libHoudiniAPPS3.so>
FUSE_HoudiniBinariesApp::createApplication(int&, char const**) <libHoudiniAPPS3.so>
OPUI_MainApp::initApplication(UI_Manager*, int, char const**) <libHoudiniAPPS2.so>
main <libHoudiniUI.so>
__libc_start_main <libc.so.6>
_start <houdini-bin>

And when I tried to run with Bumblebee Optimus, I've got the following,

/opt/hfs16.0/bin/houdini-bin: relocation error: /opt/hfs16.0.671/dsolib/Qt_plugins/xcbglintegrations/libqxcb-glx-integration.so: symbol _Z20QT_XCB_GLINTEGRATIONv, version Qt_5_PRIVATE_API not defined in file libQt5XcbQpa.so.5 with link time reference

Any help would be appreciated. Thank you


goldfarb: スタッフ; 3464 posts; Joined: 7月 2005; Offline

2017年8月1日 13:06

can those of you having difficulty with Houdini on Fedora 26 (or any other release)
please contact support through this link
https://www.sidefx.com/bugs/submit/ [www.sidefx.com]

the forums are a great place to get quick help but many issues require a bit more attention.

Michael Goldfarb | www.odforce.net
Training Lead
SideFX
www.sidefx.com


varomix: Member; 460 posts; Joined: 7月 2005; Offline

2017年8月10日 1:10

To solve that python issue I set Houdini to use the internal python version instead of Fedora version
like this in the houdini.env file

HOUDINI_USE_HFS_PYTHON=1

varomix - Founder | Educator @ Mix Training
Technical Artist @ Meta Reality Labs


chrisc: Member; 8 posts; Joined:; Offline

2017年8月11日 6:02

varomix
To solve that python issue I set Houdini to use the internal python version instead of Fedora version
like this in the houdini.env file

HOUDINI_USE_HFS_PYTHON=1

Thanks to you Varomix, after weeks of struggle with Debian 9, Houdini Apprentice runs fine on my system, at long last !

Thanks again for your help and your youtube channel

Chris


tricecold: Member; 260 posts; Joined: 7月 2006; Online

2017年8月27日 7:53

I installed 26 two days ago, it works fine here, but a few exceptions, running qt4 version, disabled Wayland, and installed Nvidia official Nvidia drivers, current openGL performance is slightly better than Windows 10

Head of CG @ MPC
CG Supervisor/ Sr. FX TD /
https://gumroad.com/timvfx [gumroad.com]
www.timucinozger.com


Arthur_Ivanov: Member; 13 posts; Joined: 9月 2015; Offline

2017年9月6日 5:15

varomix
HOUDINI_USE_HFS_PYTHON=1

Many thanks man for the tip, I append this line in env file and for now all works fine for me with houdini on fedora 26 KDE.

Cheers!

FX Artist at Progressive FX.


chrysl666: Member; 12 posts; Joined: 2月 2007; Offline

2018年3月10日 19:25

varomix
To solve that python issue I set Houdini to use the internal python version instead of Fedora version
like this in the houdini.env file

HOUDINI_USE_HFS_PYTHON=1

Tnx Varomix very useful tip!!

Quick Links

                    
                        Search links
                        Show recent posts
                        Show unanswered posts