Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
07188 DIP/Input Major Always Dec 28, 2018, 18:03 Jul 2, 2019, 00:18
Tester Hydreigon View Status Public Platform MAME (Official Binary)
Assigned To Hydreigon Resolution Fixed OS Windows 10 (64-bit)
Status [?] Resolved Driver zr107.cpp
Version 0.205 Fixed in Version 0.212 Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary 07188: jetwave and clones: Analog controls do not respond in game.
Description Jet Wave and its clones analog inputs do not respond in game. They however respond fine in test mode. Alternatively, the Left/Right select buttons are used for steering and the T-Center button can be used for acceleration. I'm pretty sure it has always been the case.
Steps To Reproduce 1. Go into test mode and go to I/O Check and test analog controls.
2. Exit test
3. Insert some games and try to play the game with analog controls mapped.
Additional Information Originally posted this as a different bug which I thought the game regressed and booted with a "Driving System Error, Error Code 1" but it turned out that was caused when Dips "3 and 4" (shows ingame as "1 and 2") were set to off. Setting these switches on most likely tests all the hardware components. Error Code 1 from what the manual says states that all sensors are on (on actual hardware, they should be off and all sensors show on in mame). It's likely this sensor/motor/drive system is currently unemulated.

Then again, these "sensors" all showing on could disable analog controls in game or other related errors (edit: they don't. The sensors and analog controls have separate dip settings).
Github Commit
Regression Version
Affected Sets / Systems jetwave and clones
Attached Files
There are no relationship linked to this issue.
User avatar
Dec 28, 2018, 23:06
I had no problem starting with 0.205 from, 64-bit or 32-bit and booting to title without any messages.
Are you positive you are working from the original source and not sources you've adjusted?
User avatar
Dec 29, 2018, 05:34
Decided to do a bit of cfg and nvram cleaning and the game started up and ran fine (I don't even know how this came down to a bad cfg file instead of a nvram file). Bless this mess.

The accellator bug I mentioned still persists though.
User avatar
Dec 29, 2018, 19:28
If you want this bug entry to continue logged, please update your report information to reflect what is actually wrong and (if you know) what integer version it regressed in function. Did the controls ever work without using left turn/right turn inputs (SHIFT/X) by default? The acceleration seems to control using (Z) by default. Has this always been the case as well?
User avatar
Dec 29, 2018, 23:14
Updated this report. These left/right turn and T-Center buttons are the only means to play the game.
User avatar
Jul 1, 2019, 15:02

DIP 1 sets the machine to either run on analog controls/potentiometers or JAMMA inputs (currently set to "off/product"). DIP 2 sets the drive system/force feedback and sensors on or off (currently set to "on" which disables both). On actual hardware, I can imagine setting DIP 2's position to "on" would disable the force feedback. Alternatively, the sensors have push buttons (except the ALM) which I forgot to implement but may find out soon since they are controlled by JAMMA inputs.

Link to manual:

It's also normal for the "machine initialization" step on those Konami PPC games to take a while so the analog controls can function properly on actual hardware.