I doubt Deadbolt is limiting CE's potiential as I'm able to use windows debugger on it without any issue. Same issue still happened with page exceptions. Possibilities are the game might be blocking ce to be full functional, some how by registry keys, or by another executable that launches within the game. (chances are low, but its better than nothing) This is something that has previously worked and now isnt for some reason.Ĭheck your debugging settings and change hardware break-point to page-exceptions. I need VEH debugger for what I'm attempting to do in dark souls as the windows debugger causes a regular "Dark Souls III had stopped responding" crash.Įven with a fresh install and an updated windows 10 this issue still happens. I had the debugger working on Dark Souls 3 previously so I'm not too sure why it wont work now and why it effects Steam games so drastically. I then tried it with the non steam version of Getting Over It and as expected the game crashed but the exe was still intact. I tried the same thing with the game Deadbolt and the game crashed with the same "Access is Denied" issue and the missing executable. exe for the game has been nuked and I have to reboot before steam can validate files. So im messing around with cheat engine and dark souls 3 and I try attaching the debugger through "Find what accesses this address" on the memory viewer.īut the moment I click that cheat engine and the game both instantly crash with no error messages and it turns out the.
Posted: Sun 3:53 pm Post subject: VEH Debugger issue.
0 kommentar(er)
