Do you happen to know if its possible to shut down the whole accelometer thing in the sixaxis conf and where i can find this file?
No it's hardcoded into the sixad driver. Has nothing to do with Smoku's packaging nor blight plugin.
As an aside though... with that jstest I have just stumbled across the fact each of the buttons on the PS3 controller is also mapped to an axis. While this helps us very little for mupen it means Sony did a really awesome job of this controller: as essentially each button is pressure sensitive: Try it out
I knew this already hehehe. with the game granturismo you can see that when you press the X button slightly you give a little bit of gas. pressing the x button to the floor it will give the car full power. same with the brakes.
I just tested this joystick app and its awsome... i didnt know all buttons were pressure sensitive, but even de R and L1 buttons and even the D-pad has pressure sensitive buttons.
wow thanks for sharing this knowledge!
i will map the keys to the config file in muppen when im back tonight!
I didnt read your tutorial correct. im sorry the on and off in the bottom gives the right number indeed. Its my bad english... i have te read everything 5 times before i fully understand.
UPDATE..
Ok i found the right one... its in home/user/.mupen64plus
But the buttons i filled in are not corresponding to the numbers out of the jtest. I must be missing something
Buttons 14 and 12 should be L1 and L2 on the jtest. filling them in the blight config they are 10 and 8...
am i missing something... im starting to get freaked out here.
PREVIOUS...
Im sorry to bother again but i cant seem to fix it.
I opened blight and changed all the buttons to the outcome of the jtest. But all buttons are still the same nothing is changing.
are there more blight_input files? I edited usr/share/mupen64plus/config/blight_input.conf
Im a noob here. i know how to edit stuff but thats about it.
No. I'm using the default 'gamepad' config if that matters.
I've absolutely no idea why it isn't working. But if there is no js0 in /dev/input then it isn't mupen64 that is the problem. Try a reboot and then sync it up again. Ensure batteries aren't dead etc.
Maybe the wiimote has an other file in that directory? or are all controllers js0?
I had the same problem too. If you dont sync up the PS3 controller with the n900 then there wont be a js0 file in that directory. so make sure that the PS3 controller is connected to the n900 correctly before running the script.
If you get the question if you want to connect the ps3 controller when syncing it to the n900 then your bluetooth input in /etc/bluetooth/main.conf is not correctly configured. While connecting you wont see any message.
