Jump to content

Just installed that benchmark, tried to run it, but all I got were weird errors, complaining about stuff that shouldn't be an issue.

 

Here's the error-log:

 

 


14:11:00 Xml::load(): can't open "D:/Program Files (x86)/Unigine/Heaven Benchmark 4.0/bin/unigine.cfg" file
14:11:00 Config::load(): can't open "D:/Program Files (x86)/Unigine/Heaven Benchmark 4.0/bin/unigine.cfg" file
14:11:00 Engine::init(): can't initialize filesystem
14:11:44 Shutdown
 
The paths are correct but the unigine.cfg file is indeed missing. I did change the default installation path, since C is an SSD-drive that's mostly reserved for OS.
 
I'm also getting different errors upon launching from the shortcut or from the heaven.exe within the "bin"-folder. Program complains that it can't open "browser_x86.exe" which is clearly there in the folder. Already created an empty text-file and renamed it unigine.cfg and made sure that the whole folder had write-protection set to off.. it was on by default for some reason.
 
Still.. no joy.
 
Any idea what could be wrong here?
 
 
S.
Link to comment
https://linustechtips.com/topic/48730-help-unigine-wont-launchinitialize/
Share on other sites

Link to post
Share on other sites

  • 1 year later...

I'm having the exactly same issue. I've re-installed it a few times and it still won't come up with the file. Does anyone want to just upload the file so I can just plug it in manually or something? I'm using the most recent version from Unigine's website

Link to post
Share on other sites

  • 6 months later...

Don't mean to necro this thread, if it hasn't already done so, but I just came back to this same issue. No matter how many times I reinstalled (whether uninstalling beforehand or not) it came up with the same error.

 

The solution was to add a desktop shortcut (maybe the start menu shortcut would work, too?) and run it from there. The Valley.exe in the bin folder still doesn't work, but the desktop shortcut ran no problem. 

Link to post
Share on other sites

  • 2 months later...

Don't mean to necro this thread, if it hasn't already done so, but I just came back to this same issue. No matter how many times I reinstalled (whether uninstalling beforehand or not) it came up with the same error.

 

The solution was to add a desktop shortcut (maybe the start menu shortcut would work, too?) and run it from there. The Valley.exe in the bin folder still doesn't work, but the desktop shortcut ran no problem. 

I think it is because most are trying to run the Heaven.exe file in bin. It's an easy mistake to make. However, the program runs from the primary folder through heaven.bat. It may also be worth noting here that Windows 10 does not appear to be adding this to the start menu. Admittedly, I have encountered that with a lot of programs including MS Office software.

 

 sshot-2015-09-21-%5B19-43-32%5D.png

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×