libretro / libretro/RetroArch

issue: neogeo games 40fps ? i have updated 1.0.0.3 for linux armhf

Open
#18,882 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Is there an existing issue for this?
  • This is a bug in RetroArch frontend
  • I have searched the existing issues
Description

hello , i get last update fbneo1.0.0.3 last build exclusivly from here foe my gamestick 4k
linux (armfh cpu , armv7 neon hf ),

https://rparadise-team.github.io/Koriki/armhf/fbneo_libretro.so.zip
i run all romhacks 2026 fine
by disable these settings and save
force 60hz "disable"
disable cyclone
disable sampleinterpolation
disable FMinterpolation
and all roms 2026 work
but same as offical version games run only 40 fps , drops framerates any help to fix that

regards,

Expected behavior

No response

Steps to reproduce the bug

force 60hz "disable"
disable cyclone
disable sampleinterpolation
disable FMinterpolation
and all romshack 2026 run on linux armfh
but drop framerate to 40fps
restart the game fix huge lag but still 40 fps
change settings not help

Version/Commit

1.7.4

Bisect Results

No response

Present in the nightly version

Yes, this is reproduced in the nightly build

Platform & operating system

linux armfh

Affected Cores

No response

Environment information

No response

Relevant log output

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported 40 FPS behavior on Linux armhf with RetroArch 1.7.4 and the linked FBNeo 1.0.0.3 build, using the listed settings and comparing the official version with the ROM hacks. Collect relevant logs and frame-timing information, then determine what changes are needed for the games to maintain 60 FPS.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
frontend, operating-systems, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.