- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
00787 | DIP/Input | Trivial | Have not tried | Feb 5, 2008, 07:55 | May 24, 2008, 22:31 |
Tester | NekoEd | View Status | Public | Platform | |
Assigned To | Resolution | Open | OS | ||
Status [?] | Confirmed | Driver | |||
Version | 0.77 | Fixed in Version | Build | ||
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 00787: bking: "Crow" DSW has no effect, crow is always on. | ||||
Description |
"Crow" DSW has no effect, crow is always on. Update:I tested this further and even went back to .71 MAME for testing too. It appears the crow object is currently not accessable with any switch settings. Besides disabling the crow, the flight pattern is not changed either when playing Birdie King. I am guessing the bug has always existed since Birdie King was first emulated in the bking2.c driver. Compare this with Birdie King 2. The crow can be disabled and the flight pattern can also be altered. I am guessing there are only two flight patterns even though there are 4 listings. 1 & 3 share same flight pattern while 2 & 4 share same crow flight pattern. New findings and comparisons: For Birdie King dips settings, "year display" works, "number of holes" works. Another dip that does not work in Birdie King dip settings besides "disabling Crow", is "free play". I tested with both .81 and also back to .71 for comparing. Anyway, part of the dips for Birdie King do work while other dip settings are "non-functional". |
||||
Steps To Reproduce | |||||
Additional Information | |||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | bking | ||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
1
No.01084
couriersud Developer
May 24, 2008, 22:31
|
This is not a dip/input issue. Just checked the schematics. If there is an issue, than that lines IO32 to IO34 (dipswitch C) are hardwired somewhere. The other possibility is, that this is just "feature by design". Can somebody check on a real pcb with *same* roms? |
---|