Vasileios Kontodimas
vakont
About Me
Project creator and innovator.
EXPERTISE
CG Supervisor
INDUSTRY
Film/TV
Connect
LOCATION
United States
WEBSITE
Houdini Skills
Availability
Not Specified
Recent Forum Posts
Houdini and Fedora 26 July 24, 2017, 9:21 p.m.
Michael RochefortThat 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.
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.
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. :-)
Houdini and Fedora 26 July 24, 2017, 5:56 p.m.
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. :-)
Houdini and Fedora 26 July 23, 2017, 11:01 a.m.
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>