Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WZ 4.4.0 #3481

Closed
cfosp1 opened this issue Nov 7, 2023 · 10 comments
Closed

WZ 4.4.0 #3481

cfosp1 opened this issue Nov 7, 2023 · 10 comments
Labels
Milestone

Comments

@cfosp1
Copy link

cfosp1 commented Nov 7, 2023

WZ 4.4.0 does not start after playing one single player game

I installed 4.4.0 this morning.
Played one game, no problems
Tried playing a second game by selecting a game and clicking start
WZ froze, displaying final screen of previous game played.
Tried to restart, WZ seems to be loading but nothing visible on screen
Tried to start a second time, same behavior
Checked Task Manager, 2 instances of WZ listed in processes.
Killed both instances, tried again, same behavior
Restarted PC, tried again, same behavior

Expected behavior
Expect WZ to load as usual

Screenshots or Videos
N/A

Your System:

  • OS: Windows 11
  • Game version: 4.4.0, 64-bit

Additional context
Previous version ran without a hitch
Attempted to reinstall, install hangs with the following message

image

@cfosp1 cfosp1 added the Bug label Nov 7, 2023
@past-due
Copy link
Member

past-due commented Nov 7, 2023

Are you using the full installer? (Not the portable version.)

If so, please use the following instructions to open the game's configuration directory:

The directory Warzone 2100 Project\Warzone 2100 <version> is located under the %APPDATA% folder.

Hence, the default path for the Warzone 2100 configuration data on Windows Vista+ would be: C:\Users\$USER$\AppData\Roaming\Warzone 2100 Project\Warzone 2100 <version>\

By default, the %APPDATA% folder is hidden. Entering: %APPDATA%\Warzone 2100 Project\ into the address bar of Windows Explorer / File Explorer will browse to your Warzone directory.

After you've located and opened the Warzone 2100 configuration directory, please locate the file named config and check to see how large it is. Then rename it config_old, and try to relaunch WZ.

@cfosp1
Copy link
Author

cfosp1 commented Nov 7, 2023

Used full installer; the fix you suggested worked, thank you. I was amazed about the size of the old config file.

@past-due
Copy link
Member

past-due commented Nov 7, 2023

Used full installer; the fix you suggested worked, thank you. I was amazed about the size of the old config file.

How big was the old config file? (And do you still have it - or is it recoverable from your Recycle Bin / Trash - and could you zip it and upload it somewhere?) We've been trying to track down a rare bug for ages that can lead to garbage data in the config file.

@cfosp1
Copy link
Author

cfosp1 commented Nov 7, 2023

I thought it was 556 MB, turns out it is 556 GB. Not sure this is practicable. Any thoughts?
image

@past-due
Copy link
Member

past-due commented Nov 7, 2023

I thought it was 556 MB, turns out it is 556 GB. Not sure this is practicable. Any thoughts?

Could you truncate the file to the first, say 20-50MB, and then try zipping and uploading that?

(You may be able to follow the instructions here, although I haven't tested them on Windows: https://superuser.com/a/1634250)

(I am assuming that length is specified in bytes(?), so it would be something like:
FSUTIL file seteof config 20971520 to truncate it to 20 MB, presumably. Again, untested, and you'd want to cd into the directory that contains the config file - not sure how comfortable you are using the Command Prompt?)

@cfosp1
Copy link
Author

cfosp1 commented Nov 7, 2023

Command prompt not a problem. Here is the link to the truncated file. I hope it has the info you need because the original config.old was replaced by the truncated file.

@KJeff01
Copy link
Member

KJeff01 commented Nov 7, 2023

Command prompt not a problem. Here is the link to the truncated file. I hope it has the info you need because the original config.old was replaced by the truncated file.

I sent you an access request so you'll have to approve me so I can grab your file.

@cfosp1
Copy link
Author

cfosp1 commented Nov 7, 2023 via email

@KJeff01
Copy link
Member

KJeff01 commented Nov 8, 2023

👍 Yes, I got the file.

@KJeff01
Copy link
Member

KJeff01 commented Nov 20, 2023

This config issue has probably been resolved with #3489.

@KJeff01 KJeff01 closed this as completed Nov 20, 2023
@KJeff01 KJeff01 added this to the 4.4.1 milestone Nov 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants