exception code 0xC000005 screenshot attached Crash Dumps file attached good luck and thnx for your help.
So we've just pushed another hotfix for the game. With it we included a new launch option that I'd like for you to try, Paul. Please go into Properties for R3E in your Steam library, and change the launch options to be the following, and then launch the game as usual:
Are you noticing any performance difference, or weird graphical artifacts? Like the experience switcher (at the top) being weird?
yes that's right, The interface is not smooth and there is slight amount of aliasing / tearing when selecting menu options Clicking on menu buttons them are not responsive sometimes have to click a couple of times. Also the experience menus on the top drop down when you move your mouse on to it in a flaky way. But still it all works now.
Also one more thing, I noticed I was in windowed mode in 5760 x 1080 . When I switched to full screen, it is back to Black screen when launched. I cannot even ALT TAB out of it, but I can press CTRL ALT DEL and choose task manager but the whole desktop freezes. I have no option then to reboot PC. When I change the graphics xml file to 'false' for windowed mode and launch game again, then it works ! However, when racing my fps is taking a hit I suspect is because of the windowed mode Can this full screen issue be looked into pls.
Great stuff guys Success! Everything seems to be working fine now - just two minor issues which don't seem to effect gameplay: 1) Although the game now launches ok I still get the steam box message saying: "failed to launch game app already running" .... despite the fact that the game launches ok. 2) the experience switcher at the top is definitely acting weird - and is uncontrolable. Was it the mobile gpu that was the problem?
I asked about this months ago but never got a definitive answer. Let's just say I've been getting this message for quite some time. The game starts ok but it's as if two instances of the game are trying to run when I click launch.
We're not sure yet. We're still trying to find some pattern between all the machines that are having this issue.