darthcloud / cube64-dx Goto Github PK

WaveBird don't work probably need special init.

I have built several Cube-64DX’s and am very happy with them! Thank you for 
all your hard work updating the Cube64 to support Wavebirds. I am currently 
building a custom N64 with the controller ports replaced by Camecube ports. 
(Allowing direct connection of Wavebirds and GC controllers.)

The problem I am going to have is regarding memory cars (Controller Pak’s). 
As I will not have actual N64 ports available, I will not be able to swap out 
the Wavebirds for N64 controllers when I need to save/load some games. I 
understand that in order for the chip to emulate a memory card it would require 
quite a bit more work. 

My proposal is this: Pass-through all traffic for the memory card out to a 
physical ‘Nintendo Controller Pak’ without processing through the PIC, 
attached to the PIC with leads. This way I could mount a memory card inside the 
case of the N64 and use it for the few games I would need it for. The other 
benefit would be someone could add a memory card port to their Cube64-DX and 
swap out memory cars just like an original N64 controller.

I have plenty of working N64 controllers and Controller Pak’s that I would 
happily destroy in an effort to accomplish this.

Is something like this possible?

Cruis'n USA

Bug:  The game simplely freeze at the first screen when I use the adapter. Like 
mario and star wars if I connect a original controller first and swap with the 
adapter everything work well.

Normally Gamecube games does calibration of the joystick when you power on your 
Wavebird.

The adapter does only this on power up and we might in some case endup with the 
controller being not calibrated correctly.

Also Wavebird send different response to 0x00 command under some condition.

Like receiver only (wavebird power off) will send a response different than 
while the Wavebird is power on.

Need to modify Wavebird implementation to support all Wavebird status 
correctly. And need to periodically check controller identity to know if the 
Controller has been power off and redo calibration once it's on again.

N64 controller never use the full range of -128 to 127 for it's axis. It only 
used it at about 66%.

Sending full range value will confuse some games like Blast Corps.

Super Mario 64 / Star Wars: Shadows of the Empire

Bug: When you open the 64 with those games and the adapter the game said that 
no controller is connected. If I start the 64 with a original
controller and swap it with the adapter everything is ok. So it's probably a 
detecting probleme only.

Doing the key combination work fine since it enable the rumble and then 
pressing the two button I do get another rumble. Controller work fine after 
that.

But the key mapping did not change.

Tested with 629 and it's still working fine. The code might need so adaptation 
for the 683....

Something that make the controller to show as a controller without rumble pak 
because a lot of game that don't suport the rumple pak detect it as a corupted 
memory card and said to you to ethier reset or replace another memory card. 
Something to disable the rumble pak emulation will be useful with those games. 
Something like press L + R + Y to
enable/disable will do the trick well.

I'm currently just replicating the communication done by my own Wavebird.

In this communication an unique ID is send by the Wavebird and the system reply 
it back to the receiver.

Since I alway return the ID of my controller this prevent other Wavebirds from 
working.

Bug #1: The rumble pak emulation didn't work.
Bug #2: This bug is realy weird. When I use the adapter with that game, the game
            sometime like every 5 or 10 seconde had I little
framerate down, you can easyly
            see that just be watching the opening demo of the game.
It's not a big lag but
            enough to notice it with the picture and the sound (sound
cut). If I unplug the
            adapter everything go back to normal.