Thomas Helzle

ThomasHelzle

About Me

Expertise
Freelancer
Location
Germany

Connect

Recent Forum Posts

Houdini 16 Feb. 22, 2017, 10:44 a.m.

Thanks Marc, not sure I want to go there yet since it creates additional clutter.
I'd rather find out what the problem actually is.
For the time being, I use the Qt4 version from yesterday.

Cheers,

Tom

Houdini 16 Feb. 22, 2017, 9:44 a.m.

Hm - could those localisation problems be the sources of my failures too?
I use Windows 8.1 x64 in english but with a german keyboard that uses a coma as well…

I attached a screenshot of the error windows I get on start.
If I close the QtWebEngineProcess.exe window, it comes up once again and if I close it again, it crashes the QtWebEngineProcess.exe
The “Error in context event handling” I can close a hundred times, it always comes back with the same message.

Starting Houdini Indie as admin doesn't change it.

It's not the non-default installation path either, I tried an installation there as well.

The Qt4 version that was available yesterday works without this problem.

Cheers,

Tom

Houdini 16 Feb. 22, 2017, 5:53 a.m.

malbrecht
The most likely issue to me seems to be a Python hickup. Do you have some global Python ENV VARs that might interfer with Houdini's Python? H is using a packaged 2.7, but it may well be possible that it tries to use your installed 3.x or whatever - and fails.
One thing you could try is set up a clean user (assuming you are setting environments for users, not globally for administrators) and check if H16/Qt5 works there. A virtual machine with a clean Windows install also comes in handy to have a quick go at comparing setups.

Else the best thing you can do is send your report to support@sidefx.com - they may be slightly drowning in requests right now, so cut them some slack

Marc
Hm - I went through my user and system paths and didn't find any python or Qt related entries, not sure where else to look. I don't have python installed separately.
I sent a bugreport to support, just thought somebody may have seen the same and found a solution.
I'll re-install the qt 4 version for the time being I guess…

Cheers,

Tom