UFO:Alien Invasion
Technical support => Bugs in stable version (2.5) => Topic started by: SoftwareSimian on May 06, 2013, 09:11:36 pm
-
I just downloaded the latest (2013-May-06) Windows binaries, and the game now crashes on startup. It gets to about 25% of the splash loading screen progress bar, and then crashes to desktop. I reverted to 2013-Apr-17 binaries and confirmed it works fine, also re-downloaded the current binaries just to make sure.
As it crashes to desktop the console is very briefly (0.2s or thereabouts) visible, and I managed to grab a screenshot (attached), but it doesn't show much useful, the last line is "--- parse scripts ---- 57 script files"
2013/05/06 15:05:10 FS_RemoveFile: remove C:\Users\User\AppData\Roaming\UFOAI/2.5-dev/base/keys.cfg
2013/05/06 15:05:11 There are still 1 opened files
-
Attach the full ufoconsole.log
-
I quoted it verbatim above. It doesn't contain anything useful, just what I quoted above. But attached as requested.
-
I quoted it verbatim above. It doesn't contain anything useful, just what I quoted above. But attached as requested.
Only two lines. I don't think I've seen that before.
-
I downloaded today's binaries and the problem persists, so it wasn't just a compilation glitch.
Yes, ufoconsole.log just contains two lines, always the same two lines, but the timestamp at the start of each line is changed on each launch, so it must be clearing the file and rewriting the log on each launch.
The path noted in the log (C:\Users\User\AppData\Roaming\UFOAI/2.5-dev/base/keys.cfg) is correct (mixed slashes aside), but that directory does not contain keys.cfg
-
Did you only download the binaries, the exe files? It is possible that there was an incompatible ufo-script format change meanwhile. That could cause early-exit on script parsing stage.
-geever
-
I had been trying binaries-only.
Today I downloaded the binaries-only, and the full installer, and both had the same result as before. Crash to desktop, nothing useful in ufoconsole.log
Any further suggestions?
-
I'm not sure what the problem was, but I tried deleting the whole installation folder and re-installing from the full installer I had already tried above, and it seems to work fine now. Sorry for the false alarm.