Farmfield Posted June 30, 2016 Share Posted June 30, 2016 Windows 10 - because of course. And yeah, I would rather run Centos but now I don't. I get this console error, and that's it, Houdini doesn't start. ERROR: Couldn't open resource file “resources” (No such file or directory) Houdini could not load (null)/python27/python27.dll Tried reinstalling, but no luck. Tried reinstalling Python - and yeah, I know Houdini has it's own, but I thought I might as well if it's connected to that - but no. And it's not in the Houdini.env or alike either, renaming the folder (forcing Houdini creates a new) still yield the same error. Quote Link to comment Share on other sites More sharing options...
michael Posted June 30, 2016 Share Posted June 30, 2016 please post a bug report thanks Quote Link to comment Share on other sites More sharing options...
Farmfield Posted June 30, 2016 Author Share Posted June 30, 2016 Done. The question is if there's a workaround. Obviously Houdini lacks a variable for the path to the resources folder, though haven't managed to figure out where, if it's in the Houdini install or in Windows. Quote Link to comment Share on other sites More sharing options...
Farmfield Posted June 30, 2016 Author Share Posted June 30, 2016 Reverted to the previous install and Houdini works perfectly. That's some oddness I'm not used too, I can't even remember when I had an app not start in Windows due to incompatibility issues. Well, it's logged as a bug, lets hope they solve it before the actual August 2 release of Windows 10 "Redstone". Quote Link to comment Share on other sites More sharing options...
Maj. Dave Posted September 11, 2020 Share Posted September 11, 2020 Bit of a callback to this old posting - I just changed our application startup code for Houdini and got punked by this. In my case, it was because I attempted to use environment resolution through Rez for the `HOUDINI_PATH` - but included windows-style environment variable notation: `%VAR%/path/to/dir` Changing these to UNIX-style environment variable notation: `$VAR/path/to/dir` solved my problem. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.