WiiRD

[sulfur]

I wasn't sure where to post this but I was woundering if anybody else was expirenceing this with WiiRD GUI sometimes it will free like I will click on a different tab at the top but it will not switch to that screen and also sometimes when I click on disassemble tab it will say disasemmble not available?

[GMO]

Occasionally I get where it doesn't switch over to a new tab, I close WiiRd and re-open it and it starts working again, but then again I did lose the search I was working on. Thank god I make it a habit of making notes on a notepad before I do searches especially addresses I working on (Bad Experience in the passed where I lost all my work).

[Romaap]

You could try Gecko dotNET, it doesn't freeze as much as WiiRD GUI.

[sulfur]

I have that to but it is wierd WiiRD will connect to my gecko but when I try to use gecko dotnet it will not connect so I just use WiiRD.

[Link]

Um WiiRd and Gecko dotNET use basically the same code to connect to the Gecko (both codes written by me).. so that indeed should work, they use the same commands.. do you try to open Gecko dotNET while WiiRd is running?

[dcx2]

I've experienced WiiRd locking up if I try to switch tabs immediately too soon after canceling a breakpoint.  I've learned to just be patient because the only button you can click fast is "Next".

WiiRd also crashes the game if I try to apply C2 code types more than once...

[Link]

WiiRd also crashes the game if I try to apply C2 code types more than once...

The C2 thing is a code handler specific problem.. C2 codes create branches and branches are sometimes slow when it comes to updating.. a good idea to make sure a C2 code can be safely applied is when you know the C2 code is currently not executed at all.. a way which should work with very high low crash rate: set an execute breakpoint to 800018A8 (entry point of the code handler, the game should be completely pauses) then apply the codes..

[dcx2]

I think I figured out how to get around the C2-type code crashing after it's already been applied.

1) Set an execute breakpoint; I usually set it on the instruction just before the one that's getting replaced with the branch.
2) Once the game is froze, go to the GCT tab and apply the codes.
3) Go back to Breakpoint tab and hit Step!
4) I usually step through the whole C2 code til it gets back to the game code, but I don't think you need to.
5) Now I can hit "Run" at the bottom.

If I skip step 3, the game will lock up after I hit run.

[hetoan2]

I think I figured out how to get around the C2-type code crashing after it's already been applied.

1) Set an execute breakpoint; I usually set it on the instruction just before the one that's getting replaced with the branch.
2) Once the game is froze, go to the GCT tab and apply the codes.
3) Go back to Breakpoint tab and hit Step!
4) I usually step through the whole C2 code til it gets back to the game code, but I don't think you need to.
5) Now I can hit "Run" at the bottom.

If I skip step 3, the game will lock up after I hit run.

Well isn't that the same thing? The line of code that you're changing has just finished executing so it is safe to change, which will have the same effect as what Link said about the execute BP at 800018A8 because it's not running the code you're changing.

[dcx2]

You can break on the entrance to the code handler but the important part that stops WiiRD from crashing the game from locking up for me is hitting step instead of run.  If I don't hit Step first and run second, the game locks up.