Rpg Maker Developers Group

I've read a few users bring this up back in 2017; when testplaying, some people experience the RM2k3 gamepad being stuck on the up key. This issue, to me, is exclusive to RM2k3 (it even works normally with rm2k). The issue appears to be the 1.12's added compatibility with the D-pad? Anyone here got the same issue as me? and if so, any idea of how to fix it? thanks!

PS: I've hd some issues with this controller (it's a bootleg PS3 controller) being briefly stuck on up when playing on the PS3 itself. I'll gently nudge and it'll go back to normal, though. I also re-calibrated and ran tests on the controller and the axis indicator doesn't detect any vertical input, either.


EDIT: AntiMicro, a controller remapping solution, seems to partially do the trick. It will allow you to create and load a whole new controller setup for whatever game you're playing. However, it doesn't overwrite the previous setup, so you'll need to dummy out the actual controller somehow. The easiest way is to just plug the controller off and only plug it in after the game's running. That should make the game ignore the actual controller input, and only respond to the AntiMicro remapped input. I don't know if RM2k3 ever performs any checks for active controllers other than at launch -- if it does, then that method won't work. Otherwise, this is a fine method for enjoying games as a player.

It's less than ideal if you're releasing a polished, commercial game, but I think a decent enough solution would be giving these instructions in a readme and providing the player with an AntiMicro controller profile that they can just plug in their app and run the game. Still, if anyone has an alternative I'm all ears!