Page 1 of 2

Moga Compatibility Issue

Posted: Sun Aug 02, 2015 6:34 pm
by Felix_Nix
I'm using the Moga Pocket (or Moga PowerA, whatever you want to call it) and I can use it on the Pivot app, and if I use the Universal Driver, I can use it on MAME, but that requires the VK. I tried using it as a VK, and just with the pivot app, but neither allow me to input anything into DraStic. I try to run the key mapping, and no button press registers on the Key mapping, or in game. Help would be greatly appriciated.

Re: Moga Compatibility Issue

Posted: Sun Aug 02, 2015 6:46 pm
by Exophase
There is an update (2.4.0.1a) which should be out soon or out already depending on where you are. It addresses issues with Moga Pocket.

Re: Moga Compatibility Issue

Posted: Sun Aug 02, 2015 7:04 pm
by Felix_Nix
Sorry, I should have probably added that I'm using a Galaxy S5 with DraStic v r2.4.0.1a Also like to add that I think (though I may be wrong) that I go more in depth than your average dude. I looked at the faq, and even looked up online for any fixes, the general consensus being that it should work with Moga "dry", and that no additional fenagaling is required.

Re: Moga Compatibility Issue

Posted: Sun Aug 02, 2015 7:30 pm
by Lordus
MOGA controllers (in mode A, which is the only one the Pocket supports) can't be mapped in the external controller settings, they have a fixed button mapping.
Does it display 'Show MOGA mapping' at the bottom of the external controller settings?
Are you using the latest version of the MOGA pivot app?

I bought a MOGA pocket yesterday just for testing this. It doesn't work for me on Lollipop with the last release (2.4.0.0a), but does with the current one (2.4.0.1a).
If you updated the app, and 2.4.0.1a isn't your first installation, try to re-install it.

Re: Moga Compatibility Issue

Posted: Sun Aug 02, 2015 7:47 pm
by Felix_Nix
Well, that clears that up. I wondered why it had 2 names. It doesn't have 'show moga mapping' which is why I attempted Custom mapping. Pivot app was downloaded two days ago, and is the latest version. I will un-install and re-install and update this post. I really have no idea why I didn't think about that.

Update: Did that, no change. Attached 2 images showing the external controller settings, and the version.

Update 2: I have now tried running it on both Nova Launcher and default Lolipop. No change.

Re: Moga Compatibility Issue

Posted: Sat Aug 08, 2015 7:08 pm
by Felix_Nix
Any other suggestions, or should I just contact the team directly?

Re: Moga Compatibility Issue

Posted: Sat Aug 08, 2015 7:10 pm
by Lordus

Re: Moga Compatibility Issue

Posted: Sat Aug 08, 2015 11:38 pm
by ericbazinga
Felix_Nix wrote:Any other suggestions, or should I just contact the team directly?
BTW, you WERE talking to the team. Exophase is the main creator of DraStic, and Lordus ported the emulator to Android.
The rest of us mainly resolve problems with the app, beta-test new builds, and scold people who download cracked versions.

Re: Moga Compatibility Issue

Posted: Sun Aug 09, 2015 4:10 am
by kaikun97
Lordus wrote:MOGA controllers (in mode A, which is the only one the Pocket supports) can't be mapped in the external controller settings, they have a fixed button mapping.
Does it display 'Show MOGA mapping' at the bottom of the external controller settings?
Are you using the latest version of the MOGA pivot app?

I bought a MOGA pocket yesterday just for testing this. It doesn't work for me on Lollipop with the last release (2.4.0.0a), but does with the current one (2.4.0.1a).
If you updated the app, and 2.4.0.1a isn't your first installation, try to re-install it.
But my pocket controller also works with the universal driver which lets me map keyboards. Whats weird is drastic ds is the only app refusing to acknowledge I am even pressing anything in key mapping and it SHOULD work because as far as drastic knows, its a standard virtual keyboard.

Re: Moga Compatibility Issue

Posted: Sun Aug 09, 2015 4:58 am
by Lordus
Just tested the Pocket with the universal driver and could map it normally. Are you using the latest beta?
2.4.0.0a could have broken this, but versions before and after should allow it.