Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
09557 DIP/Input Minor Always 2 days ago 1 day ago
Tester mmarino4 View Status Public Platform MAME (Official Binary)
Assigned To Resolution Invalid report OS Windows (x64)
Status [?] Closed Driver
Version 0.289 Fixed in Version Build x64
Fixed in Git Commit Github Pull Request #
Summary Regresssion 09557: jetwave, jetwavej: Accelerator does not reach maximum speed
Description The accelerator in Jet Wave does not reach maximum speed. It only gets to about 2/3 in the service menu on both analog and digital inputs. Reversing the input will yield the same maximum result.

This was broken in 0.274 when the steering was fixed. That works great now but this was the side effect of the fix.
Steps To Reproduce Go into the games service menu and try to get the accelerator input to the maximum level. Note that it cannot reach the top. Start a game and your craft will be slower than it should be.
Additional Information
Github Commit
Flags Regression
Regression Version 0.274
Affected Sets / Systems jetwave, jetwavej
Attached Files
 
Relationships
related to 08962Resolvedhap  jetwave, jetwavej: Analog Input Sensitivity Too High 
Notes
2
User avatar
No.24702
hap
Developer
1 day ago
edited on: 1 day ago
FYI "regression version" is the MAME version where the bug was introduced, not the last known version where it still worked fine.

Acceleration pedal is full range here. Did you make sure to remove old jetwave.cfg and nvram files? Or are you certain you didn't touch your analog controls, and your controller is not worn out (stick drift)? Or maybe you pressed CTRL during the game booting.
There's a warning message at boot "Please do NOT ride this machine during initialize". It implies it's calibrating stuff. And indeed, if I touch my xbox pad accel pedal control, the analog range is wrong in the game.
User avatar
No.24703
mmarino4
Tester
1 day ago
This can be closed. The default of "Joy Accelerator -" was reading something off of a controller I had plugged in and calibrating it wrong so even CTRL was showing this behavior on a fresh build.