When i mapped the Multikeys for example Number 1 with left and up, and i go to the game the button is pressed !!! In my example Crash Bandicoot 3 Crash is running always left-up !!! What must i switch on ???

I think if you look at the number 1 key in the controller setup, you'll likely see that it is a sticky button. If you disable the sticky it should only activate the button when you press it.

I have changed the option and the same result !?!! I don´t know what i should do....

Just to check, you changed it in the overlay manger right? not in the multikey setup?

If yes, then you will have to provide more info, like;
- What phone/device are we talking here?
- Do you have the free or the supporter version?
- What is the region (as in PAL or NTFS)?
- Did this happen from day 1? or only recently? (if supporter version, since a recent update?)
- Does the same happen for normal overlays?

Yes i changend it in the overlay manager..

My Phone is the HTC HD2
The Games are PAL and NTSC (Crash3 is PAL)
It happens the first time, when i change the Multikey to up and right for example it begins
yes with all overlays...

I suggest you reinstalling FPSEce, it migh quite possibly fix your problem =)

Do you have any software installed on your HD2 that controls landscape/portrait orientation?

If so... turn it off for FPSECE.

Also... double check that your mapped keys are NOT sticky keys... once you have made changes in overlay manager you need to exit back to main menu (by pressing fpsece power button) for the amendments to be saved.

There was no app installed to change the portrait or landscape mode...
I have reinstalled the EMU and use the original Skins, but when i change the first time for example multikey 1 (default is square an left) crash is running in this direction i have mapped for example left & up ! Before i mapped the button new it will work ok....

Is tihs problem onley on my HD2????

I just had this problem yesterday with Castlevania, where Alucard was constantly running to the left. If I held the key, he would stop, and if I turned the key into a toggle button and activated it, he also stopped. It went back to normal after a simply soft reset of my phone.

Try cycling through the input options (g-sensor/stylus mode/hw buttons). I had some problems with stylus mode being active but not selected which produced strange beghavior with onscreen d-pad...