Critical Error during game start.

Avatar
  • Views 12,904
  • updated
  • Completed - Resolved

When attempting to load the game, I'm met with the following error:


Critical error during game start

"Sharing violation on path C:\Program Files (x86)\Steam\steamapps\common\War For The Overworld\WFTOGame_Data\GameData\Options.txt"

The game cannot start.


I have checked the file and cannot find any issues with the contents. In case I'm missing something though, it reads as follows;


FirstLaunchLanguageDetection=
Lang=0
HoGLaunched=True
DLC=HeartOfGold
Screen Width=1920
Screen Height=1080
Screen Refresh Rate=60
FullScreenMode=True
Gamma=20
V-Sync=True
Camera Zoom Max=30
Editor Camera Zoom Max=50
Needs Pixel Light Upgrade=False
Pixel Light Count=10


This is the same computer that I have used to play the game for many hours before with no issues. I'm at a loss of what could be the cause of this issue.

Game Version:
Steam Public
Platform:
Windows

How would you rate the customer service you received?

Satisfaction mark by Voltoth 7 years ago

Add a comment about quality of support you received (optional):

Avatar
anonymous
  • Pending Customer

Hey Voltoth,


Can you please attempt to delete the file and try to open the game again?

Avatar
Voltoth

That was the first thing I did, I have tried multiple times since then with no joy.

Avatar
anonymous

Could you please try the steps in our Startup Crashes guide

Avatar
Voltoth
Quote from anonymous

Could you please try the steps in our Startup Crashes guide

Tried every step and still have the same issue.

Avatar
Voltoth

Have even tried uninstalling and reinstalling on a different drive. Same issue still persists.

Avatar
Stefan Furcht

Hello Voltoth,

could you trigger this problem again, quit the game and then save and upload your output_log file  in your reply before starting the game again

(Attach the file to your reply clicking the "File" button above the text area).

Here is described how to do that:

http://brightrockgames.userecho.com/forums/2-war-for-the-overworld-knowledge-base/topics/118-how-to-submit-a-bug-ticket/


A look into this file can help us to get a deeper insight where the problem occurs exactly and thus likely find out more about the cause.


Cheers!

Avatar
Voltoth
Quote from Stefan Furcht

Hello Voltoth,

could you trigger this problem again, quit the game and then save and upload your output_log file  in your reply before starting the game again

(Attach the file to your reply clicking the "File" button above the text area).

Here is described how to do that:

http://brightrockgames.userecho.com/forums/2-war-for-the-overworld-knowledge-base/topics/118-how-to-submit-a-bug-ticket/


A look into this file can help us to get a deeper insight where the problem occurs exactly and thus likely find out more about the cause.


Cheers!

output_log.txt


As requested, here is the output log file. I hope this helps, I miss playing this amazing game.

Avatar
Stefan Furcht
  • Under Review

Thanks a lot, we will take a look!

Avatar
Stefan Furcht
  • Started
Avatar
Stefan Furcht

Hello Voltoth,


I am sorry for coming back to you late but I got delayed for personal reasons.

The log helped to find the code which is triggering the exception, but it looks correct and wouldn't fail under normal circumstances. 

(We got never any report of a similar issue before and it works fine for everyone I am aware about)

However it looks like the problem would be caused if any other program tries to read or write Options.txt while the game is trying to access this file as well.
The question is, why would another program do this?


Is there any chance you opened Options.txt in any viewer or any other program which locks the file entirely?

If you are aware about such program, please try to close / release this file before starting the game.


Another potential cause could be an anti virus software which has very agressive heuristic and finds the frequent writes the game does to the file suspicious and might thus lock the file away.

Please check if disabling your AV software does solve the problem and if so activate it again (anyway) and add an exception for WFTO.exe and WFTOGame.exe to avoid it doing so, or reduce the agressiveness of heuristic search.


I hope any of this helps!