Cube64-DX - Ameliored GC controller to N64 adapter.

DarthCloud

cool we can wait. thank you for working on this

 

Did some sniffing with my LA and I'm beginning to think that Wavebird might have have an unique ID and this is what is transmitted during initialization. US Patent suggest the same thing.

I'm going to buy a second Wavebird to verity this. My code might be only working for my Wavebird who know,

EDIT: Wow they are still selling high :S

 

if you was in the US id loan you one

 

If you need a second WB, let me know and I can find a way to hook you up.

PS - how much current does the rumble on the standard GCN controller draw from the 5V bus?

 

I still didn't look at anything power related. At this point I'm using my Wii as my 5v power supply

I've buy another Wavebird this morning on ebay in Ontario, will get it by the end of the week hopefully.

 

Thanks for all the answers DarthCloud

Would any of the information posted here help?:-
http://gc-linux.git.sourceforge.net...ff;h=b0c9e93aab3a2e8b4da249eb15d30300679ad2fa
Or
http://hitmen.c02.at/files/yagcd/yagcd/chap9.html#sec9.1

 

I've read so far 4 different ID from my Wavebird, but only one match those in that documentation.

My observation so far

-Status send by Wavebird receiver:

No comm. with WB and not initiated: 0xA80000
No Comm. with WB and initiated: 0xABD0C0
Comm with WB and not initiated: 0xE9E0C0
Comm with WB and initiated: 0xEBF0C0

 

Yep. I browse the local GameStops whenever I'm near one in a decently sized city. They ask $17.99 for a used Wavebird (friend with me bought one we found yesterday and another a few days before that) and $11.99 for Game Boy Players. Last one I found had a disc that never had its tape removed, the disc itself goes for $15 alone without being sealed. :thumbsup:

If there is an easyish way to read IDs I have access to four different Wavebirds.

 

I will receive my second one tomorrow or Friday. So it will be ok.

Anyway I'm beginning my semester end exam next week so I won't be working on this much before Easter.

 

Received the second Wavebird, did some quick sniff with it and their is indeed an unique ID for each Wavebird.

But it's easy to fix, will try to fix it this week-end.

So my first Wavebird is the only one working currently

 

what does it matter

 

Received my Blast Corps today, tried it with Cube64-DX version prior to the joystick fix and I'm not getting any issue.

Since the GC joystick don't go beyond 208 and never reach 256 it stay in a range acceptable for Blast Corps. The only issue is that Blast Corps think the rumble pak is an corrupted memory card like Cruis'n USA and stay at an error screen.

But the same workaround I implemented for Curis'n USA is working fine to avoid the error.

I thinking about removing the joystick range fix since it don't create any real problem in any game to have a extended range and since it's taking lot of CPU cycles to apply and take a good amount of flash memory.

 

Hmm, but didnt you say before that the joystick range fix makes the analog stick feel more like an original N64 analog stick? Personally I think thats worth using up some CPU cycles and flash memory, but its your project and you know the pros/cons more than me so :shrug:

 

Yeais I guess I will have to play with both solution to make my mind about it

 

Still waiting on a tutorial.

 

....

 

Have some patience, good things come to those who wait :nod:

 

Whats with the entitlement attitude?

 

i beleive he is just eager to build one but doesnt know enough to wing it. no entitlement attitude

 

That and more of a subtle bump explaining my interests in this man's project.