Jump to content

  • Log In with Google      Sign In   
  • Create Account

We're offering banner ads on our site from just $5!

1. Details HERE. 2. GDNet+ Subscriptions HERE. 3. Ad upload HERE.


#ActualSuperVGA

Posted 06 January 2013 - 05:11 AM

Hmm. Never did anything like this myself. Depending on the loaded stuff and the version of the application (defining offset in the heap to where the menu-related stuff is kept),
there's bound to be a byte that changes back and forth when you enter/exit the menu.
Try to grab a dump of the memory allocated for the application in and outside the menu several times to find it,
then look into means of accessing this place from your app.

But I've got no idea whether it would work. Just seems less hackish than looking at loaded textures...

#2SuperVGA

Posted 06 January 2013 - 05:10 AM

Hmm. Never did anything like this myself. Depending on the loaded stuff and the version of the application (defining offset in the heap to where the menu-related stuff is kept),
there's bound to be a byte that changes back and forth when you enter/exit the menu.
Try to grab a fump of the memory allocated for the application in and ousode the menu,
then look into means of accessing this place from your app.

But I've got no idea whether it would work. Just seems less hackish than looking at loaded textures...

#1SuperVGA

Posted 06 January 2013 - 05:06 AM

Hmm. Never did anything like this myself. Depending on the loaded stuff and the version of the application (defining offset),
there's bound to be a byte that changes back and gorth when you enter/exit the menu.
Try to grab a fump of the memory allocated for the application in and ousode the menu,
then look into means of accessing this place from your app.

But I've got no idea whether it would work. Just seems less hackish than looking at loaded textures...

PARTNERS