Problem loading any games with Doomsday

SlimeHudson

Hi, I've been trying to play some games with Doomsday, but it seems that I am missing the OpenAL library for it. Because of this, I get an error message after attempting to play a game. My OUT file is here (opens in-browser and should display as text) and a screenshot of the error dialog box is here. However, the dialog box reports something about showing FPS, whereas the OUT file mentions that the OpenAL library is missing. Which one is correct and how do I fix it?

Thanks

DaniJ

The error dialog and the warning about OpenAL in your log are unrelated. The OpenAL warning is because this library is for some reason missing in the install but it can be ignored (unless you wanted to use it specifically, of course).

It looks like something went a little awry with your upgrade, though, as window.main.showFPS should be defined by default in your config. Try a -reconfig to get Doomsday to regenerate this file. As you are running Doomsday from the front end you can do this by adding that to Settings -> Developer -> Custom options. Run Doomsday and then remove this option when you return to the front end as it does not need to be done every time.

SlimeHudson

Ah, thanks, that solved my problem.

Vermil

I had this issue when updating from a build prior to the additional of the new fps counter.

The config files from earlier builds (and presumably stable versions), as is, seem incompatible with it; as DaniJ mentions.

skyjake

The problem was most likely caused by the error fixed in this commit.

@SlimeHudson: I assume you have previously been running some earlier version of Doomsday on your system?

Until that fix was applied, what has been happening was that whenever you started Doomsday, it would think that it was running a build from that particular day, even if you hadn't really upgraded. We are nowadays running a bunch of scripts at the launch of the application, and one of the things these scripts do is check whether you have installed a new build and if so, update your config automatically. (So far this only applies to the new libdeng2 stuff, though.)

When we add new variables to the libdeng2 Config, their default values will be automatically added to your personal copy of the Config without touching any of your existing settings. However, this cannot (and didn't) work properly unless the installed build number is detected correctly.

In practice, your personal copy of the Config is stored in the persist.pack file in your runtime folder. You can also delete it to force everything to the defaults (which is equivalent to using the -reset command line option).

In the future, we will be moving all of the console variables and other settings into the libdeng2 Config, but of course until that time we must make sure the mechanism is working flawlessly. Finding and fixing issues like the one in this thread is very important.