View previous topic :: View next topic |
Author |
Message |
SwaggaJackin' Master Cheater
Reputation: 2
Joined: 06 Nov 2009 Posts: 304
|
Posted: Mon Apr 09, 2012 10:45 am Post subject: Serious Sam 3, debugger not working? |
|
|
I'm sure this is some sort of protection but not sure what kind it is. I was trying to find the pointers for life and armor but when checking what accesses/writes to the addresses gives out nothing. This was with using the VEH debugger.
Any ideas?
|
|
Back to top |
|
 |
Kavvman Master Cheater
Reputation: 2
Joined: 17 Apr 2004 Posts: 316
|
Posted: Mon Apr 09, 2012 11:13 am Post subject: |
|
|
I haven't fiddled with the game but i do know it uses steam CEG also a region locked game. So its definitely the protection.
A no-cd fix should take care of it.
_________________
... |
|
Back to top |
|
 |
SwaggaJackin' Master Cheater
Reputation: 2
Joined: 06 Nov 2009 Posts: 304
|
Posted: Mon Apr 09, 2012 12:02 pm Post subject: |
|
|
I'd rather not go that route. I'm more curious what is causing it and how to bypass it for future reference rather than just getting it to work.
|
|
Back to top |
|
 |
Dark Byte Site Admin
Reputation: 470
Joined: 09 May 2003 Posts: 25785 Location: The netherlands
|
Posted: Mon Apr 09, 2012 1:37 pm Post subject: |
|
|
if using the beta and not ce 6.1 then go to settings->debugger and tick "Override existing breakpoints"
the game might crash though
_________________
Do not ask me about online cheats. I don't know any and wont help finding them.
Like my help? Join me on Patreon so i can keep helping |
|
Back to top |
|
 |
SwaggaJackin' Master Cheater
Reputation: 2
Joined: 06 Nov 2009 Posts: 304
|
Posted: Mon Apr 09, 2012 2:27 pm Post subject: |
|
|
Game crashed. I also tried using software breakpoints but nothing showed up. However I did get the instruction right before the crash. So the game is creating it's own breakpoints to check for something? What's causing this?
|
|
Back to top |
|
 |
Dark Byte Site Admin
Reputation: 470
Joined: 09 May 2003 Posts: 25785 Location: The netherlands
|
Posted: Mon Apr 09, 2012 2:37 pm Post subject: |
|
|
Some protections do this. Fill up all hardware breakpoints and make it point to a routine that will crash when executed. When that routine is then called the breakpoint handler changes eip to a function that does not cause a crash
_________________
Do not ask me about online cheats. I don't know any and wont help finding them.
Like my help? Join me on Patreon so i can keep helping |
|
Back to top |
|
 |
SwaggaJackin' Master Cheater
Reputation: 2
Joined: 06 Nov 2009 Posts: 304
|
Posted: Mon Apr 09, 2012 3:19 pm Post subject: |
|
|
What's the best way to "catch the crash" before it executes so I know what function is doing it so I can reroute it?
|
|
Back to top |
|
 |
Dark Byte Site Admin
Reputation: 470
Joined: 09 May 2003 Posts: 25785 Location: The netherlands
|
Posted: Mon Apr 09, 2012 4:42 pm Post subject: |
|
|
no idea, try looking at the debug registers and find out how they are set. If it's an execute bp, set a software breakpoint in front of it,. Perhaps single stepping will follow it
_________________
Do not ask me about online cheats. I don't know any and wont help finding them.
Like my help? Join me on Patreon so i can keep helping |
|
Back to top |
|
 |
Dark Byte Site Admin
Reputation: 470
Joined: 09 May 2003 Posts: 25785 Location: The netherlands
|
Posted: Tue Apr 10, 2012 8:56 am Post subject: |
|
|
And if it is an onAccess or onWrite breakpoint you can check that using the veh debugger and the debug event list (without setting any breakpoint) . Rightclick the debugevent that says a breakpoint triggered and get the state
_________________
Do not ask me about online cheats. I don't know any and wont help finding them.
Like my help? Join me on Patreon so i can keep helping |
|
Back to top |
|
 |
|