This tutorial works on both 32 and 64 bit of Dolphin!
First you need to modify my Lua script starting at line 67 so that it is correctly adjusted for your Dolphin. In the Lua script are the necessary steps explained to get correct addresses.
After editing the 5 variables (DolphinIs64bit, GameRAMStartAddress, TexturesCreatedAddr, ArrayOfBytesAddress, FrameCounterAddress) you can add RAM Addresses after line 144 by entering
local VariableName = readBytes(AddressOffset+o,NumOfBytes,GiveAsTable)To convert the table to a hex string you can use my function tabletostr(x). So for example you write now:Language: lualocal xpos = readBytes(0x8C6504+o,4,true) local byte1,byte2 = readBytes(0x123456+o,2,false)
For more functions like readBytes in Cheat Engine see here or here Now, you have to add it to the table t like this:Language: luaxpos = tabletostr(xpos)
When you have correctly modified the script you can run it in Cheat Engine by clicking on Table > Show Cheat Table Lua Script. There you have to paste the lua script and press on the Execute script Button.[/i] If you have any questions, please ask =DLanguage: luat = appendstr(t,"xpos: "..xpos) -- or you can do it like this t = appendstr(t,"xpos: "..xpos.." ohman even more to come "..ypos.." you get it")
-- Has to be adjusted: Once every game start local TexturesCreatedAddr = 0x1DAEF6DC
you have to make sure that every single variable is "local", since these variables are faster and work better
I get an "Access Violation" dialog in Cheat Engine sometimes, even when just working with Cheat Engine's address list. Maybe it's the same thing you're experiencing? I'm not at all certain about when it happens, but it seems to happen often after I change my dual-monitor display settings (or disconnect/connect my external monitor from my laptop). It fixes itself if I just close and re-open Cheat Engine.
And once it starts happening, it never stops.
I have no clue why is this.Edit: I've found out, it's because of "graphics > show statistics" check box. Well, how to hide then all these informations ? If I uncheck it, will I still have the informations I'd like to have on screen ?
-- 48 63 D8 48 03 DF 48 83 7D C0 10
-- if you have 64 bit Dolphin
--
-- 83 C4 0C 83 7C 24 1C 10 8D 3C 06
-- if you have 32 bit Dolphin
But again, scanning for these bytes in more recent Dolphin versions turns up nothing. My guess is this part of the Dolphin code has changed since then, and now there may be a different array of bytes we can scan for to make the script work again. But what would that new array of bytes be? What instructions am I looking for here?
(Ignore the bottom right part, that's just my desktop)
Works up to 4.0-2826 now. The Lua script is in this pastebin.
I've set it up so that it's possible to change just one variable, DolphinVersion, in order to get the script working (as long as you have one of the exact Dolphin versions listed there). Otherwise, you will have to look for a few addresses like in Masterjun's original script. For convenience, I plan to add a version that has Wiimote + Nunchuk TAS Input, once RachelB has merged the Nunchuk input code.
Like Masterjun's script, all the addresses under the "function debugger_onBreakpoint()" part are for one game specifically (in this case, Super Mario Galaxy 2). The stuff above that it is applicable to any game. All in all, I made the script quite a bit longer, but that's largely because of the SMG2 stuff and my comments...
