You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I tried to play a bunch Commander Keen games with 4 button support I noticed some problems.
Movement goes Up-Left automatically, and trying to reconfigure in game won't help and sometimes even crashes the core.
This does not happen when using a controller that has thumb sticks. But you have to restart the core for this to work.
Introducing the dual sticks support messed things up it seems.
I think the regular 4 button/gravis setting is somehow looking for a pad with assigned joysticks, and won't work properly if there's none.
Gravis joypad mode is also not recognized inside the keen configuration screen, when using a 8bitdo m30.
While using 8bitdo sn30 pro, it is.
Adding to the confusion: sometimes the m30 controller will randomly work and get recognized as a gravis without error.
But then when you exit to dos and start another game, input malfunction or dodgy recognition again happens .
Perhaps adding a "None" Joystick Mode, is all that is needed to fix this?
The text was updated successfully, but these errors were encountered:
When I tried to play a bunch Commander Keen games with 4 button support I noticed some problems.
Movement goes Up-Left automatically, and trying to reconfigure in game won't help and sometimes even crashes the core.
This does not happen when using a controller that has thumb sticks. But you have to restart the core for this to work.
Introducing the dual sticks support messed things up it seems.
I think the regular 4 button/gravis setting is somehow looking for a pad with assigned joysticks, and won't work properly if there's none.
Gravis joypad mode is also not recognized inside the keen configuration screen, when using a 8bitdo m30.
While using 8bitdo sn30 pro, it is.
Adding to the confusion: sometimes the m30 controller will randomly work and get recognized as a gravis without error.
But then when you exit to dos and start another game, input malfunction or dodgy recognition again happens .
Perhaps adding a "None" Joystick Mode, is all that is needed to fix this?
The text was updated successfully, but these errors were encountered: