How to increase steering sensitivity on lr-fbalpha

[thestarglider]

@dudleydes I know, but several emulators do.

[quicksilver]

@thestarglider what controller are you using? I seem to remember some PlayStation style controllers having an issue where the full range of motion for the analog stick isn't detected properly.

[thestarglider]

@quicksilver so far I have tried an official Xbox One controller, a Speedlink Xeox Pro analog game pad and my usual go-to controller, the EasySMX wireless controller. All exhibit the same problem on lr-fbalpha, but are fine on lr-fbalpha2012.

[barbudreadmon]

@thestarglider said in How to increase steering sensitivity on lr-fbalpha:

All exhibit the same problem on lr-fbalpha, but are fine on lr-fbalpha2012.

Which is a bit weird, the analog control code in fbalpha2012 was backported from my work on fbalpha, the only difference i can remember is the missing "analog speed" core option which i added only recently (fbalpha2012 is basically always at 10). I'll investigate.

[thestarglider]

@barbudreadmon I appreciate that. Any word on what's happening?

[barbudreadmon]

@thestarglider I took a look twice, the second time this morning after someone opened an issue at https://github.com/libretro/FBNeo/issues/27, i still don't know what's the problem.

[barbudreadmon]

@thestarglider with the latest commits, you can get the tires to squeal.
NB : this is on FBNeo, you'll need to update your RP setup script and build the "new" core from source to get it.

[thestarglider]

@barbudreadmon Okay so I updated FBAlpha to FBNeo, played the game, it's close but still not 100%. Yes the car now steers a bit better, but it's still not quite there in regards to strength of turn. For example when taking a fork in the road (and what happens depends on if you go left or right, I am using going right as an example here), yes the wheels skid and smoke when turning but the car is still moving a little too fast to the outside edge of the road. When you then hit the next turn before joining the next stage the car should only be drifting very very slowly to the other side of the road with no skidding. The car is drifting too much.

Another game that is suffering badly is Chase HQ. The car is barely controllable with analogue sticks, it hardly moves, and since the update, it's actually gotten worse.

I also tried adjusting the sensitivity range from 1-10 and it seems to have no effect to the turning ability of either Out Run or Chase HQ.

To show you what I meant, I have made a video for you, recordings from both FBNeo on the Pi to MAME64 on the PC (which is how I've always known the steering to be, and just how I remember it in the arcades - I even played on real hardware only a couple of weeks ago and it's the same).

Out Run slide comparison

I hope this helps.

[thestarglider]

@barbudreadmon oh and again, I still tested Fbalpha2012 and although the visual guide to the high low gears are not there, that still runs perfectly.

[barbudreadmon]

@thestarglider i pushed another commit an hour ago, it should be fine now.

[thestarglider]

@barbudreadmon Yup! Out Run is now absolutely perfect! Thank you!

Chase HQ is now back to slightly crap for turning, but I'm not too fussed about that - it was more of an alternative driving game to test the steering with! :D

[barbudreadmon]

@thestarglider said in How to increase steering sensitivity on lr-fbalpha:

Chase HQ is now back to slightly crap for turning

Thanks for the heads up

[barbudreadmon]

@thestarglider Waiting for your logs on github, in the first place if you don't visit github regularly, you probably shouldn't post issues there.

[thestarglider]

@barbudreadmon I tried earlier this evening pasting the logs to the github page but it wasn't working properly for me.

So the logs are here. It doesn't to me show anything wrong, but trust me, updating the emulator from source crashes the game. I also attach a screengrab of the game direct from my Pi, and also a video of the game failing to load.

https://pastebin.com/0E7MRfh2

Video - link text

[barbudreadmon]

@thestarglider I can't figure out your issue from your logs, so let's try this :

• delete your eeprom at /home/pi/RetroPie/roms/fba//fbneo/outrun.fs, it might be corrupted
• update your retroarch, there is a [INFO] Environ UNSUPPORTED (#65587). message
• make sure your outrun.zip and chasehq.zip aren't corrupted, basically they must be extractable : i've seen a few cases where the content of a romset could be scanned, saying the crcs are ok, but actually couldn't be read
• try using only "stock" settings (i.e. no raspberry overclock or anything else that might not be "standard")

Again, considering it wasn't happening on your previous sd card, and there was no change to those games since then, i don't see how it can be a core issue, i think there is something wrong with your new setup but idk what it is, i can only make blind guess.

PS : anyone can confirm outrun and chasehq work properly on retropie using latest FBNeo source ?

Edit : i found an old sd card to install retropie on my rpi3b+, i confirm your issue, this is weird, i'll investigate

[barbudreadmon]

@thestarglider fixed in my latest commit.

[thestarglider]

@barbudreadmon no worries! I'll update my end later after work and let you know.

[thestarglider]

@barbudreadmon Outrun now working :D Thanks!

[drylightn]

@thestarglider Slightly off topic here, but I see above you have a EasySMX Wireless 2.4ghz controller. Did you have to do anything special to get it to work with the RetroPie setup? When i got through the usual process of assigning buttons, everything works as expected till I get down to the trigger buttons, and neither one of them will register (so I have to skip them). If I plug the same controller into my windows 10 laptop, the trigger buttons seem to work just fine?

[thestarglider]

@drylightn assigning trigger buttons on Retropie with any controller is a bit of a bugger. Best thing to do is assign all your buttons and directions first, skip the triggers until you have assigned all the rest, but before saving, move back up to the triggers. Now try to assign them, and keep retrying until you get (from memory) a +AXIS for each one. That's very important, they must be a + and not a - otherwise they won't work properly.

It can take a few goes, because the triggers are feeding an analogue response to Retropie but you will get there eventually! Hope that helps! When I am on my Pi I will adjust this if I got it wrong, but from memory I'm pretty sure that's the way to get it working.