Ideas for new Wiird

[James0x57]

Agreed, that would be a nice feature to have.

[hetoan2]

A way to right click on search results and mark them or remove them would be nice. Marking to remember something about it :|

Also, how do you get out of breakpoint hit mode? WiiRD will randomly send me into it sometimes...

[Link]

A way to right click on search results and mark them or remove them would be nice. Marking to remember something about it :|

Also, how do you get out of breakpoint hit mode? WiiRD will randomly send me into it sometimes...

WiiRd does not do it basically, there is a breakpoint cancel command in the Gecko code.. sometimes they cancel command however does not seem to be properly recognized. If it is not: then a breakpoint you activated ages ago might be still active and will hit while you already do other stuff!

[mdmwii]

Any chances to see 64 bit floating point registers and FPSCR on WiiRD?

[James0x57]

I would like to see an option on the main menu to launch the last channel that we launched. :)
Thank you!

[paynless]

didnt manage to read all 4 pages so forgive me if these have been mentioned.. btw.. let me take this opportunity to say how amazing the current versions are.. and thanks for all your hard work..

1.. bigger interface for the debugger.. perhaps integrating the DISASSEMBLER and the BREAKPOINT screens together.. it seems a little harder to trace through code when u can only see a few lines at a time..
2.. a feature that lets u RUN to the next RET or BLR in the ppc instruction set.. so that you can see what function called what code.. etc.. helps to trace back through lots of code without having to wade through (and possibly missing returns)

i havent been using it long.. but these are the only 2 things i can come up with from a purely REVERSING stand point..

cant wait to see future versions.. good luck guys.. hope this helps to give some direction.

[REDSOXROX]

A way to right click on search results and mark them or remove them would be nice. Marking to remember something about it :|

Also, how do you get out of breakpoint hit mode? WiiRD will randomly send me into it sometimes...

I was working on a code  where that would be useful.

Also while I was working on the same code, I thought of a function that would be extremely useful.
An option in the code search to remove address values that changed since the last search.

[[sheep]]

hope this thread is still being read by the creators of wiird :)

ok.. a few things now ive used wiird for a little while..

hope these havent already been covered..

1.. Some kind of save/state.. not for the game.. but for the wiird interface.. its annoying when u crash the game and
have to keep typing in the SAME addresses because wiird resets.. a nice save state that worked once u had crashed the game would be nice so when u reloaded u could be back at the addresses u were before..
2.. make the LIST of excluded breakpoints exportable.. or copyable.. i dont actually use it to EXCLUDE that much.. what i do use it for is to list every address that DOES access my code or data.. then i have to write them all down :(
3.. (this ive actually coded myself to help me with wiird) but would be great if u could add it.. my tool saves breakpoints from wiird and stores them
in a list.. so ALL breakpoints ive used i can scroll through.. and put them back into the breakpoint window.. so basically a HISTORY of breakpoints would be cool..
4.. when an update doesnt TAKE.. ie.. if u dont pause the game first.. and u just UPDATE.. it rarely writes.. or.. if u update and the instruction is incorrect.. it then fills the box BACK with the original instruction.. can this be a choice?? cus its very annoying typing out the instruction again..
also.. a side note to this.. when u have an incorrect syntax for the code u enter.. and it displays a little message box with the correct one.. instead.. can u either show and THEN insert the correct one.. or.. at least put the correct syntax in the edit box..
5.. keep all readouts in HEX.. or at least give a choice.. having half the program work in hex and the other in decimal is very hard to work with.. ie.
in the code u see stw r0,3434(r6) to get to that address u have to first convert it to hex then goto the memory address and dump it +hex value..
6.. i guess its just what i asked for last time but will keep it current :) the window for debugging is very small.. its hard to get a gauge on what the surrounding code looks like.. can this be much bigger.. or resizable?? something like olly would be pretty amazing :)

neways.. i hope these dont sound too arrogant or casting bad points on the current software.. because its not.. the current program is amazing.. no doubt about it.. great work indeed.. but as this is a wish list :) i thought i would put mine down.. tnx

[Ruffy]

A screen grabber for homebrew applications (if it is not possible yet)

[giantpune]

-Ratio buttons by the search to select hex/dec/char
-resizable window so you can fill up the whole screen if you want
-BUGFIX when you have a list of search results, right click one->poke.  but you can't right click the next search result.  you have to left click->right click->poke
-i would like the ability to have the program open and click around without being connected to the game.  then just click a button to mount the game.
-remember my settings.  if i have the program open with wiird console showing, 16bit search selected in 0x90000000, then i would like to close the program and open it and all these are the same settings.

[Trekkie]

Well, in my Opinion, the Best choice to make Videos of Homebrew-Applications, and working Games running with Codes, would be using a TV-Grabber with your PC/Laptop.
That would also keep you safe from extreme slowdowns.

[gameshark]

Would really like to have a MEMORY EDITOR instead of a memory viewer >:D

[Skiller]

Add MemoryEditor. but still keep the Memoryviewer but alow Multi Memview Windows .. (Expandable) -- Note: a new window would open for u to compare the last one to. At the same size u expanded the Memory editor to ..

[Thomas83Lin]

-resizable window so you can fill up the whole screen if you want

I agree If it could be added, it would be appreciated  :)

[dcx2]

You guys should move requests over to this thread of Gecko dotNET requests.  I tried to grab all the interesting things from this thread already.

GDN is being actively developed right now.  The current build is pretty stable...I've been using it instead of WiiRDGUI for about two weeks.  Some of the requests in this thread are even already implemented, though there's more to come.

For instance, the current build's Memory Viewer has a poke box, so it's more like a memory editor.

Also, the next build Link releases should be resizeable!  <--- first of many contributions to GDN  ;D

So yeah, head on over there, grab the latest build, play with it, make requests, and tell others to do the same!

EDIT:

5.. keep all readouts in HEX.. or at least give a choice.. having half the program work in hex and the other in decimal is very hard to work with.. ie.
in the code u see stw r0,3434(r6) to get to that address u have to first convert it to hex then goto the memory address and dump it +hex value..

If you look at the machine code for the instruction in the disassembly window, the lower 16 bits are the immediate value in hex.  For your example, stw r0,3434(r6)...while I'm not sure what the high 16 bits would be for stw r0,r6, I do know that the 3434 makes the lower 16-bits 0D6A.