Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
08165 DIP/Input Minor Always 20 days ago 7 days ago
Tester hap View Status Public Platform MAME (Official Binary)
Assigned To Resolution Open OS Windows 10/11 (64-bit)
Status [?] Confirmed Driver
Version 0.238 Fixed in Version Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary 08165: inputs not active during first frame
Description Inputs are not active during the first frame after cold boot or hard reset.
I think it only applies to inputs obtained from the OSD (keyboard, gamepad, etc).
Steps To Reproduce This is a bug in the MAME core, it can affect any driver.
I found an easy test case with im05, though that set has been added late december 2021, it will be in MAME 0.240.
One of the first things im05 does is check the keypad, and it enters a routine if one of the buttons was pressed. This happens in the 1st timeslice before the first frame is drawn.

- mame im05 -noskip_gameinfo
- at the gameinfo popup, hold "b" on keyboard
- game starts and shows "b" on the display

again:
- mame im05 -noskip_gameinfo
- press any key to start
- hold "b" on keyboard
- while holding "b", press F3 to do a soft reset
- game shows 4 dashes

The 2nd one is correct. It will show 4 dashes if you hold "b" at power-on, but does not happen in MAME unless you do a soft reset.
Additional Information I think what happens in general is:

- start MAME
- emulate 1 frame
- enter 'vblank'
- draw frame
- check inputs
- emulate 1 frame
- enter 'vblank'
- draw frame
- check inputs
- etc

want:
- start MAME
- check inputs
- emulate 1 frame
- enter 'vblank'
- draw frame
- check inputs
- emulate 1 frame
- enter 'vblank'
- draw frame
- check inputs
- etc
Github Commit
Flags
Regression Version
Affected Sets / Systems
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
0
There are no notes attached to this issue.