Game Closing.

[Jeromemon]

Hello, provding the information from the Steam Discuss post.

All the log files look the same.

Hello,

i got an issue with my game whenever i try to start anything no matter if it is a base campaign ,scenario or any type of add-on, it closes itself.

No Error Message, in campaign all it does is give me the text before the actual scenario and as soon it's done, closing.

I tried downloading it standalone, Deleted all files, including save files and add-on.
Pc restart, changing language, it has writing rights, tried combability modes, it's in admin mode, changned the compress mode of save files.

I am kind of lost here and could really use some help.

I tried the 1.17 version same Issue. 1.14 does not have that issue.

Here the Version Info:

Code: Select all

The Battle for Wesnoth version 1.16.5 x86_64
Running on Microsoft Windows 10 21H2 (10.0.19044) x86_64
Distribution channel: Steam

Game paths
==========

Data dir:        C:\Program Files (x86)\Steam\steamapps\common\wesnoth
User config dir: C:\Users\USER\Documents\My Games\Wesnoth1.16
User data dir:   C:\Users\USER\Documents\My Games\Wesnoth1.16
Saves dir:       C:\Users\USER\Documents\My Games\Wesnoth1.16\saves
Add-ons dir:     C:\Users\USER\Documents\My Games\Wesnoth1.16\data\add-ons
Cache dir:       C:\Users\USER\Documents\My Games\Wesnoth1.16\cache

Libraries
=========

Boost:             1.79
Lua:               5.4.2
OpenSSL/libcrypto: 1.1.1o (runtime 1.1.1o)
Cairo:             1.17.6 (runtime 1.17.6)
Pango:             1.50.7 (runtime 1.50.7)
SDL:               2.0.22 (runtime 2.0.22)
SDL_image:         2.0.5 (runtime 2.0.5)
SDL_mixer:         2.0.4 (runtime 2.0.4)

Features
========

Lua console completion:       yes
Win32 notifications back end: yes

Current video settings
======================

SDL video drivers:       [windows] dummy
Window size:             1280x768
Screen refresh rate:     60
Screen dots per inch:    96,000000x96,000000
Screen dpi scale factor: 1,000000x1,000000

Current audio settings
======================

SDL audio drivers:  [wasapi] directsound
Number of channels: 2
Output rate:        48000 Hz
Sample format:      signed 16 bit little-endian
Sample size:        4096 bytes

Installed add-ons
=================

No add-ons installed.

The Log:

Code: Select all

Battle for Wesnoth v1.16.5 x86_64
Started on Wed Jul 27 20:39:17 2022

Automatically found a possible data directory at C:\Program Files (x86)\Steam\steamapps\common\wesnoth

Data directory:               C:\Program Files (x86)\Steam\steamapps\common\wesnoth
User configuration directory: C:\Users\USER\Documents\My Games\Wesnoth1.16
User data directory:          C:\Users\USER\Documents\My Games\Wesnoth1.16
Cache directory:              C:\Users\USER\Documents\My Games\Wesnoth1.16\cache

Setting mode to 1280x768
Checking lua scripts... ok

This should be everything.

[Pentarctagon]

If you go to the folder Wesnoth was installed in and run cwesnoth.cmd, once Wesnoth crashes is anything additional printed to the console that opens?

[Jeromemon]

The cwesnoth.cmd starts the game and closes as soon the game closes down as well.

It's the same log entry. No change at all.

[Pentarctagon]

I was wondering if it would do that, which isn't very useful. In that case then:

• Open a command prompt (search cmd.exe from the start menu.
• Type cd C:\path\to\install\folder.
• Type wesnoth.exe --wconsole --wnoredirect.
• Make the game crash.
• Check if there's anything additional printed on the command prompt after the crash.

[Jeromemon]

It gives out the exact same information like in the log i already shared, nothing new added.

[Pentarctagon]

Well, that's odd. Can you try running wesnoth.exe --wconsole --wnoredirect --log-debug=all > wesnoth.log 2>&1 and uploading that here?

[Jeromemon]

So i ran that command, It took quite a bit to start up the game and i tried to play and it worked! No closing or crash.

I didn't get any different Log file from that. It's the same as before.
And i forgot to take a screenshot of the CMD window. But it had a lot about "Firing raw file".
That's all i remember sorry.

But thank you a lot for fixing my game!

[Pentarctagon]

Wait, what? All that should have done differently was enable a *ton* of logging (literally all of it), but it shouldn't have actually fixed anything. Does it work when you launch it from Steam now too?

[Jeromemon]

Yes it runs fine, no problems at all, i tried playing before using the command and i still had the issue. Afterwards it worked just fine.

Yeah i can use it from steam just fine now, i also did nothing else that could have fixed it.

Should i try running the command again and screenshot the command window?

[Pentarctagon]

At this point if it works then whatever the issue was has been solved, so I don't think there'd be anything useful in the logs now.

[Jeromemon]

Alright, i am not sure what it did but thank you a lot for helping me.