Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List of games that are broken on ARM64 but work on x64 builds #16484

Open
1 of 5 tasks
mavethee opened this issue Dec 31, 2024 · 20 comments
Open
1 of 5 tasks

List of games that are broken on ARM64 but work on x64 builds #16484

mavethee opened this issue Dec 31, 2024 · 20 comments
Assignees

Comments

@mavethee
Copy link

mavethee commented Dec 31, 2024

Quick summary

As advised by @kd-11, I'm making mega issue with games that have issues on ARM64 builds on macOS.
List will be expanded with time, if I've overlooked any title, feel free to report it here.

List of games I've tested:

CleanShot 2024-12-31 at 15 27 13@2x

CleanShot 2024-12-31 at 15 27 22@2x

If some isn't listed further, it doesn't have any issues related to ARM64 build specifically.

I've had issues with Ratchet and Clank Trilogy but that's covered by #16472,
The Journey Collection issues are caused by libvdec requirement - #14513,
Potencial Red Dead Redemption and GTA IV issues mentioned here, as it's not exclusive to ARM64 build. - #16495

Some games require multiple boots due to amount of cache or Stub PPU Traps: 1 in custom config's yml file.

Details

  1. TESTED FOR THIS ISSUE:
  • Red Dead Redemption: Game of the Year Edition [BLES01294]
    Crashes after cache compilation

    EDIT: Initially tested RDR, it was crashing with a Pad Thread, if you have same issue, switch to Keyboard handler or do not connect the controller until cache is compiled, issue seems to be gone on later runs. It can be reproduced by deleting the cache and issue is still present. You can downgrade to 1.0 to get rid of the issue.
    And unlike I thought, it's on both ARM64 and X64 build, so removing it from list.
  • Grand Theft Auto IV: Complete Edition [BLES01128]:
    Crashes on ARM64 after game selection (base game or DLCs), while on x64 build it loads just fine. I found only strange issue with Pad Thread, my DualSense crashes only in this game in same spot (Keyboard handler works fine).

    EDIT: it was crashing with a Pad Thread, if you have same issue, switch to Keyboard handler or do not connect the controller until cache is compiled, issue seems to be gone on later runs. It can be reproduced by deleting the cache and issue is still present. Downgrading to 1.0 doesn't solve it.
  • Heavenly Sword™ [BCES00078]:
    Black screen after pressing START GAME, not an issue on x64 build.
    image
    CleanShot 2024-12-30 at 18 27 51@2x
  • Ratchet & Clank: Tools of Destruction™ [BCES00052]:
    Crashes on loading existing save, haven't tested starting new game. On X64 build works fine.
    CleanShot 2024-12-30 at 21 15 53@2x
    CleanShot 2024-12-30 at 21 23 46@2x
  • Ratchet & Clank™: Quest For Booty [BCES00301]:
    Crashes while loading a save game, while on x64 build loads fine.
    CleanShot 2024-12-30 at 22 08 41@2x
    CleanShot 2024-12-30 at 22 16 08@2x
  1. ALREADY EXISTING:
  1. NOT ARM64 vs X64 RELATED:

Attach a log file

Attach capture files for visual issues

No response

System configuration

  • SYS: RPCS3 v0.0.34-17287-b16d267f Alpha | HEAD
  • SYS: Apple M1 (4P+4E) | 8 Threads | 16.00 GiB RAM | TSC: 0.024GHz | FMA3
  • SYS: Operating system: macOS, Version: 15.3.0
  • SYS: Current Time: 2024-12-30T23:03:40
  • RSX: Found Vulkan-compatible GPU: 'Apple M1' running on driver 0.2.995
  • SYS: Firmware version: 4.91

Other details

No response

@pstef
Copy link
Contributor

pstef commented Dec 31, 2024

Arm in general (as the title suggests) or specifically "Apple silicon"?
Oops, sorry, I must have missed the info in the title tag.

@kd-11 kd-11 changed the title [macOS] List of games that are broken on ARM64 but work on x64 builds List of games that are broken on ARM64 but work on x64 builds Dec 31, 2024
@kd-11 kd-11 self-assigned this Dec 31, 2024
@kd-11
Copy link
Contributor

kd-11 commented Dec 31, 2024

I've updated the title to make it more general. Typically if it's broken on macos arm64, it's also broken on linux arm64

@shinra-electric
Copy link
Contributor

shinra-electric commented Dec 31, 2024

