Debugger not activating.

[retroben]

On 5.0-2991 master,the debugger won't appear after doing the procedure on a shortcut and adding /d after the exe part.

I have an older PR build (5.0-416 dirty) that works fine with this method of enabling the debugger tools.


If there is a new method to enable them,how do I activate the debugger now?
I need it in order to,well,debug why a code is failing to work in newer builds where it works on the older one I have.

Maybe the cheats are not being enabled quick enough and being left in the dust from how Recompiler refuses to update from changes to ASM memory.
The issue occurs in Pokemon Snap with the 60fps codes I recently posted because the "Forced 60fps" code requires being written early enough to be executed correctly,otherwise the changed bytes get ignored.

Codes as dword parches "OnFrame" are...

Max fps
011DD338 00010001

and

Forced 60fps
0119A800 25F80002
The ASM altering code that only seems to have fully worked on the older Dolphin build,or both codes are failing on the newer builds for whatever reason.

Please help me figure out how to enable the debugger on newer builds.

[gamemasterplc]

I just use Dolphin 5.0-583. The forced 60FPS code is a MIPS ASM code and the code may not be writing to memory before the instruction executes.

[retroben]

Well,I actually found out the first code isn't writing according to cheat search's results having my address with 00010002 as the value,which is 30fps at Professor Oak.
Thought the forced cheat normally makes it hit 60fps there anyway on its own,at least with PJ64 before I ported it over to Dolphin.

Cheats appear to be broken (again) currently,at least the patch section is failing to update it.

The title screen is still hitting 60fps ranges via 1:1 on an OC of 295% as guided by my friend.

Ahh,the Action Replay code creation then apply actually made the address work for the first code,so patches are busted currently.

[JosJuice]

(03-20-2017, 12:45 PM)retroben Wrote: On 5.0-2991 master,the debugger won't appear after doing the procedure on a shortcut and adding /d after the exe part.

I have an older PR build (5.0-416 dirty) that works fine with this method of enabling the debugger tools.

Huh, you're right... Using /d doesn't work, but using -d does work. I guess some developer who was using Linux wasn't thinking about Windows when making changes to the command-line parsing.

EDIT: Bisected to https://github.com/dolphin-emu/dolphin/pull/4916

[retroben]

Patch codes are an issue I think should be fixed pretty soon,primarily for the manual version of TP Hyrule Speedhack or in general for other interesting patches.

Good to know the debug flag was changed,but at least I still salvaged what was going wrong for the 60fps code (only needs the original code I found to be ported and the 295% OC) thanks to cheat search working in my favor with low result counts showing my ported address in the list with its unchanged value despite the enabled patch for that address which works on an older Dolphin build but now has been proved to fail on newer versions for some odd reason.
And the byte affected doesn't force an auto-change back to 02,it only changes on each menu/area load then can be changed to the value one desires,like 03 for 20fps on low-end PCs or most non-beastly laptops or the essential 01 for the real-time 60fps code.

[retroben]

Bumping because the latest build 5.0-3255 still has patch codes NOT working,ergo no Twilight Princess Speedhack access unless I look into the ini and re-create it as a new Action Replay code.
Shouldn't have to do that,but still find this issue infuriating when wanting to test things in patch code form even though the AR section can be utilized in real-time.
Its just that patch codes,when they were functional,they are (they were) more reliable at game boot and with consistency for simple value writing to addresses.