I have some ideas for any new wiirdgui vesion, here i go:
- Changing gct code names (New code 1 and so on) and being possible to import .txt (from code manager)
- Fixing screenshots for panoramic TV, coz doesnt works
- Being able to make videos with it!!!(with panoramic support)
- Any way to make the sound mute when paused, to aboid the BIIIIIIIIIIIP!!! sound.
- More wiird commands
Quote from: agrs700 on November 01, 2008, 04:28:53 PM
I have some ideas for any new wiirdgui vesion, here i go:
- Changing gct code names (New code 1 and so on) and being possible to import .txt (from code manager)
- Fixing screenshots for panoramic TV, coz doesnt works
- Being able to make videos with it!!!(with panoramic support)
- Any way to make the sound mute when paused, to aboid the BIIIIIIIIIIIP!!! sound.
- More wiird commands
How would videos work? I haven't messed with WiiRD's screenshot feature, but seeing as the USB Gecko is the same speed as the GameCube BBA, and seeing as GCNrd took much more than 16ms to dump a screenshot, trying to take videos using the screenshot feature would almost certainly slow down the game, probably making it unplayable.
Videos would be impossible without EXTREME slowdowns, you would probably get >5fps doing this.
What kind of wiird commands? Maybe you should elaborate.
You can already change gct code names....
QuoteYou can already change gct code names....
Rly?? how?
Quote from: agrs700 on November 01, 2008, 07:21:44 PM
QuoteYou can already change gct code names....
Rly?? how?
simply clicking on them.. they should be renamable like files in Windows Explorer by clicking on their file names.
For videos: no probably not, sorry.. even if we optimized the screenshot feature.. by just sending over the necessary YV data (meaning 614400 Bytes per Screenshot).. we have a about 1.5 MB/s - so it's 2.5 FPS... not feasable.. really :(
For widescreen: you can select "Resize screenshot".. by default WiiRd takes the native Wii image.. which is always 4:3 ..
the beep sound is unfortunately not directly a WiiRd fault.. it's caused by pausing the game..
however: more commands.. sure? like what?
Maybe it's possible to make some quick JPEG compression routine on the Wii side, so you could compress each frame to 32KB, and take only the odd frames, making a 640x480 30fps video. That way you can fit it into the 1.5MB/s bandwidth.
The video quality will sure go down, but the possibility to take videos using usbgecko would be great anyway.
I think I will make a short video with that compression settings to see if the quality is still acceptable... But I think it will be pretty acceptable, with some JPEG artifact noise but good anyways..
Link, could you make it so wiird mutes the wii when you do a dump or have a breakpoint?
If its possible, make it be able to be toggled. Some games like super paper mario dont have the beep, the music is nice.
Quote from: sarkwalvein on November 01, 2008, 09:42:54 PM
Maybe it's possible to make some quick JPEG compression routine on the Wii side, so you could compress each frame to 32KB, and take only the odd frames, making a 640x480 30fps video. That way you can fit it into the 1.5MB/s bandwidth.
The video quality will sure go down, but the possibility to take videos using usbgecko would be great anyway.
I think I will make a short video with that compression settings to see if the quality is still acceptable... But I think it will be pretty acceptable, with some JPEG artifact noise but good anyways..
If you could make a fast JPEG compression function fit in the Wii's RAM without interfering with the game's RAM usage, that would work. But I'm guessing that isn't possible; the WiiRD code handler only uses 4KiB or so, and I would guess that many games don't leave much more than that available.
How much of the wiis ram could we use without seeing major slowdowns?
Quote from: Igglyboo on November 01, 2008, 09:51:06 PM
Link, could you make it so wiird mutes the wii when you do a dump or have a breakpoint?
If its possible, make it be able to be toggled. Some games like super paper mario dont have the beep, the music is nice.
I wouldn't be surprised if this could be done by poking a sound register or something like that. Or it could be impossible. But if it's possible, I would like it to be optional, rather than doing it all the time. I find the beeping noise to be a useful nonvisual indicator that the dump is done, so that I don't have to pay thorough attention. Yes, I'm probably the only one.
Quote from: IgglybooHow much of the wiis ram could we use without seeing major slowdowns?
I don't know much about Wii games' RAM usage. On the GameCube, the standard amount of reliable free RAM was 32KiB. I recall that Link said that it was much less on the Wii. But if we use too much RAM, the problem won't be slowdown, it will just crash the game at random times depending on what the memory allocation routines of the game are doing.
Wait wait wait.. the Gamecube used 32 KiB.. however, technically it didn't have them.. there are games which tend to crash with GCNrd.. like Starfox Adventures PAL.. try Star Fox Adventure Gamecbe in WiiRd.. WiiRd is running completely in the head ram.. and we do not really want to put it out of that.. because it's fast and safe that way.. on the GC.. there were GC games where the FST interfeered with GCNrd.. many games required special master codes.. ths is simply because GCNrd is sharing memory with the game.. WiiRd technically isn't .. WiiRd runs completely off the head memory..
So if we increased the ram usage, it would overflow and use more than the head memory?
Couldnt we just make a master code then?
a master code could not really solve it..
the main problem was: GCNrd uses: 817F8000 to 81800000 and marks that memory as unusable.. many games obey that.. however there are games with hardcoded addresses.. like Starfox Adventures.. you have would have to reprogram entire memory to tell the game not to use it.. other games use that memory for their FST.. that's also hardcoded and very very hard to relocate.. and therefore we were quite happy that WiiRd is running at 80001800 until 80003100 (including codes) and therefore at least that problem does not exist..
would turning off the code handler while recording allocate any more memory?
that might theoretically work but it will be complicated.. as the code handler is inside the USB Gecko communication part (meaning even Ocarina communicates with the USB Gecko as we were lazy).. though I doubt we could add JPEG compression for something like MJPEG compression to the handler.. and then in the end.. if wouldn't fix audio issues:
-what if games use Direct Audio? Then we'd have to capture the audio while it's being sent to the hardware.. otherwise we'd record BEEEEEEEEEEEEEEEEEEEEEEP..
-what if games use streamed audio? then the music would just continue playing .. and it would go completely off-sync
Quote from: Link on November 01, 2008, 10:07:28 PM
Wait wait wait.. the Gamecube used 32 KiB.. however, technically it didn't have them.. there are games which tend to crash with GCNrd.. like Starfox Adventures PAL.. try Star Fox Adventure Gamecbe in WiiRd.. WiiRd is running completely in the head ram.. and we do not really want to put it out of that.. because it's fast and safe that way.. on the GC.. there were GC games where the FST interfeered with GCNrd.. many games required special master codes.. ths is simply because GCNrd is sharing memory with the game.. WiiRd technically isn't .. WiiRd runs completely off the head memory..
Okay, thanks for clearing that up. I knew that GCNrd crashed certain games, but I wasn't aware of the architectural difference that prevents that with WiiRD. Learn something new every day.... :)
And yeah, personally, I think buying a $50 USB video capture card is a better solution than trying to fit an MJPEG encoder into a 4KiB piece of RAM along with the existing hook code. Doing it over USB Gecko would be cool, but just too hard. (But that's just my opinion; feel free to form your own!) :)
How about support for the VPU's, there are several games that I've encountered routines like the following that I've been unable to continue a trace due to the lack of support on them.
80215074: E0430000 .word 0xe0430000
80215078: E0840000 .word 0xe0840000
8021507C: 10C2202A vsel v6,v2,v4,v0
80215080: F0C50000 .word 0xf0c50000
80215084: E0638008 .word 0xe0638008
80215088: E0A48008 .word 0xe0a48008
8021508C: 10E3282A vsel v7,v3,v5,v0
80215090: F0E58008 .word 0xf0e58008
80215094: 4E800020 blr
Please update to the newest WiiRd.. the Gekko instructions have been added by me which was a pain in the ass..
in your case the instructions would be:
80215074: E0430000 psq_l f2,0(r3),0,0
80215078: E0840000 psq_l f4,0(r4),0,0
8021507C: 10C2202A ps_add f6,f2,f4
80215080: F0C50000 psq_st f6,0(r5),0,0
80215084: E0638008 psq_l f3,8(r3),1,0
80215088: E0A48008 psq_l f5,8(r4),1,0
8021508C: 10E3282A ps_add f7,f3,f5
80215090: F0E58008 psq_st f7,8(r5),1,0
the vsel command is wrong, we figured, the Gekko CPU does not know it!
Awesome work man, much appreciated!
Something you could add on Wiird, IMHO:
-Audio Capture.
-A kind of real-time Debug on GCT Codes section. Ex.: 48010000 80854033 Given address: 90112200.
-An 'AND' option on search tab. Ex.: Search for 0x34230000 AND 0x12340012 on next word. (kind of 64 bits search).
-A breakpoint 'STEP' function/button on Memory Viewer.
-A textBox to insert raw hexadecimal code on disassembler or something that convert raw hexadecimal code to PPC instructions.
-A textBox on Poke section showing current poked address value or Put another Poke function on Memory Viewer.
Wiird is an awesome application!
Making Videos (good idea)
Quote from: Ninja on January 19, 2009, 07:27:58 PM
Making Videos (good idea)
good idea, but (almost) not possible.
you noticed the lag in memory viewer? it will be even laggier :o
-lagless memory viewer
-can use GCT files to activate cheats.
Quote from: jassim on January 19, 2009, 08:46:34 PM
-lagless memory viewer
-can use GCT files to activate cheats.
lagless memory viewer = not possible
Videos should be animated gifs/gif compatible image dumps.
its a pain converting them
also i think GCT could be done but i haven't looked into the file type actually
sending gct via WiiRD would only need a GUI implementation of sendcheats.
Also, pressing Next on the memory viewer window should automatically update the display.
Could you change wiirdgui to a standard windows form app? The GUI it has really annoys me and it ALWAYS stays on top, i have to keep clicking that minimize GUI button. Also, it seems buggy and locks up randomly when doing searches to fast or using breakpoints, idk if thats the GUI or not.
Yea regular minimize with a button for staying on top instead :D
-Would it be possible to view textures in FST? I don't think so but maybe.
-Search GCT codes. I have over 50 codes for some games, its annoying to look by hand
-Functions in WiiRD console. Sometimes WiiRD messes up when I bring up WiiRD Console and GUI. Like /dump file.bin etc
-Time search- search for timers
-Text search- convert text into hex and search
I'm toying with video capture. Might be possible if send to SD
More stability, so less freezes
Delete Line Of code function.
copy entire code.
Suggestions/bug fixes:
1#.
In the memory viewer, you're able to double click on a MEM1 address and it'll take you to the MEM1 address, this doesn't work for MEM2 addresses.
2#.
When adding MEM2 addresses to the viewer from the code search result window, it doesn't update the viewer MEM# base box, it'll stay on MEM1.
This is an inconvenience because if you then attempt to scroll down, the viewer will jump to the MEM1 area instead of MEM2.
This also affects the text search.
3#.
After adding an instruction via the Assembler, could we have the next instruction line selected automatically, just like Ollydbg.
In fact if you have OllyDBG then pretty much any option it has that WiiRD is missing would be a great addition.
Also, could we have a separate float converter button or add the "paste" option when right clicking the 'search value' box.
Quote from: TNTkryzt on January 24, 2009, 04:36:19 PM
Suggestions/bug fixes:
1#.
In the memory viewer, you're able to double click on a MEM1 address and it'll take you to the MEM1 address, this doesn't work for MEM2 addresses.
2#.
When adding MEM2 addresses to the viewer from the code search result window, it doesn't update the viewer MEM# base box, it'll stay on MEM1.
This is an inconvenience because if you then attempt to scroll down, the viewer will jump to the MEM1 area instead of MEM2.
This also affects the text search.
3#.
After adding an instruction via the Assembler, could we have the next instruction line selected automatically, just like Ollydbg.
In fact if you have OllyDBG then pretty much any option it has that WiiRD is missing would be a great addition.
Also, could we have a separate float converter button or add the "paste" option when right clicking the 'search value' box.
Hi TNTkryzt, you probably know this, but you can still use ctrl+v keyboard shortcut
However, a right click option would be nice :]
being able to press play/pause/next while in the memory viewer
Quote from: REDSOXROX on January 24, 2009, 06:26:45 PM
Hi TNTkryzt, you probably know this, but you can still use ctrl+v keyboard shortcut
However, a right click option would be nice :]
Yeah I know, I'm just lazy.. :p it's a hassle to have to change to keyboard shortcuts when the app is mostly mouse orientated.
jassim don't post what other people said in the same thread -.-
@TNTkryzt I like to lean on one of my arms and keep the other on the mouse so I can relate...
I'd also like to see a regular sized Taskbar and stuff. It's kindof annoying having it with the little small x and bar at the top and HUGE buttons on the inside.
Also a sexier interface would be nice :D
more colors and pictures in background of geckos or something... i don't know...
Actually, PUT A HYPNOTOAD!
ALL GLORY TO THE HYPNOTOAD!
Quote from: hetoan2 on January 26, 2009, 02:55:35 AM
jassim don't post what other people said in the same thread -.-
@TNTkryzt I like to lean on one of my arms and keep the other on the mouse so I can relate...
I'd also like to see a regular sized Taskbar and stuff. It's kindof annoying having it with the little small x and bar at the top and HUGE buttons on the inside.
Also a sexier interface would be nice :D
more colors and pictures in background of geckos or something... i don't know...
Actually, PUT A HYPNOTOAD!
ALL GLORY TO THE HYPNOTOAD!
The Pirate Song as backround music ^^
he can't, it's copyrighted.
along with hypnotoad :|
he would have wanted it this way :(
-Ability to re-order code searches (e.g highest values on top)
-auto convert dec-hex upon clicking start search (option to turn that off and on)
-can switch tabs even when usbgecko isnt connected, why?because sometimes my game jams and i wanna go to the code search tab to save my search.
Quote from: Jassim on January 31, 2009, 07:55:26 PM
-Ability to re-order code searches (e.g highest values on top)
i'm told that this is not possible.
its not possible because he is not loading the search into ram
Custom Backrounds to go with Gecko 2.0 ^.^
Definately being able to import codes into the gct tab from a .txt or .gct file would be very useful. Either that or being able to convert a GCT/TXT file into a wgc file that you can just paste into /codes and load.
To make it easier for people like me just getting started. Would it be possible to make it so that once you have found an address and you poke the address with a value it and it does show a change? Make it so that when you export a code that it already makes the code according to what method was used to search for the code and according to the location where the code was found?
For example instead of just exporting the base address 8xxxxxxx or 81xxxxxx, make it so that it automatically changes the first two characters for you to what the code should be?
I know this is for newbs like me but in other programs I have used in the past to cheat on windows games and in emulators. Basically once you have found a code basically that is the address and all you do is change a value or freeze it and that is your code for use within the program. That just seems so much easier for finding codes, I do find that having to look up the table to find out what my code should look like seems a little complicated. I have only had the USBGecko for 1 day and I spent hours trying to find some codes and well now I have read a lot about what the different codes should look like I kind of understand why some codes start with 04 and some with 00 and some with 02 etc... But if the program would do this for you it would be much user friendly.
I understand that this would not be possible with all codes but it would help. I have yet to make a working code that has a O.P and I guess that's why some infinite energy codes where not working for me because I need a O.P to work with the code. I wish there were more video tutorials out there with different games, other than Mario Galaxy. Some for Wiiware games would be nice.
Real-time memory watch in the "search" tab. It'd be nice when you have less than ten results instead of having to do another search.
Though you should have to put an upper limit to how many adresses to watch. 5243 results might slow the game down a bit. :rolleyes:
Quote from: HaXXeR on June 19, 2009, 12:29:33 PM
Real-time memory watch in the "search" tab. It'd be nice when you have less than ten results instead of having to do another search.
Though you should have to put an upper limit to how many adresses to watch. 5243 results might slow the game down a bit. :rolleyes:
That's actually a great idea. I was using Tsearch to find cheats for some PC games and I noticed that it has that and you can see what changed easy when you have few results.
Agreed, that would be a nice feature to have.
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...
Quote from: hetoan2 on June 20, 2009, 05:42:46 PM
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!
Any chances to see 64 bit floating point registers and FPSCR on WiiRD?
I would like to see an option on the main menu to launch the last channel that we launched. :)
Thank you!
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.
Quote from: hetoan2 on June 20, 2009, 05:42:46 PM
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.
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
A screen grabber for homebrew applications (if it is not possible yet)
-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.
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.
Would really like to have a MEMORY EDITOR instead of a memory viewer >:D
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 ..
Quote from: giantpune on September 30, 2009, 02:45:23 AM
-resizable window so you can fill up the whole screen if you want
I agree If it could be added, it would be appreciated :)
You guys should move requests over to this thread (http://wiird.l0nk.org/forum/index.php/topic,4954.msg45144.html#new) 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:
Quote from: [sheep] on August 06, 2009, 02:15:54 PM
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.
GeDoN sounds cooler than GDN in my opinion...
:)
Yeah, GDN doesn't seem as cool, but it's hard to type "Gecko dotNET" three or four times. :) Too many geckos, what is this a Geico commercial? Gecko OS, USB Gecko, Gecko dotNET.
Maybe G.NET? Or Gecko.NET? I think the thing I don't like is the word "dot"...interferes with the flow too much. But it's not my call to make, since the app is 99.9% Link's work.
The max speed on usb is 1.5mb's right so video over that is imposible but what about over PATA? pata to sata is cheap and small nowdays and should be easy to mod, (for me) the PATA speeds are something like 16-33-66-100-133MB/s unless they limited the bus speed on the Mainboard (or even PATA to USB), would it work as a better connection to the PC if you could?
Though you would need one with a passthrough PATA back to the DVD drive with a switch (if you can get them) for people who use the drive...all for getting video streamed onto the PC of coarse...oh and playing backed up games in places that its still legal
Also one idea is making the memory dumping faster by using select memory ranges for that game for that level but that would require an online database or something connected to the client and people would probably have to upload their dumps unless you can get the client side to do 'IT' properly. Now 'IT' would be if you had 100 levels in a game and the "level 1" data is in the exact same place every time if the client software could scan that data (hacking it so all "stats/items etc remain the same"), upload it and compare it to all the other level dumps (getting rid of the changed data that is grouped together) it can in theory be eliminated from the search saving lots of time (possibly hours for many people), not to mention the junk memory with nothing in it.
Now in theory it's not always like that but after lots of practical use it seems to be like that (but I could be wrong) but even if it did work for only 20% of games becuase they are layed out as they are in the 100 level's example it would still save many hours for many people for 20% of games that exist, worst case is you can just do the inversion of everything that changes as the ranges to scan.
I don't have as much experience as some of you guys so these may be really stupid ideas that you've heard lots of times before but anyways...tell me whats what...thanks
its been said many times that the bottleneck for the usb gecko speed isnt the usb port or drivers. it is the speed of the gamecube memory card port. the fastest ive seen with it is 660kBs but only with one app. it could be faster than that, but not enough for any sort of video other than still images.