Windows 8.1 64 bit, 8 Gm RAM, Intel(R) Core(TM) I7-4500 CPU1.80 GHz 2.40
GHz GPU: AMD Radeon R7 M265, Intel(R) HD Graphics Family. Version game 1.4.1
I went back to version 1.4.1, since 1.4.2. game crashes when entering map edit.The game crash (during the game) on the big map, there were a lot of creatures and traps.
War for the Overworld Launcher Log.txt
I don't understand this phrase "AmdLiquidVrD3D11WrapDeviceContext" do you even use LiquidVR ?" No virtual reality I have not used, I have no such devices. LiquidVR is also not set, and the first time it is read you.
I checked again - no, fresh drivers, the device Manager does not offer other. And sorry, I forgot to fix the copied text about my laptop. Now I have windows 10.
I went back to version 1.4.2
And I edited it in version 1.4.1., because in version 1.4.2. can't log in to edit the map. A vicious circle.
War for the Overworld Launcher Log.txt
Liquid VR is software/a drive related to AMD (it is not virtual reality software itself, but is AMD's drivers to make VR devices work with their cards), what Stefan is saying is that this appears to be an issue with your system's drivers and he is suggesting you check if there are any software updates for those drivers since this doesn't appear to be an issue on WFTO's end.
Liquid VR is software/a drive related to AMD (it is not virtual reality software itself, but is AMD's drivers to make VR devices work with their cards), what Stefan is saying is that this appears to be an issue with your system's drivers and he is suggesting you check if there are any software updates for those drivers since this doesn't appear to be an issue on WFTO's end.
Liquid VR is software/a drive related to AMD (it is not virtual reality software itself, but is AMD's drivers to make VR devices work with their cards), what Stefan is saying is that this appears to be an issue with your system's drivers and he is suggesting you check if there are any software updates for those drivers since this doesn't appear to be an issue on WFTO's end.
Accepting for further investigation by code.
The problem is that the graphics driver is crashing for an unkown reason.
The attached crash logs show a stack trace which only contains AMD graphics driver related code.
So it seems to be an issue with the AMD driver it self, not even Unity or WFTO.
When searching the web for the drivers involved in the crash, I find similar issues of other people having similar crashes in other games (including Witcher 3, Farcry 3, Batman Arkham Knight and even World of Warcraft).
See some fellows:
(which can be found by searching one of the items in stack trace eg "AmdLiquidVrD3D11WrapDeviceContext" or "AmdDxGsaFreeCompiledShader")
https://community.amd.com/thread/196520
https://community.amd.com/thread/200731
http://steamcommunity.com/app/265550/discussions/0/613935404114338338/
https://steamcommunity.com/app/292030/discussions/0/613958868368558837/
http://us.battle.net/forums/en/wow/topic/18300092113
https://forums.wildstar-online.com/forums/index.php?/topic/128360-cant-launch-the-game/
On a quick look, none of them got a decent answer and thus I don't know how to help.
It looks like it's either an issue with newest AMD drivers or a system specific issue with your configuration.
There is no pointer that it would be related to the War for the Overworld code.
If anyone has found a solution to this problem, please leave us a message here.
Cheers
The crash stack trace contains only system internal stuff and not anything which would relate to War for the Overworld:
0x00007FFC9AD48316 (atidxx64) AmdDxGsaFreeCompiledShader
0x00007FFCC1D48102 (KERNEL32) BaseThreadInitThunk
We got some known issues with Unity crashes in the version we used to build most recent patch.
However this one looks different and if you look at above dlls causing the issue,
you see AMD specific drivers involved, which suggests an issue with your graphics drivers which obviously did crash.
"AmdLiquidVrD3D11WrapDeviceContext" do you even use LiquidVR ?
You might want to check if your graphics card settings are correct and maybe try to reinstall/update the drivers.
Cheers