Control issues with Final fantasy fables: chocobos dungeon

I'll start with system info, OS-windows 7 professional 64 bit, graphics card-nvidia GT 620, cpu-i7-3770 3.4 GHz, RAM-12 GB. Dolphin version is 4.0-4766. In short i have a wiimote config set up and a classic controller config as well, the game only appears to respond to the classic controller which is fine with me. The issue is that directional controls don't seem to be working(not yet gotten in-game). Basically in short upon reaching the file select menu, the game immediately jumps to file 2 in the center and refuses to accept anything except input from either button A or B(shouldn't I be able to pick file 1 or 3 is i want?). If I select that i'm offered the pictures of either holding the wiimote with a controller horizontal or vertical. I cannot get the game to allow me to pick between the 2. I have not actually tried going in-game yet, and don't really want to until i resolve whats going on here. I'll update this post shortly with screenshots of my wiimote and classic controller settings.

EDIT
If I disable the classic controller then no controls of any kind are acknowledged by the game including A or B on the wiimote settings(which is just basically left and right mouse clicks)
These settings work without any problems in rune factory frontier though I have not yet tried out knocking on doors in that game.
Wiimote settings
http://i165.photobucket.com/albums/u...20settings.png

classic controller settings
http://i165.photobucket.com/albums/u...20settings.png

Just looking at the Classic controls looks like your sticks are not center

you can try with windows to do a re-calibrate or make the deadzone bigger, 1st option will be the best

see if you can center up the sticks

Re-calibrating seems to not help, upping the dead zones doesn't appear to matter either, like I said works fine with other games, and doesn't cause trouble with other emulators.

What controller are you using, an X360 controller? Can you try using it in DInput mode instead of XInput?

Okay tried switching to DInput makes the controller not respond at all in the emulator.

I think you have to set up a new config for DInput.

Nope, all the displayed controls (see above screenshots) are still shown when i switch to DInput which suggests its either using the same ones, or that I already configured it. Either way, the controller does not respond at all if i use DInput.

I'm sure DInput doesn't have trigger L or trigger R instead it has button 8, button 9, or z axis +,- etc.

just try setting up a new config it wont hurt.

Like I said it has the same setup as XInput does here a screenshot

EDIT
As for trying to re set up the config in DInput mode, not surprisingly all input of any kind from the controller is ignored, not even allowing it to be re-configured. I'm using the standard microsoft driver for it, pretty sure it doesn't even support DInput in the first place.

http://i165.photobucket.com/albums/u...n%20DInput.png

I'm not sure why this is happening. Switching to DInput is like plugging in a different controller, so maybe you have to change the "Device" to your controller? I'm not sure why it says "Keyboard Mouse" on your device.

or hit refresh and make sure the DInput Joypad is selectable otherwise it is just not seeing your pad at all in Dinput mode

Hitting refresh doesn't seem to help. DInput joypad does not show up as a choice. Like i said before, I do not believe the Microsoft driver for 360 controllers supports DInput.

Ok that was my bad, I have a PS3 controller and my PS3 driver allows me to switch between DInput and XInput so I thought something similar exists for X360 drivers but apparently not.

But according to MSDN X360 controller does support DInput, so I'm not sure why it's not showing up in your devices...

Last time I used a 360 pad I used no drivers and it just runs directly with not drivers as D input though it was a usb pad

hmmn when I plugged mine in the first thing that happened was that windows started looking for a driver for it, found the microsoft one and installed it.

Last time I used a 360 pad I used no drivers and it just runs directly with not drivers as D input though it was a usb pad

Okay I took the time to do a little bit more testing. This problem seems to be only with the main menu that you reach upon booting the game up. Once I get to in-game there isn't any problems at all. Still its quite bizarre.