Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|07104||DIP/Input||Minor||Always||Sep 22, 2018, 15:47||31 days ago|
|Tester||mmarino4||View Status||Public||Platform||MAME (Official Binary)|
|Assigned To||Osso||Resolution||Fixed||OS||Windows 10 (64-bit)|
|Version||0.201||Fixed in Version||0.206||Build||64-bit|
|Summary||07104: bbh, bbhsc, bbhsca, bbh2sp, bbh2spa, bbh2spb: Targeting is off|
|Description||After calibrating the gun, the crosshair does not match where the game thinks you are aiming. It worked correctly in 0.199 but 0.200 and 0.201 have this issue. Call of the Wild and Carnival King do not have this problem as the calibration setup is done with multiple points.|
|Steps To Reproduce||Start the game and go into the test menu. Select Gun Calibration and shoot the target in the center. The next screen will show where the game thinks you are aiming which does not match the crosshair, particularly as you travel away from the center of the screen. This also occurs during regular gameplay.|
|Affected Sets / Systems||bbh, bbhsc, bbhsca, bbh2sp, bbh2spa, bbh2spb|
|There are no relationship linked to this issue.|
Sep 22, 2018, 17:32
This commit is likely culprit:
Confirmed using bbh
Sep 22, 2018, 20:05
|I tried the alternate versions bbh2spa, bbh2spb and bbhsca and they all had issues even on 0.199. In some cases the input is not accepted at all.|
Jan 18, 2019, 20:45
FWIW changing line 280 of iteagle_fpga.cpp from
result = (m_guny_cb(0) << 16) | (m_gunx_cb(0) << 0);
result = (m_gun_y << 16) | (m_gun_x << 0);
seems to fix this (tested with bbh), but since Ted seems to have changed it on purpose I won't apply this.
Jan 19, 2019, 17:32
Yeah that change definitely wasn't intended. Thanks a lot for looking into this.
The fix is pushed.