Emulator

The message being misaligned is due to our free text.

I just created issue 8362 for that.

Can confirm that using GC BIOS fonts resolves the misplaced text issue.

Should also note that the controller test specifically fails during the analog directional control test. Prior to tests for the c-Stick / shoulder buttons.

Um wait, is it invalid that an emulated controller can't pass this? The emulated controller can't pass the test which still seems like problem. I understand that a real controller can, but I'd presume we'd want an emulated controller to so so.

We can't due to the shape of the joystick range, from what I just read.

OK, I guess if we want to declare this a controller settings problems I want a bit more detail on if there are settings that can be changed to resolve it. If there are then I'm fine with this being invalid, if not then it seems there may be some work left to do.

I understand that skidau provided basic directions, but even after a while of adjusting the radius settings I can't get things to align to exactly 100 in the test. We may be able to better restrict inputs to range expected here.

We also have the "SI:Unknown command (0x43)" error with an emulated controller that seems like it would need to be resolved.

The radius setting of the GC pad main stick will fix this for you. To determine the right value to enter, go into the Controller test and push the stick as far right as it can go and record the X value. Use this formula:

100 / X * 100 = value to enter into radius setting.

The other part of the problem is that there needs to be a way to limit the diagonals to a value of 75 in the test. This emulates the stick "gate" which is the dark gray plastic part at the bottom of this picture: http://upload.wikimedia.org/wikipedia/commons/a/a9/GameCube_Analog_Stick.jpg Note that the GC pad's gate is not perfectly round. It is an octagon.

Thanks for the further info, skidau.

Ia there another issue related to the gate emulation. Again, I don't want to be a pain, but it's an issue that may subtlety effect a lot of games. The failure here at least provides a clear indicator of the emulation problem (i.e. even if it doesn't apply to the real GC controller.).

Further on the (0x43) error...
https://code.google.com/p/dolphin-emu/issues/detail?id=8365

It's apparently passing in latest master. Can this be retested?

I've tested it again with both a native GC controller and an XBOX One S controller through Bluetooth. Seems like the native controller works fine and passes the test, but I couldn't get the sticks to work properly. Seems the range of the sticks doesn't line up with the range of the sticks on a native controller. Max value on a native controller was 101, whereas the max value with my XBOX controller was 83. I tried using the recalibration tool, which didn't improve anything either (I calibrated both before and after the video).
Here's a short youtube clip:
https://www.youtube.com/watch?v=jd8AnIHB3RQ
It did manage to pass with a native controller, but looks like emulated controllers are still broken. The SI command error doesn't seem to be present anymore however, I tried multiple times and never had it show up.

This should be retested with: https://github.com/dolphin-emu/dolphin/pull/8963

No, that pull request is not relevant.

The SI command error returned at some point before 5.0-10411. 5.0-10411 through 5.0-10741 spits it out once and if you press OK the test works just fine. On 5.0-14095, pressing OK will just result in the test immediately throwing the error out again and ignoring it will cause not just the service disc, but Dolphin altogether to crash. It seems 5.0-10745 changed the way this behaves, which makes sense since it's an SI related PR. Also got the usual "harmless" 0xff FIFO error on all versions tested.