duzenko, on 06 Feb 2019 - 3:26 PM, said:
Did you try other graphics drivers?
Yes, I have the latest drivers. I tried to force install newer drivers and even Bikerdude tried to help make a hack to let Windows install it but they don't work on this laptop. Which we tried on another issue in this thread: http://forums.thedar...-to-menu-solved
stgatilov, on 06 Feb 2019 - 2:38 PM, said:
You said that 32-bit and 64-bit versions behave differently: one of them exits itself.
Does it look like a crash in this case?
What are the contents of qconsole.log in the case when TDM exits itself?
If there is a crash, please record crashdump and share it.
The difference in behavior for the two version is that the 64-bit version does not even show the TDM mouse and it crashes without having this screen with "TDM is not answering would you like to close the app or wait for it?" , what would you like to do, and after that it is logical to close it and "it sends information to Microsoft" and then it closes itself. But both versions do not launch the game and they have a black screen. The 32 bit version has a mouse on a black screen and it is freezed with the situations that Windows proposes to "wait for the app of close it". I made a condump off of this moment because when it sends information to Windows when I choose to close it the app closes too fast to make a condump file. Clicking around leads to the game "not answering". Which brings the necessity to close it because it won't work after this anyway.
So, here's the condump off of the 32 bit version link - https://1drv.ms/u/s!...lH-BzTMHk8AT8yA
I will work to see If there are any changes in troubleshooting with gsconsole.log tomorrow when I come back!