06319: gticlub and clones: Accelerator don't work and message appear in screen

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
06319	DIP/Input	Major	Always	Jul 21, 2016, 19:50	Aug 30, 2019, 18:44

Tester	Fortuna	View Status	Public	Platform	MAME (Official Binary)
Assigned To		Resolution	Open	OS	Windows 10 (64-bit)
Status [?]	Confirmed			Driver	konami/gticlub.cpp
Version	0.175	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	06319: gticlub and clones: Accelerator don't work and message appear in screen
Description	Load, wait the initial tests, error appear when, this not happen in older versions The accelerator control don't respond in game
Steps To Reproduce
Additional Information
Github Commit

Flags
Regression Version
Affected Sets / Systems	gticlub and clones

Attached Files	0000.png (4,569 bytes) Jul 21, 2016, 19:50 Uploaded by Fortuna

No.12967 Osso Moderator Jul 24, 2016, 05:22	The steering wheel error has been there for a long time: I checked back to 0.130 and it was there. The accel error I cannot reproduce and it works in game too.
No.12974 Kale Developer Jul 26, 2016, 10:43	What happens if you try to calibrate it thru Test Mode?
No.12975 Fortuna Tester Jul 27, 2016, 00:04 edited on: Jul 27, 2016, 00:04	Do not respond when the button is pressed too Trying: -Reset the machine -Clear the nvram (F2+F3 inn start) -Deleting the *.nv created for new file Always has this screen (is next to calibration screen), in older versions working ok, bit a bit less performanced
No.12977 Tafoid Administrator Jul 27, 2016, 04:15	Please refer to my note at 06325 - default mapping with a fresh install doesn't act like you have mentioned. Try a fresh install on your end without mapping anything and see how that works. I suspect you have some controller condition that is causing conflict and the the game is looking and determining your pedal mapping is down all the time.
No.12989 Fortuna Tester Jul 27, 2016, 22:01	Well, testing with new and clear config, the problem continue
No.13866 Fortuna Tester Jun 2, 2017, 01:31	Update Testing in .185 version and using 2 differents joysticks and keyboard: Test 1: Xbox 360 joystick with wireless reciever, deleted cfg and ini configs, all clear only detect this joystick: Steering wheel error Test 2: Generic 8 buttons 4 axis USB joystick model Genius Maxfire G-08XU, Clear config, deleted cfg and all ini for default, only this joystick detected, the games boots and the message "Steering wheel error" not appear, runs perfectly Test 3: Keyboard with usb reciever, model Logitech, same above, Runs ok, but if the Xbox 360 joystick is detected, this has the message "Sterring wheel error" appear
No.15747 MetalGod Senior Tester Nov 6, 2018, 12:13 edited on: Nov 8, 2018, 15:59	Tested with a logitech G27 Steering Wheel. It marks 2 errors: Device Error (Steering Wheel) Device Error (Brake) Once ingame the steering wheel works, the brake doesn't. I figured out how to solve this. It is neccesary to mark "combined pedals" option inside the g27 wheel settings. Then, configuring mame keys for accelerator and brake. Now they both will appear marked as "combined pedals". The only error the game will show in its startup will be the one for the steering wheel. Once ingame everything works fine, steering wheel, accelerator, brake... It is pretty weird because gti club is the only mame racing game where I've had to enable that option.
No.15767 Hydreigon Tester Nov 8, 2018, 18:27	The culprit lies within adc1038.cpp, National Semiconductor ADC1038. Only GTI Club has a hack in that device for its analog controls to function because it doesn't sync on sars. The best fix would be to improve on that device and remove the hack for good but idk how much work that would take. Come to think of it, this may be related to why Silent Scope's analog controls work in test mode but not ingame (Ted probably should have leaved my Silent Scope bug as confirmed and make these two bugs related). It does use a different semiconductor, ADC12138, but both issues are related to sync/cycles ingame.
No.16234 Hydreigon Tester Mar 10, 2019, 18:36 edited on: Mar 11, 2019, 14:42	Regression: Link removed. Mistake from my end as I forgot to read the top post.
No.16236 Osso Moderator Mar 11, 2019, 06:15	As I wrote before the "steering wheel error" was already present in 0.130, which predates that commit you highlighted. As of 0.207, the analog controls work fine for me, so I'd like to have another opinion. The steering is a bit slow to respond with the default values, but adjusting the values in the MAME's analog controls menu gets it way better.
No.16822 MetalGod Senior Tester Aug 30, 2019, 16:14 edited on: Aug 30, 2019, 16:16	What I explained in my previous message is no longer neccesary since mame 0.212 (it seems it was fixed by Hydreigon). I mean, pedals using a logitech g27 now work fine with no need to activate the "combined pedals" g27 option inside its setup. When using this wheel, the game doesn't show the brake error anymore, but the wheel error persists.
No.16823 Hydreigon Tester Aug 30, 2019, 18:44	The steering wheel error will show up regardless due to an unemulated drive board. On actual hardware, GTI Club will check the force feedback motor during the control initialization test much similar to San Francisco Rush. The game expects to have its drive board logic detected and the steering pot values change accordingly from the drive board doing its motor test. This behavior is also present in the NWK-TR games.