Reopenend as now occuring again on 1.4.2f4

That's a shame to hear. It's possible that we don't yet have the version of Coherent in our game that John was alluding to. I expect we'll be able to roll that in for the next patch, I'll be sure to check with our code team whether or not we have the latest version.

The Bluescreen sounds somewhat worrying I wish I could advise you further on that but Windows isn't my speciality I'm afraid. :(

All text we create is automatically translated into a variety of languages and stored in a CSV file which is used for languages. If you load a language in game that whole language is loaded with no exceptions. Anything which never received an official translation has received machine translations.

Theoretically it's possible to do so by editing the CSV file but I don't think it'd be very easy to identify which rows have received machine translation. (Our internal spreadsheet has this data and we'll be making templates based off this for community translation)

Hi Maaseb,

No problem at all what you've provided is good as the Output log is included in the crash folder you submitted in the OP.

From what I could tell from the output log the crash is caused by the game attempting to access an invalid memory address to store data. This can happen if the system is running low on active memory, though I wouldn't expect that to be very common on a system with 8GB of RAM.

This could however depend on the state of your PC at the time as well, were you running many other programs or perhaps did you have many different tabs open on your browser at once?

Does the crash occur if you try to duplicate the same situation now?

Cheers,

Lee

Interesting I'll make a note to investigate this further in the coming weeks.

Closing due to lack of customer response.

Bohser's response is fairly comprehensive and makes sense. This has always been a difficult area to balance on aggression radii. This is not a bug but we'd always welcome suggestions via the forum on how you might invision improvements without causing further issues.

Assuming complete due to lack of customer response.

Hi Guys,

Just so you're aware there's a hotfix on the Public Test Branch that might fix this issue. Please can you give it a go and let us know if it works.

Cheers,

Lee