Metal Gear Solid 4 BLES00246 (v2.00)

M1 Pro / Sequoia 15.2

Arm:
Shows the menu for an instant, then only displays a black screen. Music still plays, but the menu is not responsive.
Screenshot 2024-12-31 at 22 18 21

x86:
Menu works fine. Gets to the first in-game cinematic at least (probably gets further, didn't test).
Screenshot 2024-12-31 at 22 22 08
Screenshot 2024-12-31 at 22 36 24

Logs:

armRPCS3.log.gz

@shinra-electric
Copy link
Contributor

rain NPEA00394 v1.00

Arm:
Crash on boot
Screenshot 2024-12-31 at 23 02 51

x86:
Gets to menu (probably further, didn't test).
Screenshot 2024-12-31 at 23 09 09

Log:
rain_NPEA00394_arm.txt

@mavethee
Copy link
Author

@shinra-electric rain is related to #15982 which I've mentioned 😅

@mavethee
Copy link
Author

mavethee commented Jan 2, 2025

Initially tested RDR, it was crashing with a Pad Thread, if you have same issue, switch to Keyboard handler or do not connect the controller until cache is compiled, issue seems to be gone on later runs. It can be reproduced by deleting the cache and issue is still present.

And unlike I thought, it's on both ARM64 and X64 build, so removing it from list.

@mmkzer0
Copy link

mmkzer0 commented Jan 16, 2025

Gran Turismo 5 BCES00569 v02.07

M3 Pro:
Game Boots but crashes after displaying Logos with
F {PPU[0x100002a] Thread (n3FKY) [0x00aa07bc]} SIG: Thread terminated due to fatal error: Narrowing error (object: 0x10000000b)

Image

x86 through Rosetta works.

Log:
GT5_BCES00569_arm.txt

@mavethee
Copy link
Author

Gran Turismo 5 BCES00569 v02.07

Just for the record, v01.00 has exact same issue.

@FantasyGmm
Copy link

All of these games crashed on Linux 8Gen2, which I ran with the latest RPCS3 compilation

  • The Last of Us
    After compiling, you can enter the loading interface, but after waiting for about 1s, it will be stuck in the main and then RPCS3 display crashes.
  • Grand Theft Auto V
    The application crashes immediately after compilation, completely failing to enter the loading interface. This is accompanied by severe memory leaks that render the system unresponsive.
  • Assassin's Creed IV: Black Flag
    Same as GTA V.
  • Uncharted 3: Drake's Deception
    After compiling, you can enter the loading interface, but the loading icon in the lower right corner will get stuck after 5-8s of rotation.

@mavethee
Copy link
Author

All of these games crashed on Linux 8Gen2, which I ran with the latest RPCS3 compilation

ekhm, any logs? besides most games you mention require re-run due to amount of cache on first run, if it happends every boot, then it's an issue.

@FantasyGmm
Copy link

All of these games crashed on Linux 8Gen2, which I ran with the latest RPCS3 compilation

ekhm, any logs? besides most games you mention require re-run due to amount of cache on first run, if it happends every boot, then it's an issue.

I'm running it on a customized front-end based system, and I don't know how to get the logs yet, I may upload the logs for each game when I find a way to do it!

After compiling, I've tried running it straight away, restarting the emulator and running it again, even restarting the whole system and running it again, all with the same result, my machine only has 8 gigs of RAM but the game crashes before it runs out of that!

Image

@mavethee
Copy link
Author

After compiling, I've tried running it straight away, restarting the emulator and running it again, even restarting the whole system and running it again, all with the same result, my machine only has 8 gigs of RAM but the game crashes before it runs out of that!

RPCS3's Log file will be RPCS3.log.gz (sometimes shows as RPCS3.log with zip icon) or RPCS3.log (sometimes shows as RPCS3 wtih notepad icon).

On Windows it will be in the RPCS3 directory near the executable
On Linux it will be in ~/.cache/rpcs3/
On MacOS it will be in ~/Library/Caches/rpcs3. If you're unable to locate it copy paste the path in Spotlight and hit enter.

@mavethee
Copy link
Author

mavethee commented Feb 1, 2025

Gotta love this shitty reports from android folks 🥱
Proving you wrong as you fail to prove your point.
Tested on 506d921 due to #16646

So issues on newer builds are unrelated

GTA V

(requires Precise SPU Verification or last recommended by auto updater - 0.0.34-17413, see #16647):
Image
(Shitty perfs, cuz i refuse to kill my web browser eating shittone of resources, but boots, so that matters)

Logs:
GTAV_BROKEN.log
GTAV_WORKING.log

The Last of Us

Image
(this game ESPECIALLY requires a couple of boots to go ingame first time, so skill issue)

Logs:
TLOU_WORKING.log

Assassin's Creed IV: Black Flag

I don't have the game dumped (will edit this part when I do), but I assume I need to attach the corresponding issue it seems. But it just shows you don't follow RPCS3 Wiki recommended settings - #5831

Uncharted 3: Drake's Deception

(just as TLoU, needs a few attempts due to amount of cache)

Image

Logs:
U3_WORKING.log

@mavethee
Copy link
Author

mavethee commented Feb 1, 2025

For Mac users, ig - until #16646 is resolved, I would suggest testing on 0.0.34-17413 or 0.0.34-17414.

ISSUES RESOLVED

@kd-11
Copy link
Contributor

kd-11 commented Feb 2, 2025

Most of these are fixed with #16659

@mavethee
Copy link
Author

mavethee commented Feb 2, 2025

Most of these are fixed with #16659

Thanks, will remove that note, once #16659 get merged :D

EDIT:

Games using Unity engine now boot with latest master! Fix for GTA V is no longer needed too!

@shinra-electric
Copy link
Contributor

MGS 4 isn't fixed yet. Same issue as posted above.

@FantasyGmm
Copy link

FantasyGmm commented Feb 5, 2025

I'll add the other Logs as I find time.
I told you this would never work.

GTA V

It won't run, it's a LOG after starting it many times, each time it crashes at the end of the SPU compilation
Or maybe I just don't have that much RAM to launch the game, my device only has 8G RAM

·F 0:00:51.182236 {PPU[0x100000c] Thread ([RAGE] RenderThread) [0x00bdc798]} SIG: Thread terminated due to fatal error: Illegal instruction at 0000fffd3ca81804 (0x20e1182500e4006f62f1c03d0b008012).
Emu Thread Name: 'PPU[0x100000c] [RAGE] RenderThread'.

·! 0:00:51.198288 {PPU[0x100000c] [RAGE] RenderThread} SIG: Thread time: 0.129299s (0.000000Gc); Faults: 0 [rsx:0, spu:0]; [soft:67866 hard:0]; Switches:[vol:98 unvol:62]; Wait:[0.000s, spur:0]
·W 0:00:51.198381 SYS: CPU Thread 'PPU[0x100000c] [RAGE] RenderThread' terminated abnormally!

Logs:
GTAV_BROKEN.log

The Last of Us

Basically the same error reporting as GTA V, but crashes at the loading screen

·F 0:00:33.973310 {PPU[0x1000000] Thread (main_thread) [0x00c37c50]} SIG: Thread terminated due to fatal error: Illegal instruction at 0000fffd1092ae24 (0x20e1182528f97fd34aed7c92e9e7076f).
Emu Thread Name: 'PPU[0x1000000] main_thread'.

·! 0:00:33.983633 {PPU[0x1000000] main_thread} SIG: Thread time: 13.011802s (0.000000Gc); Faults: 0 [rsx:0, spu:0]; [soft:324339 hard:0]; Switches:[vol:760 unvol:7590]; Wait:[0.000s, spur:0]
·W 0:00:33.983850 SYS: CPU Thread 'PPU[0x1000000] main_thread' terminated abnormally!

Logs:
TLOU_BROKEN.log

Assassin's Creed IV: Black Flag

I'm able to get into the game with Interpreter (static), but it's extreme slow.

Image

It looks like a problem caused by LLVM recompilation, and ASMJIT Recompiler will directly cause RPCS3 to crash and become completely unusable. A lot of game crashes I've tested have been caused by this

@mavethee
Copy link
Author

mavethee commented Feb 5, 2025

@FantasyGmm You weren't taught comprehensive reading at school, are you? Get out with Black Flag, you won't boot it on LLVM with x64 build either, so it's not related like e.g XMB/VSH, read the first post for once.

Aside that, if i get my hands on proper Linux ARM machine, will be able to test as well. You're running android handheld with Linux that isn't main intent for this device, that brings unnecessary crap to the number of issues.

@shinra-electric
Copy link
Contributor

Heavenly Sword looks like it's not fixed either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants