Daily build won't launch

   624   16   4
User Avatar
Member
90 posts
Joined: April 2018
Offline
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.)
Edited by BrianHanke - Oct. 24, 2020 13:51:57
http://youtube.com/brianhanke [youtube.com]
http://twitter.com/brianhanke [twitter.com]
https://www.instagram.com/brianrhanke [www.instagram.com]
http://facebook.com/brianrhanke [facebook.com]
User Avatar
Member
3954 posts
Joined: Sept. 2011
Offline
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.
User Avatar
Member
90 posts
Joined: April 2018
Offline
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!
http://youtube.com/brianhanke [youtube.com]
http://twitter.com/brianhanke [twitter.com]
https://www.instagram.com/brianrhanke [www.instagram.com]
http://facebook.com/brianrhanke [facebook.com]
User Avatar
Member
4990 posts
Joined: July 2007
Online
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
Edited by tamte - Oct. 25, 2020 00:27:08
Tomas Slancik
FX Supervisor
Method Studios, NY
User Avatar
Member
90 posts
Joined: April 2018
Offline
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!
http://youtube.com/brianhanke [youtube.com]
http://twitter.com/brianhanke [twitter.com]
https://www.instagram.com/brianrhanke [www.instagram.com]
http://facebook.com/brianrhanke [facebook.com]
User Avatar
Staff
186 posts
Joined: Feb. 2018
Offline
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.
Edited by mabelzile - Oct. 26, 2020 10:36:22
User Avatar
Member
314 posts
Joined: July 2013
Offline
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.
Edited by Daryl Dunlap - Oct. 26, 2020 10:41:34
Houdini Indie
Redshift 3D
User Avatar
Member
90 posts
Joined: April 2018
Offline
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.
http://youtube.com/brianhanke [youtube.com]
http://twitter.com/brianhanke [twitter.com]
https://www.instagram.com/brianrhanke [www.instagram.com]
http://facebook.com/brianrhanke [facebook.com]
User Avatar
Staff
2288 posts
Joined: Sept. 2007
Offline
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]
Edited by chrism - Oct. 26, 2020 11:59:46
Chris McSpurren
Senior Quality Assurance Specialist
SideFX
User Avatar
Member
90 posts
Joined: April 2018
Offline
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.
http://youtube.com/brianhanke [youtube.com]
http://twitter.com/brianhanke [twitter.com]
https://www.instagram.com/brianrhanke [www.instagram.com]
http://facebook.com/brianrhanke [facebook.com]
User Avatar
Member
4990 posts
Joined: July 2007
Online
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
Edited by tamte - Oct. 26, 2020 13:44:39
Tomas Slancik
FX Supervisor
Method Studios, NY
User Avatar
Member
3954 posts
Joined: Sept. 2011
Offline
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.
User Avatar
Member
90 posts
Joined: April 2018
Offline
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.
http://youtube.com/brianhanke [youtube.com]
http://twitter.com/brianhanke [twitter.com]
https://www.instagram.com/brianrhanke [www.instagram.com]
http://facebook.com/brianrhanke [facebook.com]
User Avatar
Staff
2288 posts
Joined: Sept. 2007
Offline
We're working on a packages fix.
Chris McSpurren
Senior Quality Assurance Specialist
SideFX
User Avatar
Staff
186 posts
Joined: Feb. 2018
Offline
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.
User Avatar
Staff
186 posts
Joined: Feb. 2018
Offline
The problem should be resolved with H18.5.378.
User Avatar
Member
314 posts
Joined: July 2013
Offline
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.
Houdini Indie
Redshift 3D
  • Quick Links