Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.
2026-11-14 · News and analysis
Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.
God of War: Ascension is the only God of War with multiplayer, and it is the one most people never played. Its servers are the reason: the game shipped in 2013, the mode was built around PlayStation Network, and the whole thing was tied to a console generation that has moved on.
So "the unofficial PC port has multiplayer now" is a very attractive sentence. It is also not quite what the project says, and the gap is worth a page of its own.
What the project documents is that going online, the terms screen, the warrior lobby, quick match, the matchmaking handshake, pairing two players with one as host, and relaying the match traffic all work. Every one of those steps is marked done. The two steps underneath them are not: a match between two PCs over the internet is in progress, and a whole match from the lobby to the end is still to do. The working pairing is annotated "two games on one PC".
Meanwhile, a different project working on the same game has done something nobody is writing about at all: it ran the campaign end to end on a handheld, and published the numbers.
Everything here assumes you are playing games you already own. We do not link to game files, key files, firmware, or dumping tools, and we do not explain how to obtain any of them.
The Short Version
- The game: God of War: Ascension, PlayStation 3, 2013, never released on PC
- Three separate projects are porting it by static recompilation. They are not forks of each other's work and they are at very different stages
- The online project has its own server and has brought up the entire sign in and matchmaking chain. Two clients pair and relay correctly on one machine. A real match between two PCs over the internet is listed as in progress, and a complete match as not started
- No release. That project has published no release at all; it is launcher driven and updated from source
- The handheld project is Windows stable with the full campaign played, and its Linux build runs on SteamOS through Proton. It was tested end to end on a Lenovo Legion Go S
- The handheld numbers: 46 to 49 fps at the opening at 15 W, an average of 48.0 over a 25 minute run, around 44 fps mid game, 65 to 68 fps at 30 W, and about 24 fps in heavy combat at 15 W with audio dropping out
- The third project is Windows only, single player by its own statement, and has not been tried on a Deck
- What you supply: your own disc copy. The 1.04 update and the PS3 system software are free downloads from Sony's own servers, which one project's tool fetches for you
- ARM and Android handhelds: no route. This is x86-64 output
What "Multiplayer" Currently Means
The project building online play publishes a step by step table of what works, which is the most useful thing any project in this scene can do. Here is the state of it.
Working: going online and the Online Pass check, the online configuration the game reads, the terms of use and a multiplayer profile stored per account, skipping the tutorial into the warrior lobby, quick match finding the player's location, quick match picking a matchmaking server, connecting to matchmaking over an SSL session, two players matched into one game with one as host, the match's traffic passing through the project's relay, and signing in and starting an online game from the launcher.
Not working yet: a match between two PCs over the internet, which is in progress. A whole match from the lobby through to the end, which has not been started.
The two lines that read as done but carry a note are the important ones. Both the pairing and the relay are marked "ok (two games on one PC)". Two copies of the game on one machine matching with each other proves the handshake, the lobby and the relay path. It does not prove that two people in two houses can fight each other, because the hard parts of that are the ones a single machine never exercises.
The technical approach is interesting and explains why the last step is the hard one. The game's original netcode is a peer to peer mesh over UDP. Two players at home can rarely reach each other directly, each sitting behind a router, so the project passes the packets through a relay on its own server and the game does not notice. Getting that to work across two real connections, with two routers and real latency, is a different problem from getting it to work over a loopback.
The project is also careful about something worth noting: its server does not pose as Sony. It answers only what the game expects, derived from the translated code and from captures of the game talking to the original service. Playing offline is explicitly promised to keep working, and the campaign will never ask for an account.
So the fair description today is that online play is close and not finished, and anybody installing this expecting to fight a friend tonight will be disappointed. We would rather say that than repeat a headline.
The Three Projects, and Which One You Want
These are separate efforts on the same game, and conflating them is the easiest mistake to make here.
The online project is the one with the server, the accounts and the matchmaking work. It targets the European disc. Its campaign has been beaten start to finish on a very strong desktop. On an ordinary processor it is slow: around 20 fps in the boss fight on a Ryzen 7 5700G. It has published no release, so running it means building from source with its launcher. Since early November it has changed strategy, moving the PS3's SPU and graphics work into native PC and GPU code rather than emulating those parts better, with the stated goal of no SPU emulation at all.
The handheld project is the one to install if you want to play. It targets the US disc, its Windows build is described as stable with the full campaign played, and it is driven by a launcher that downloads the port, builds the game on your machine and keeps it updated. It ships roughly six updates a day. Its Linux build has been in beta since a launcher release in November and runs on SteamOS through Proton.
The third project is a Windows alpha. It boots, plays cinematics and gets into levels, and has not been played start to finish. It says plainly that online is not supported and the port is single player. It has a launcher with presets, FSR scaling and frame generation, and a cheat menu. The Steam Deck has not been tried; one player reports running it on Linux through a Wine prefix.
All three build on the same underlying PS3 recompilation toolkit, which is why three projects on one game appeared within weeks of each other. The same lineage effect produced the sudden wave of PS4 ports we wrote about in the PS4 and PS5 recompiled games list.
The Handheld Result Nobody Is Reporting
The handheld project maintains a bench page for its Linux build, on a Lenovo Legion Go S. This is the first time a PS3 recompilation has published handheld numbers at all, which is why it matters more than the online story.
The setup: a Legion Go S with a Ryzen Z1 Extreme and Radeon 780M, SteamOS 3.10, a GE-Proton build, the portable AVX2 build of the port, six SPU threads, 720p internal resolution, and the 60 fps limiter off. Each figure is 15 samples of five seconds from a checkpoint.
| Scene | TDP | Frame rate |
|---|---|---|
| Opening of the game, three runs | 15 W | 46 to 49 fps |
| Opening, one 25 minute run | 15 W | 48.0 average, 42.7 minimum, no drift over time |
| Two mid game checkpoints | 15 W | Around 44 fps, minimum 39 to 41 |
| The same two checkpoints | 30 W | 65 to 68 fps, and a flat 60 with the limiter on |
| Heavy combat with many enemies | 15 W | Around 24 fps, with audio dropping out |
Three things to take from that.
A 25 minute run with no drift is the figure to trust. Short benchmark bursts hide thermal behaviour. An average of 48.0 with a 42.7 minimum over 25 minutes on a 15 W handheld is a genuinely playable result for a 2013 PS3 game.
Heavy combat is the wall, and the project knows it. Around 24 fps with audio dropouts is not playable, and the project has it under active work. Its own notes from 13 November report moving ten more graphics effects to native code for roughly 15 percent more frame rate on a 15 W handheld, plus a fix that cut audio dropouts from 83 to 98 occurrences in six minutes down to 32 to 34 on a deliberately limited processor. So the number in that bottom row is the one most likely to be out of date by the time you read this.
Thirty watts changes the game. At 30 W the same scenes hold 60 fps with the limiter on. That is the familiar handheld trade: this is playable on battery and comfortable plugged in.
A detail worth recording: the project checked whether heavy combat was a memory problem and found it was not, with 2.6 GB of 8 GB of video memory in use. The slowdown has another cause, which they say they are still chasing. That is the kind of note that makes a bench page worth reading.
Which Handhelds Can Actually Run It
| Device type | God of War: Ascension ports | RPCS3 emulation |
|---|---|---|
| SteamOS handhelds (Legion Go S, Steam Deck) | Yes, in beta, through Proton. Tested end to end on a Legion Go S | Demanding, and this game is one of the harder ones |
| Windows handhelds | Yes. The Windows build is the stable one | Demanding |
| Android handhelds | No. x86-64 output, no ARM build, none planned | Early and limited |
| Linux ARM handhelds | No | Not supported |
The Steam Deck deserves one specific note. The handheld project's Linux build is listed as supporting SteamOS generally, and the device it actually measured is a Legion Go S. A Deck is a weaker machine than a Z1 Extreme at the same wattage, so expect lower numbers than the table above, and treat the Deck as untested until somebody publishes figures for it.
If PS3 games on an ARM handheld is the goal, nothing here helps and the route is emulation. We cover it in PS3 emulation on handhelds and PS3 emulation on Android handhelds.
A Note on Numbers in This Scene
One detail from the online project is worth holding onto as a general lesson.
On 9 November it found that its own Vulkan renderer's frame counter had been counting every frame twice, because the same frame was being presented again a millisecond later with nothing drawn into it. Every performance figure that project had published from that renderer was therefore double the real value, and it said so in its own notes.
That is a project behaving well. It is also a warning about this entire category. A recompiled port's frame rate figures usually come from the person who wrote the port, measured with tools they also wrote, in scenes they chose. Most of them are honest. None of them is an independent benchmark, including the handheld numbers higher up this page, which are the project's own.
We have not benchmarked any of these ports, and we will say so every time.
What You Need to Play
- Your own disc copy of the game. The projects target different releases: one the European disc, one the US disc, one the digital US version. Check which before you start
- The 1.04 update and PS3 system software, both free from Sony's own servers. One project's tool downloads them for you
- About 35 GB free during the build on the handheld project, which extracts your copy once
- A build step on your machine, because no project can distribute the game's code. The launcher handles it
- An x86-64 processor. The handheld project builds for AVX-512 or AVX2 where available and falls back to a slower compatible build otherwise
No project ships game content, and we do not help with obtaining it.
What to Watch Next
- A match between two PCs over the internet. That is the line that turns "multiplayer works" from a lab result into a feature, and it is the one still in progress.
- Steam Deck numbers, as opposed to Legion Go S numbers. The Deck is the device most readers own and it is weaker at the same power budget.
- Heavy combat performance, which is the only genuinely unplayable result on the handheld bench page and the thing the project is working on right now.
- Whether the three projects converge. Three efforts on one game, all built on the same toolkit, is a lot of duplicated work, and this scene has a history of that resolving suddenly.
Frequently Asked Questions
Does the God of War: Ascension PC port have multiplayer?
Not yet, in the sense most people mean. The project building online play has brought up sign in, the lobby, matchmaking and its own relay, and has matched two players successfully with both copies running on one PC. A match between two separate machines over the internet is listed as in progress, and a complete match from lobby to end has not been started. The other two projects have no online play, and one of them states it is single player only.
Can I download it and play?
From one of the three projects, yes. The project with the stable Windows build is launcher driven: the launcher downloads the port, builds the game from your own disc copy and keeps it updated. The project doing the online work has published no release at all and must be built from source. The third is a Windows alpha.
Does it run on a Steam Deck?
Its Linux build runs on SteamOS through Proton and is in beta. The device the project actually measured is a Lenovo Legion Go S, not a Deck, and a Deck is weaker at the same wattage, so expect lower figures. Nobody has published Deck numbers for this port yet.
What frame rate does it get on a handheld?
On the project's own Legion Go S bench, 46 to 49 fps at the opening at 15 W, an average of 48.0 over a 25 minute run, around 44 fps mid game, and 65 to 68 fps at 30 W. Heavy combat with many enemies drops to around 24 fps at 15 W with audio dropouts, which is the scene the project is currently optimising. These are the project's figures, not ours.
Is it an emulator?
No. The PS3's main processor code and its SPU code are translated to C or C++ ahead of time and compiled for x86-64, so the game runs natively. One project still draws through a renderer borrowed from the RPCS3 project while its own Vulkan renderer matures, which is a graphics path rather than emulation of the processor.
Do I need the original game?
Yes, a disc copy, and which release depends on the project. The 1.04 update and the PS3 system software are free downloads from Sony and one project's tool fetches them automatically. No project includes game data.
Can I play it on an Android handheld or a Retroid?
No. All three projects produce x86-64 programs and Android handhelds are ARM. There is no ARM build and nobody is working on one.
Why are there three projects on the same game?
All three are built on the same PS3 recompilation toolkit, which lowered the barrier enough that several people started independently within weeks of each other. The same pattern produced a cluster of PS4 ports earlier this year. It usually resolves as one project pulls ahead.
Is this legal?
The projects distribute no game code and no game data, and require you to supply your own copy, which is the same position every port in our recompiled games list occupies. The online project's server answers only what the game expects and does not present itself as Sony's service. None of that is a guarantee against a rightsholder objecting.
Related Reading
- PS3 Recompiled Games List: What Actually Runs So Far — the running index, now with downloads in it
- Demon's Souls Runs Natively on PC — the other PS3 port that moved this month, and the one with a native Linux build
- PS4 and PS5 Recompiled Games List — the same shared toolkit effect on a different console
- Recompiled Games List: Every Native Port by System
- PS3 Emulation on Handhelds
- PS3 Emulation on Android Handhelds
- Best Handhelds for PS3 Emulation
- Best PS2 Games on a Handheld — where the rest of the series sits today
- Decompilation and Recompilation Explained
Written 14 November 2026 from the three projects' own READMEs, milestone files, release notes and bench pages. All performance figures are the projects' own; we have not benchmarked any of them. These projects publish daily, one of them several times a day, so the online status table and the handheld numbers here will date quickly. Corrections are welcome and this page will be dated again rather than quietly rewritten.

