I'm trying to play using my F710 gamepad and I've noticed something in some games. I've looked for similar threads, but I didn't find any. Take a look at the following screenshots, which were taken using the build 4.0-5811 (it was the latest when I created this thread):![[Image: KOHcEZS.jpg?1]](http://i.imgur.com/KOHcEZS.jpg?1)
![[Image: AQKfM5h.jpg?1]](http://i.imgur.com/AQKfM5h.jpg?1)
Without saying anything, both screenshots seem normal, but if I mention this, they aren't. In the first screenshot I'm playing "Tilt Island" on Super Paper Mario, where you normally hold the Wiimote sideways and tilt it to the left, or right to make that island tilt. What is happening is that when I took the screenshot, I wasn't "tilting" my emulated Wiimote at all. What you see is the default position of the Wiimote. The game "thinks" that you are tilting the wiimote to the right all the time. In other words, the game receives tilt commands when it shouldn't be. Although it's not a big deal in Super Paper Mario, it is really frustrating when playing other games, like Sonic and the Secret Rings (the second screenshot), or racing games. One might think that something's wrong with the gamepad, but that isn't true. These are my settings:
![[Image: 1dsXhwi.png?1]](http://i.imgur.com/1dsXhwi.png?1)
Ignore the fact that both "Sideways" and "Upright" are checked, this is what it is suggested in the wiki, I've tried all combinations with these by checking and unchecking them and they have no effect at all in THIS issue.
Instead, look at "Tilt":
Axis Y- = Left stick up
Axis Y+ = Left stick down
Axis X+ = Left stick right
Axis X- = Left stick left
I set dead zone to 1, so, the tiny square in the center is gray and not red. When it's gray, Dolphin doesn't receive any tilt-related commands. I've also tried changing the angle, but that didn't change anything. I eventually noticed that the problem has nothing to do with the gamepad, it also happens even when using the default settings of the keyboard! Does anyone else have the same problem?
Without saying anything, both screenshots seem normal, but if I mention this, they aren't. In the first screenshot I'm playing "Tilt Island" on Super Paper Mario, where you normally hold the Wiimote sideways and tilt it to the left, or right to make that island tilt. What is happening is that when I took the screenshot, I wasn't "tilting" my emulated Wiimote at all. What you see is the default position of the Wiimote. The game "thinks" that you are tilting the wiimote to the right all the time. In other words, the game receives tilt commands when it shouldn't be. Although it's not a big deal in Super Paper Mario, it is really frustrating when playing other games, like Sonic and the Secret Rings (the second screenshot), or racing games. One might think that something's wrong with the gamepad, but that isn't true. These are my settings:
Ignore the fact that both "Sideways" and "Upright" are checked, this is what it is suggested in the wiki, I've tried all combinations with these by checking and unchecking them and they have no effect at all in THIS issue.
Instead, look at "Tilt":
Axis Y- = Left stick up
Axis Y+ = Left stick down
Axis X+ = Left stick right
Axis X- = Left stick left
I set dead zone to 1, so, the tiny square in the center is gray and not red. When it's gray, Dolphin doesn't receive any tilt-related commands. I've also tried changing the angle, but that didn't change anything. I eventually noticed that the problem has nothing to do with the gamepad, it also happens even when using the default settings of the keyboard! Does anyone else have the same problem?
[color=#000080]Warning Level: 99.9999999999...%[/color]
That's funny, but it's not what you said, it's a peach and it isn't hanging from the tree, it's falling from the sky, like those glasses of juice! I haven't hacked the game or something! In this mini-game you have to tilt the Wiimote to move Mario and make him collect fruit falling from the sky, in order to score. Anyway, I'd really appreciate it if some people help me find out whether I'm the only one having this issue, or not and whether I can fix it someway I haven't thought of in the first case, or wait for a fix in the next development builds in the second case.