Hello m100madness,

Yoou log seems to stop before any of the games code is even running, which suggests a very basic issue to be present as not even Unity (our game engine) seems to start correctly.


can you check if you use AVG Antitvirus and if so if disabling it fixes the problem when you start the game?
AVG likes to find a false positive and block off some of the games resources.
In this case add an exception for WFTO.exe and WFTOGame.exe in the games installation folder.

Further to, can you check if you are using wireless headphones and if so if unpluging them fixes it?
In this case make sure they are set as default audio output and to stereo, otherwise Unity (our game engine) likes to crash.

There are more possible things to try.
Here is a full ist:
http://brightrockgames.userecho.com/topics/1093-startup-crashes/
http://brightrockgames.userecho.com/topics/1094-general-crash-troubleshooting/

Hope any of that helps!

This sounds odd because it was working before indeed.
However we did some changes to the Veins of Evil to avoid players getting locked off further down aspects by disabling early aspects.
Maybe this change broke it, anyway we will have to test this next week.

The number behind is a suggested free slot the player can switch to to resolve the error.
These two translation keys are very old from a time before the game wasn't even released and the company was in danger to run out of money.
The way this message is handled needed to change after official translations provided by a thirdparty were already done, but we saw no way to get anything else translated soon to other languages.
Thus we kept the old key despite it did not match it's purpose anymore to 100%.

Essentially these two translation keys need to be redone to suggest exactly one slot to the player he can use to get a rid of the error.
I will bring that up in the team next week.

Hey Policeofficer110,
These are so called "proper names" which are not supposed to be translated as far as I am aware and they are like this in any supported language we have.
Maybe Lee can explain why.

We needed to quickly look at multiple issues this saturday to get an hotfix out which had more pressing problems than this.
So we found a potential cause for the problem which we fixed but did not took the time to test if it does so in fact.
We'll be looking into this one again next week when it is a bit more calmed.
The save game will help to reproduce quicker I hope.