How to increase steering sensitivity on lr-fbalpha

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

alt text

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.

drylightn

@thestarglider How do you move back up to the triggers when doing the joystick config from emulation station? Far as I can tell you can only skip by holding down the A button? Or are you configuring them somewhere else?

I'm pretty sure on my old wired xbox style controllers the triggers assigned just fine. No matter how many times I've restarted the joystick config from emulation station, and no matter how many times a pull the trigger, it doesn't even attempt to assign them.

thestarglider

@drylightn I just tested it myself and what I suggested is still correct. And you should be able to skip with any button on the controller, but that's isn't too important - that you can skip is.

Once you have configured every other controller but before you confirm the controls at the very bottom, use the D pad to move back up to the triggers. Then try to assign the trigger buttons, ensuring that they are set to +AXIS (Mine shows up as 2 and 5 for left and right triggers respectively).