- --
Viewing Issue Advanced Details
[ Jump to Notes ]
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
07793 | DIP/Input | Minor | Always | Nov 19, 2020, 00:28 | Nov 24, 2020, 20:38 |
Tester | GeekyFerret | View Status | Public | Platform | MAME (Official Binary) |
Assigned To | Resolution | Unable to reproduce | OS | Windows 10 (64-bit) | |
Status [?] | Closed | Driver | |||
Version | 0.226 | Fixed in Version | Build | 64-bit | |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 07793: calspeed, sf2049, vaportrx and clones: Broken analogue inputs after second launch | ||||
Description | When launching the game the first time, the analogue inputs will function correctly. But after closing MAME and launching it again, the analogue inputs will malfunction when pressed. In calspeed and sf2049, the game will randomly select things in the menu on its own and the car won't respond to inputs most of the time. In vaportrx, you can't control the ship, it just flies up and down on its own. Entering the service menu temporarily fixes the issue. | ||||
Steps To Reproduce | |||||
Additional Information | |||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | calspeed, sf2049, vaportrx and clones | ||||
Attached Files
|
|||||
Relationships
Notes
5
No.18165
Osso Moderator
Nov 19, 2020, 10:35
|
I just tried calspeed and it works fine for me even after relaunching the game. |
---|---|
No.18170
PepsiBoy428 Tester
Nov 20, 2020, 01:32
|
Try reinstalling MAME |
No.18171
GeekyFerret Tester
Nov 20, 2020, 05:05
|
I've found out that enabling freeplay in calspeed's service menu causes the controls to break after relaunching. |
No.18174
Tafoid Administrator
Nov 24, 2020, 00:27
|
Even with FREEPLAY set when I attempted calspeed after a full stop and restart of MAME the default controls seemed to work fine for me for steering, gas and brake. Anyway, I cannot confirm. Closing. |
No.18180
Tafoid Administrator
Nov 24, 2020, 20:38
|
Looking back, this may be included as issue related to 07799 which was related to inputs not functioning correctly. I'll add as related. |