- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
01950 | DIP/Input | Minor | Always | Jun 28, 2008, 18:28 | Oct 26, 2008, 04:16 |
Tester | Canim | View Status | Public | Platform | MAME (Self-compiled) |
Assigned To | Resolution | No change required | OS | ||
Status [?] | Closed | Driver | |||
Version | 0.125u8 | Fixed in Version | Build | Normal | |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 01950: cybrcycc: You can't turn to the left. | ||||
Description |
Left seems to be center and center seems to be right. See IO Check. |
||||
Steps To Reproduce | |||||
Additional Information | |||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | cybrcycc | ||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
6
No.01424
Tafoid Administrator
Jun 28, 2008, 18:46
|
This I can confirm. The Test Mode shows a value of 0-255 (128 being center - but showing RIGHT). Is it possible this is a -255 to 255 with 0 center? Would the input changes assume all digital values have to be positive? |
---|---|
No.02381
Canim Senior Tester
Sep 6, 2008, 23:48
|
Seems that the steering is now fixed. Bug resolved. |
No.02383
Tafoid Administrator
Sep 7, 2008, 00:12
|
Not here. 32-bit Windows build still goes no farther than center in the I/O tests. So it works on 64-bit? |
No.02392
Canim Senior Tester
Sep 7, 2008, 17:57
edited on: Sep 7, 2008, 17:59 |
OK I tested it now more, tested it in 127u1 32bit with and w/o mouse and it worked perfectly after initialise with 9 and F2. I deleted nvram and cfg. Also works for 64bit in 127u2. Without initialise it is stuck to the middle and the right. |
No.02832
Canim Senior Tester
Oct 14, 2008, 03:31
|
This one is totally fixed for me now. It seems the nvram initialise was broken for a few versions. |
No.02932
Tafoid Administrator
Oct 26, 2008, 04:16
|
It seems to work if I initialize it the way you suggested. If you do it in the menus (there are 2 different initialization areas), it does nothing to fix this. Resolving |