I want to use the latest daily build with the Karma license fix, but it won't launch for me. I get a “Couldn't open file: FUSE_ColorOptions.ui” error. Production build works fine. Any ideas how to fix this? Thanks! (Windows 10 by the way.)

BrianHanke
I want to use the latest daily build with the Karma license fix, but it won't launch for me. I get a “Couldn't open file: FUSE_ColorOptions.ui” error. Production build works fine. Any ideas how to fix this? Thanks! (Windows 10 by the way.)

Disable all third party renderers. I got this error until I disabled 3Delight.

jsmack
Disable all third party renderers. I got this error until I disabled 3Delight.

Thanks, I tried but that wasn't it. I did figure it out though, so here's the solution for anybody who might be looking. For some reason the two most recent daily builds look for the Houdini files in C:\Program Files\Side Effects Software\Houdini 18.5.375\packages\viewer_handle_demo, but they're all actually in C:\Program Files\Side Effects Software\Houdini 18.5.375\houdini. There's probably some config file thing to fix this, but I just copied all the files to the viewer_handle_demo folder. Working so far!

it looks like the main houdini path is not being added to $PATH variable

and sicne every package attaches it's path to $PATH variable it tries to find config files in there

I created new package json and named it something that hopefully executes first (if that matters), like $HPS/packages/_.json
with this in it:

which works as a workaround, I'm pretty sure this will be fixed soon though

tamte
it looks like the main houdini path is not being added to $PATH variable

and sicne every package attaches it's path to $PATH variable it tries to find config files in there

I created new package json and named it something that hopefully executes first (if that matters), like $HPS/packages/_.json
with this in it:

{
    "path" : "$HFS/houdini"
}

which works as a workaround, I'm pretty sure this will be fixed soon though

Nice, that works perfectly. Thanks!

I just installed 18.5.376 and it starts fine. How can I reproduce the problem ?

I don't understand how your workaround can add the houdini path to $PATH as path is just a shortcut for $HOUDINI_PATH.

mabelzile
I just installed `18.5.376` and it starts fine. How can I reproduce the problem ?

It seems that the root Houdini folder is not automatically being added to the Houdini_Path with packages (only packages it seems).

If you configure your 3rd party engine with the Houdini.env, all works fine.

mabelzile
I just installed 18.5.376 and it starts fine. How can I reproduce the problem ?

I don't understand how your workaround can add the houdini path to $PATH as path is just a shortcut for $HOUDINI_PATH.

I just checked 377 and it has the same problem. I don't have any other renderers or addons installed. The current production build works fine. All I know is that the most recent daily builds look for the Houdini files in the packages/viewer_handle_demo/ folder, but they're not there. I can fix the problem by either copying all the /houdini/ files and folders to /viewer_handle_demo/ or by using the fix posted above.

Hi Brian! You may want to a) log a bug and b) clear out your prefs or move them aside.
In the bug, you can include your prefs and system info and let us know if you installed with the regular installer or the launcher.
Thanks! I just installed and ran 18.5.377 on windows with the regular installer and it's working fine for me, but I don't have your prefs. We'd like to figure out why it's not working for you.

https://www.sidefx.com/forum/topic/25347/ [www.sidefx.com]

chrism
Hi Brian! You may want to a) log a bug and b) clear out your prefs or move them aside.
In the bug, you can include your prefs and system info and let us know if you installed with the regular installer or the launcher.
Thanks! I just installed and ran 18.5.377 on windows with the regular installer and it's working fine for me, but I don't have your prefs. We'd like to figure out why it's not working for you.

https://www.sidefx.com/forum/topic/25347/ [www.sidefx.com]

Ah, that was it. I deleted everything in the houdini18.5 folder and restarted 377. Launched just fine. I'll send an email to support with the info anyway. Maybe there was an incompatibility with whatever was in my 18.5 production build prefs.

mabelzile
I don't understand how your workaround can add the houdini path to $PATH as path is just a shortcut for $HOUDINI_PATH.

it's just that main $HFS/houdini was not in $HOUDINI_PATH as it should have been, but on a second look, I also had 3delight package in my user prefs and that was directly changing the $HOUDINI_PATH environment variable instead of using the “path” approach to append to it
so editing 3delight package fixed it more properly without the need to remove it or delete user prefs

tamte

mabelzile
I don't understand how your workaround can add the houdini path to $PATH as path is just a shortcut for $HOUDINI_PATH.

it's just that main $HFS/houdini was not in $HOUDINI_PATH as it should have been, but on a second look, I also had 3delight package in my user prefs and that was directly changing the $HOUDINI_PATH environment variable instead of using the “path” approach to append to it
so editing 3delight package fixed it more properly without the need to remove it or delete user prefs

So is this a bug with handling setting HOUDINI_PATH directly in packages? The same package file is working fine for me with 18.5.351.

I emailed support and included pics of my houdini18.5 folder comparing the production build and after I purged it and let 377 repopulate. Can confirm that I had a 3Delight item in there even though I uninstalled the renderer. Looking like that's the culprit here.

We're working on a packages fix.

The issue with the packages is due to a regression introduced in build H18.5.375, I'm currently working on a fix. Setting HOUDINI_PATH with a single value is ok, it should work again once the regression is fixed.

The problem should be resolved with H18.5.378.

mabelzile
The problem should be resolved with H18.5.378.

Confirmed. H18.5.378 is working with packages again. Thanks for the quick fix SideFX.

Hello just checking as I downloaded latest Houdini 20.5.410 on Windows 11 (clean machine, no older install ) and trying to start Houdini via my own .bat setup file ( which used to work with Houdini 19, but no longer works.
I was able to figure out a lot of the missing variables I need to setup in my .bat, but am still getting the error ...

ERROR: Couldn't open resource file "resources" (No such file or directory)
ERROR: Couldn't find 'FUSE_ColorOptions.ui' for reading. Looked in:
C:/Program Files/Side Effects Software/sidefx_packages/SideFXLabs20.5/config/Applications
C:/Program Files/Side Effects Software/Houdini 20.5.410/packages/sculpt/config/Applications
C:/Program Files/Side Effects Software/Houdini 20.5.410/packages/kinefx/config/Applications
C:/Program Files/Side Effects Software/Houdini 20.5.410/packages/apex_cop/config/Applications
C:/Program Files/Side Effects Software/Houdini 20.5.410/packages/apex/config/Applications
C:/Program Files/Side Effects Software/Houdini 20.5.410/sidefx_packages/SideFXLabs20.5/config/Applications

I tried looking for this file, but cannot find it ???
And not sure where I can find it ???
The splash screen does start, but then app shuts down.
Any work around I can setup in my .bat pre-processing (trying to KISS) or hint to bupass this problem would be greatly appreciated.