I received several messages from people asking me to finish this project. Sorry to say, I cannot. It’s not because I don’t want to, it’s because I don’t know how to make it work. I received a message from Michael Laforest (the creator of wiiuse) and he said he had no idea how to make this work on the wii. (on the PC, yes) If he can’t do it, who am I kidding by trying? Daid’s informatby datalogger - Coding
Here is the last example from Ersek (I think he's in Budapest, Hungry) This I got from a non-wii site, just someone trying to help. Maybe someone else can make some use of this. It seemed to almost work... #define MAXDEVICES 10u /* Device identifier of the device we care about, or whatever. */ static const u8 mycod[] = { 0xAAu, 0xBBu, 0xCCu }; /* Return value: neby datalogger - Coding
I wasn’t going to say anything else because no matter how I word it, it sounds like I’m a whiner. This maybe so, but what I have to say is still valid if you think about it. My experience from this is that you are correct in saying no one else on the net was going to give me useable help while I tried to figure this out. The only people that offered any help in the form of example codeby datalogger - Coding
I think I'm going to give up on this. It seem to complicated for me to figure out on my own. Three days with little sleep trying to do this isn't worth the cost of a few wii remotes. The tape idea will have to do, although I think that's going to get found out quickly and defeated (like me now) :( Thanks to everyone who made suggestions! (Mod can close this thead now)by datalogger - Coding
On a c-programming user group, I was told to try the code below, but it DSI's on my wii. Any chance a wii expert can look at this and tell me how to "wii"-ize this to work? Ersek said: int main(void) { FILE *file = fopen("output.txt","wb"); struct bd_addr *BD_ADDR; BD_ADDR->addr[0] = 0xff; BD_ADDR->addr[1] = 0xff; BD_ADDR->addr[2] = 0xff;by datalogger - Coding
So far, by trial and err(mostly err) I have this working except the proper way to format printing BD_ADDR My APP compiles and runs on the Wii, but the compiler complains about how I'm printf'ing the macro, and I can't find any help to show me how to do it right. I can see the Bluetooth numbers, but they are not in the correct format. Can someone please help me by tellinby datalogger - Coding
Maybe I should be looking at the \bte\bd_addr.h and bte.h lib for answers? Can someone please give me a hint on how I can use this? #ifndef __BD_ADDR_H__ #define __BD_ADDR_H__ #include #ifdef __cplusplus extern "C" { #endif /* __cplusplus */ struct bd_addr { u8 addr[6]; }; #define BD_ADDR_LEN 6 #define BD_ADDR_ANY (&(struct bd_addr){{0,0,0,0,0,0}}) #define Bby datalogger - Coding
QuotedancinninjaPieces of tape work as well. Also, "byte" needs to be declared, try: typedef unsigned char byte; ...up at the top of your file. That fixed it so it compiles without errors, Thanks! Now to figure out how to call this function. If I can get it to run and just show me the printf statements, I think I'll be good to go. What do I need to prepare to call into thisby datalogger - Coding
I'm getting closer, but need a little help (hope it's just a little ) Using devkitpro, I can compile WinterMute's sample "How_to_use_the_Wiimote" source from here just fine. Unlucky for me though, it doesn't use any of the WIIUSE calls, only the WPAD calls. WPAD does not have any functions to read the wiimote id. If it did- I'd be done and sleeping by now :)by datalogger - Coding
This part I understand. I think I'm not wording my issue clearly, so sorry for this. We want/need to be able to know internally who's wiimote belongs to who. This will stop the "problem" of people bringing over their "suspect" working correctly wiimotes, then "accidently" leaving a broken one behind. We have several Wii's where I live (not a home, in the normal sense). Pby datalogger - Coding
I think I'm heading down the wrong tracks here. Even if this worked it would defeat the purpose of what I'm trying to learn about. This will disable all of the wiiuse funtions I want to learn about and figure out how they work. What I'm trying to do is see how the wm structure works and how to use it. I'm trying to figure out a way to get the Bluetooth address from theby datalogger - Coding
Quotegiantpuneopening the rar says the folder inside it was last modified 19 april 2008. so obviously he was using libogc and devkit made before that date. also the readme says he is using grrlib 2.0. so that is a clue to how his build environment was set up. anyways, i tried to compile with the latest devkit and i see some shit that needs changed the error about vector and all the cam stby datalogger - Coding
I'm trying my hand at C programming my wii using devkitpro and came here to WiiBrew to look at example APPs. I found the perfect starting platform to use, but I cannot get it to compile. I have tried every verison of libogc, going back to 2006, but no-go. I can compile many other Homebrew apps from WiiBrew, but not this one. Is there a way that will tell me what versions of devkitpby datalogger - Coding
Quotedirtrider73068Why not use the sync buttons on the wii and wiimotes when they bring theirs over, wouldn't that be easier? After they are done and go home then resync them back to there own wii's? This post actually may belong in the coding section. Thank you for replying. The sync buttons won't tell me who brought which remote to my place. They all look the same. I wilby datalogger - Coding
I would like to start learning about using the Wiimotes in a Homebrew app. I was searching the internet and found an basic sounding source to start with, but it is so old and it seems libogc has changed so much since it was written that it won't compile. it is at (Trying to read its source code is very hard because it has all comments in Spanish.) All I want is a simple app sourby datalogger - Coding