You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This affects Doom (II) and Duke Nukem Advance. I didnt test other Torus games yet.
While the rest 3D games (VRally 3, GBA NFS demakes and such) run reasonably on weak devices, Doon 2 and DNA have horrendous speed issues, to the point where these games are unplayable without heavy frameskip. That happens even on mobiles devices with 4 Cortex-A7 cores and Mali GPU. Stronger dvices run these games fine, but considering other 3D GBA games run perfectly fine, one would expect Torus' software to run as well, which makes me suspect its some kind of an emulator issue.
Sorry if its invalid, or a libretro specific issue.
The text was updated successfully, but these errors were encountered:
freq-mod
changed the title
Torus Games's GBA games have a noticeable slowdown
[ARM] Torus Games's GBA games have a noticeable slowdown
Dec 26, 2023
endrift
added
the
pending
This issue needs more investigation by a maintainer to triage appropriately
label
Jan 7, 2024
This appears to just be the game using more CPU time. I've tried to optimize it some, but none of that seemed to pan out. While I do want to improve performance in the long run, that's broad and not to a schedule. As such, this bug isn't, well, a bug.
This affects Doom (II) and Duke Nukem Advance. I didnt test other Torus games yet.
While the rest 3D games (VRally 3, GBA NFS demakes and such) run reasonably on weak devices, Doon 2 and DNA have horrendous speed issues, to the point where these games are unplayable without heavy frameskip. That happens even on mobiles devices with 4 Cortex-A7 cores and Mali GPU. Stronger dvices run these games fine, but considering other 3D GBA games run perfectly fine, one would expect Torus' software to run as well, which makes me suspect its some kind of an emulator issue.
Sorry if its invalid, or a libretro specific issue.
The text was updated successfully, but these errors were encountered: