Rolling Thunder on FB Neo Core Unresponsive

General
#1

Hi have noticed that whilst playing Rolling Thunder on the FB Neo core with RA stable build 1.20.0 the controls can be unresponsive randomly, for example pressing the fire button sometimes wont actually register or pressing down and the character wont ducking for example

I have tried the standalone nightly FB Neo emulator and this issue isn’t present so it does appear to be a Retroarch issue. I have tired a fresh install of RA 1.20.0 and have just updated Assets, Controller Profiles, Cheats Databases, Overlays, Shader and of course the FB Neo core I have not altered any other settings what so ever from a fresh install and still notice Rolling Thunder being unresponsive.

Has anyone else come across this issue at all??

#2

Try going to settings > latency and set the ‘polling behavior’ to “normal” or “early” instead of “late”. I don’t know if this will help, but it’s a good first thing to check if inputs are being weird or not happening at all with a specific core.

2 Likes
#3

I’ll give it a try but not sure if it will work as the missed inputs doesn’t happen all the time just now and again

#4

Ok, have tried both Normal and early for polling behaviour but it does not seem to fix the issue sadly

#5

Is your controller a bluetooth one? If so, can you test using a wired one? I’ve seen some pretty weird behavior with RetroArch and bluetooth, sometimes.

#6

I may be way off on this, but is FB Neo based on a very old MAME? Rolling Thunder was one of the later games to be added. Not sure if this is even remotely helpful, but it ocurred to me when I read this.

#7

Im using an xbox series pad over 2.4ghz so not bluetooth. As said i dont notice this issue with the standalone FB Neo emulator

#8

I don’t think so, as said I have tried the game on the standalone FB Neo emulator and its absolutely fine there

#9

Then, if it happens only with that game, I suggest opening an issue here: https://github.com/libretro/FBNeo/issues

It may be some regression and the devs might help you better.

#10

Yeah, that would seem to shoot that idea.

#11

I don’t think FBNeo has any relation to MAME, other than using similar ROMsets.

#12

Have opened a case, let’s see what they say.

I haven’t noticed the issue with other games on FB Neo in the past but noticed it with Rolling Thunder before completing the first stage, just noticed the movement of the character just seemed ‘off’ and slightly unresponsive.

I wonder if the issues is there will other namco games that use the same driver as rolling thunder, it would seem odd just to be isolated to just one game no?

1 Like
#13

I’ve checked and they’re working on it. Meanwhile, one of the devs suggested “does using the force 60hz core option fix the problem for you ?” You could try that and see if it helps you.

#14

Yeah i tried that, it was set to 165hz so changed it to 60hz but sadly did not fix the issue

#15

Thanks to, dinkc64 & barbudreadmon over on FB Neo github the issue has now been resolved!!!

2 Likes