- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
08569 | DIP/Input | Critical (emulation) | Always | Feb 25, 2023, 00:01 | Feb 25, 2023, 22:43 |
Tester | PepsiBoy428 | View Status | Public | Platform | MAME (Official Binary) |
Assigned To | Resolution | No change required | OS | Windows 10/11 (64-bit) | |
Status [?] | Closed | Driver | |||
Version | 0.252 | Fixed in Version | Build | 64-bit | |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 08569: sf2049, sf2049se: Unresponsive pedal inputs | ||||
Description | Before the update was released, the pedal inputs on my Logitech G920 wheel on Rush 2049 worked fine but in the latest version of MAME, the pedal inputs became unresponsive in-game. I even tried deleting my cfg file and my NVRam but it didn't work. The same problem happens with an Xbox One controller. | ||||
Steps To Reproduce | Map Joy 1 Accel to the gas pedal of your wheel or right trigger on Xbox One controller in Input settings and then enable Joy 1 Accel Reverse or whatever its called in Analog Input Adjustments (if using an Xbox One controller, skip this step) and then you'll notice the issue. | ||||
Additional Information | |||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | sf2049, sf2049se | ||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
16
No.21100
Robbbert Senior Tester
Feb 25, 2023, 12:20
|
I don't have any controllers so unable to test/verify this, however there's been reports elsewhere of controller issues in this release, so I'll acknowledge this report. Hopefully the person responsible for the changes in the 251-252 cycle will have a look. |
---|---|
No.21101
Wampa Tester
Feb 25, 2023, 12:36
|
Is this not just an issue in switching to the Game Controller API as default in 0.252? What happens if you: "just set the joystickprovider setting to sdljoy in your mame.ini file." As described in the release statement to restore Joystick API. |
No.21102
PepsiBoy428 Tester
Feb 25, 2023, 15:28
|
I'm planning on downgrading to MAME 0.251 until this gets fixed in a future version of MAME |
No.21103
cuavas Administrator
Feb 25, 2023, 20:51
|
No-one provided testing with driving controls during the two months while 0.252 was on development. I made an effort to support controllers I have no access to and spent a fair bit of time trying to find documentated standards for different kinds of controllers. However, it's all a mess, different manufacturers do things differently, and there's no accurate documentation for developers. If you want this fixed, you'll need to provide actual useful information for diagnosing the issue, or buy me a G920 wheel (at Australian prices). I don't have driving controls, and they simply aren't worth the asking price to me. But if you're just going to threaten to downgrade, go ahead - I don't mind. |
No.21105
PepsiBoy428 Tester
Feb 25, 2023, 21:03
|
How do I get the diagnostics? |
No.21107
PepsiBoy428 Tester
Feb 25, 2023, 21:07
|
I'll make a video later of the problem |
No.21108
cuavas Administrator
Feb 25, 2023, 21:11
|
I need to know at least: Type and subtype reported by controller Which control maps to each axis in DirectInput Actual raw value ranges reported in DirectInput A video is completely useless. |
No.21110
PepsiBoy428 Tester
Feb 25, 2023, 21:27
edited on: Feb 25, 2023, 21:40 |
UPDATE: tested this with an Xbox One controller and the pedal inputs didn't work on that either therefore it's an emulation bug therefore the Logitech G920 is not the only device with this issue |
No.21111
cuavas Administrator
Feb 25, 2023, 22:09
edited on: Feb 25, 2023, 22:12 |
Do you know the difference between emulation and I/O? Now are you going to give some useful information or are you just going to keep being angry? Because if it's the latter, I'll just ignore this issue. I tested extensively myself and solicited user testing to cover more controllers: https://github.com/orgs/mamedev/discussions/21 Being uncooperative won't help you. Also, pedal inputs work fine with default assignments when using the triggers on an Xbox controller. That's been tested by multuple people. You must be doing something wrong if that isn't working, or you have an outdated configuration file. |
No.21112
PepsiBoy428 Tester
Feb 25, 2023, 22:12
|
I don't know how to give the useful information, I'm not an expert on MAME |
No.21113
PepsiBoy428 Tester
Feb 25, 2023, 22:17
|
I could try a new MAME directory |
No.21114
Robbbert Senior Tester
Feb 25, 2023, 22:18
|
Pepsiboy428, please take this conversation over to the github thread mentioned by cuavas, everything should be explained there. If it isn't, just ask. You'll never win this battle by being argumentive about it. |
No.21115
PepsiBoy428 Tester
Feb 25, 2023, 22:20
|
I'm not trying to be argumentive, I am just frustrated |
No.21116
cuavas Administrator
Feb 25, 2023, 22:25
|
I just tested sf2049 again with official 0.252 using an Xbox controller with default assignments. The right trigger works as the accelerator, the left trigger works as the brake, and the left thumb stick X axis works as steering. Some notes: • Old configuration files will need to be removed or updated because the input tokens are different for 0.252. • The Input Devices menu is your friend – you can use it to check whether your controller is recognised and how MAME is mapping the controls. * Verbose output provides useful diagnostic information when MAME is recognising controllers. |
No.21117
PepsiBoy428 Tester
Feb 25, 2023, 22:31
edited on: Feb 25, 2023, 22:32 |
Turns out it actually was my cfg file, it works good now, you can now close this, sorry for the false report |
No.21118
Robbbert Senior Tester
Feb 25, 2023, 22:42
|
Thanks for finding this out. Closed. |