Repository navigation
Infinite loading screen on area transitions (tracking) #1131
Description
EN:
This issue gathers every report of a loading screen that never ends (the Omega icon keeps spinning, the game keeps rendering, the next area never arrives). Please post here from now on.
Reports so far
| Where in the game | WAD in the log | Open | Earlier reports |
|---|---|---|---|
| After Poseidon | #1065 | #565 | |
| Helios, hidden door | Bas400 | #982 | #701 |
| Caves (Medusa) | Cav500 / Cav600 | #1047 | #296, #636 |
| Before and inside the Forge | Hds500 | #987 | #428, #586, #781 |
| Chamber of the Flame, spiral stairs | #809 | ||
| After Hades (HADESDEATH) | Hds690 | #345, related #1024 | |
| Heart of Gaia / end of the chain | Pos700? | #990 | #433 |
| After Hercules | #723 |
What we know
- The logs show the same signature:
WAD_STATS: WAD <name> allocfor the next area, and never thefSizeline that every finished load prints. - It happens on NVIDIA, AMD, Windows and Linux, on CUSA01623 and CUSA01715, from v2.2.0 to v2.7.0.
- In Hang after Hades boss: WAD Hds690 load never completes (no file reads during hang) #345 the whole Hds690.WAD file was read without errors (98,197,264 bytes), and the load still did not finish.
- In Não consigo passar do Helios #701 the reporter fixed it by extracting the game again, because files were missing after the first extraction.
- These areas load normally on our test install (CUSA01623 01.00). So the first step is to compare your game files with a working install.
How to help (5 minutes, nothing is uploaded or changed)
- Download
game_manifest.py. It only reads your game folder. - With Python 3, in PowerShell:
python -I game_manifest.py create "<your game folder>" -o current.json - Post a comment here with:
current.jsonattached (file names, sizes and SHA-256 hashes only; no game data and no full folder path)- where the game gets stuck
- CUSA and update version (01.00 or 01.02), port version, GPU and driver
- your
user/last_run.logfrom a run that got stuck (copy it before you start the game again)
If you got past one of these areas without problems, your manifest helps too, especially on CUSA01715. Please post it with your CUSA and update version.
Please do not attach game files or saves. We will attach the manifest of our working 01.00 install for comparison.
PT-BR:
Esta issue reúne todos os relatos de tela de carregamento que nunca termina (o ícone Omega continua girando, o jogo continua renderizando e a próxima área nunca chega). Por favor, poste aqui daqui em diante.
Relatos até agora
| Onde no jogo | WAD no log | Aberta | Relatos anteriores |
|---|---|---|---|
| Depois do Poseidon | #1065 | #565 | |
| Helios, porta escondida | Bas400 | #982 | #701 |
| Cavernas (Medusa) | Cav500 / Cav600 | #1047 | #296, #636 |
| Antes e dentro da Forja | Hds500 | #987 | #428, #586, #781 |
| Câmara da Chama, escada em espiral | #809 | ||
| Depois do Hades (HADESDEATH) | Hds690 | #345, relacionada #1024 | |
| Coração de Gaia / fim da corrente | Pos700? | #990 | #433 |
| Depois do Hércules | #723 |
O que já sabemos
- Os logs mostram a mesma assinatura:
WAD_STATS: WAD <nome> allocda próxima área, e nunca a linhafSizeque todo carregamento concluído imprime. - Acontece em NVIDIA, AMD, Windows e Linux, no CUSA01623 e no CUSA01715, da v2.2.0 à v2.7.0.
- Na Hang after Hades boss: WAD Hds690 load never completes (no file reads during hang) #345 o arquivo Hds690.WAD foi lido inteiro sem erros (98.197.264 bytes), e mesmo assim o carregamento não terminou.
- Na Não consigo passar do Helios #701 o relator resolveu extraindo o jogo de novo, porque faltavam arquivos depois da primeira extração.
- Essas áreas carregam normalmente na nossa instalação de teste (CUSA01623 01.00). Por isso o primeiro passo é comparar os seus arquivos com uma instalação que funciona.
Como ajudar (5 minutos, nada é enviado nem alterado)
- Baixe o
game_manifest.py. Ele só lê a pasta do jogo. - Com Python 3, no PowerShell:
python -I game_manifest.py create "<pasta do jogo>" -o atual.json - Poste um comentário aqui com:
- o
atual.jsonanexado (só nomes, tamanhos e hashes SHA-256; sem dados do jogo e sem o caminho completo da pasta) - onde o jogo trava
- CUSA e versão da atualização (01.00 ou 01.02), versão do port, GPU e driver
- o
user/last_run.logde uma execução que travou (copie antes de abrir o jogo de novo)
- o
Se você passou por uma dessas áreas sem problema, o seu manifesto também ajuda, principalmente no CUSA01715. Poste com a CUSA e a versão da atualização.
Por favor, não anexe arquivos do jogo nem saves. Vamos anexar o manifesto da nossa instalação 01.00 que funciona para comparar.
Activity
FelipePrado0 commentedon Oct 30, 2026
EN:
A test build is ready: windows-v2.8.0-issue1131-test1 (Windows zip and Linux AppImage).
It has memory fixes that are not in 2.7.0 yet (#1005), texture cache and GPU fixes for cards with less than 8 GB (#1124), and a log that shows where a load stops. It may already fix the hang for some of you.
How to test (about 10 minutes):
$env:SPARTAN_FILE_TRACE="1"; $env:SPARTAN_LOAD_WATCHDOG="30"; & ".\SpartanPort.exe"user/last_run.log(copy it before starting the game again).The game file check from the first post (
game_manifest.py) still helps, especially if the build does not fix it for you.@Azaberth @SyedRayyan0 @saitamashiop-stack @jacopolucchini35-boop @lainiwakura292 @vggamer101supremo @yuridam @AndreiSantanaK20 @xdk100k @Dineshscet @marcos010203 @sahilthorve18 @Tgo1014 @midun232005-afk @SAM221109 @rafaelontour @LamShiiKi @khiss0959-gif @animelegend094-sketch
@brunoweierich-ctrl, in #296 you saw copy threads stuck while others waited, and said you were working on a fix. Did you find the cause? Any detail helps.
PT-BR:
Uma build de teste está pronta: windows-v2.8.0-issue1131-test1 (zip para Windows e AppImage para Linux).
Ela traz correções de memória que ainda não estão na 2.7.0 (#1005), correções de cache de texturas e de GPU para placas com menos de 8 GB (#1124) e um log que mostra onde o carregamento para. Ela pode já resolver o travamento para alguns de vocês.
Como testar (cerca de 10 minutos):
$env:SPARTAN_FILE_TRACE="1"; $env:SPARTAN_LOAD_WATCHDOG="30"; & ".\SpartanPort.exe"user/last_run.log(copie antes de abrir o jogo de novo).A verificação dos arquivos do jogo do primeiro post (
game_manifest.py) continua ajudando, principalmente se a build não resolver para você.@brunoweierich-ctrl, na #296 você viu threads de cópia presas enquanto outras esperavam, e disse que estava trabalhando numa correção. Chegou a encontrar a causa? Qualquer detalhe ajuda.
jacopolucchini35-boop commentedon Oct 31, 2026
Still hangs on windows-v2.8.0-issue1131-test1 (SPARTAN_FILE_TRACE=1, SPARTAN_LOAD_WATCHDOG=30).
Where: City of Olympia, the transition into the Helios area (WAD Bas400). Loading the autosave there hangs every time.
What the trace shows: BAS400.WAD is opened and read completely by SceFiosIO (1081 preads, 165412864/165412864 bytes, all errno=0). No close follows, and nothing else happens. After 30 s the watchdog reports "Load: STALL no file progress for 30 s". SceFiosCallback and the Copy0-3 threads show no CPU change between samples. The WAD_STATS line for Bas400 shows alloc/ax8, but never fSize.
Game: CUSA01715, update 01.02. Manifest attached (current.json, 12070 files, 0 unreadable). BAS400.WAD sha256 700a3f7c50370c5c984dd2fa5ddec1932524a8add8b96aeb8daa46bc7a48a787.
Also hangs the same way on 2.5.0, 2.6.0 and 2.7.0 (previously #701). FPS 60/120 and deferred_readback/stale_readback/async_shaders off made no difference.
System: Windows 11 Pro, Ryzen 7 8700F, RX 9070 XT (driver 32.0.31041.1004), 32 GB RAM, native 1920x1080 borderless.
last_run.log (copied while the game was still hung) and current.json attached.
last_run_helios_test1131.log
current.json
FelipePrado0 commentedon Oct 31, 2026
EN:
@jacopolucchini35-boop thank you, this is exactly what we needed.
Your file list matches our working install in every game WAD except one:
BAS400.WAD, the Helios area that hangs. Yours is 165,412,864 bytes, ours is 380,330,752 bytes (CUSA01623 01.00). All other 412 WADs are identical.So the problem is very likely this one file, either broken during extraction or replaced by the update. Could you:
BAS400.WAD, and its size.EXEC/WAD/PS4_LE/BAS400.WAD.Everyone with update 01.02 who got past Helios: please tell us the size in bytes of
EXEC/WAD/PS4_LE/BAS400.WADin your game folder, and your CUSA. One number is enough.PT-BR:
@jacopolucchini35-boop obrigado, era exatamente o que precisávamos.
A sua lista de arquivos é igual à da nossa instalação que funciona em todos os WADs do jogo, menos um:
BAS400.WAD, a área do Helios que trava. O seu tem 165.412.864 bytes, o nosso tem 380.330.752 bytes (CUSA01623 01.00). Os outros 412 WADs são idênticos.Então o problema muito provavelmente é esse arquivo, quebrado na extração ou substituído pela atualização. Você poderia:
BAS400.WAD, e o tamanho dele.EXEC/WAD/PS4_LE/BAS400.WAD.Todos com a atualização 01.02 que passaram do Helios: por favor, informem o tamanho em bytes de
EXEC/WAD/PS4_LE/BAS400.WADna pasta do jogo, e a sua CUSA. Um número basta.jacopolucchini35-boop commentedon Oct 31, 2026
Tgo1014 commentedon Oct 31, 2026
For it me still loads forever going up the chain. Log attached.
last_run.log
saitamashiop-stack commentedon Oct 31, 2026
Hii i tried the game on the Test build issue1131-test1 and still has infinite loading screen when trying to enter the forge in realm of hades.
last_run.log
also i must add my game version is cusa01623 . version 01.02
my pc specs :
i5 14600k
rtx 4070ti super
32 gb ddr5 ram 6000mzh
2 remaining items
xdk100k commentedon Oct 31, 2026
Infinite Loading at Omega Logo After Poseidon Fight (CUSA01715, Update 01.02)
Hi SpartanPort developers,
I'm experiencing an infinite loading issue after defeating Poseidon in God of War III Remastered. The game gets stuck on the Omega logo when transitioning to the next area (Hades / River Styx).
System specifications:
What happens:
Log observations:
Additional information:
I've attached my "last_run.log" for investigation.
Could you please investigate whether this is a GPU command processing hang or a game-specific compatibility issue?
Thank you!
last_run.log
sahilthorve18 commentedon Oct 31, 2026
Just unistall the game file and reinstall it your saves doesn't get lost dw it will work then
FelipePrado0 commentedon Oct 31, 2026
EN:
@xdk100k thank you. Your log has no
Load:lines, so the diagnostics were off. Please start the game from PowerShell with step 3 of the test post ($env:SPARTAN_FILE_TRACE="1"; $env:SPARTAN_LOAD_WATCHDOG="30"; & ".\SpartanPort.exe"), wait one minute on the hang and send the newuser/last_run.log. The GPU thread at 99.6% is normal; it runs like that on working installs too.@jacopolucchini35-boop xdk100k has the same CUSA01715 01.02 eboot as you, and his BAS400.WAD is about 362 MB, the same as ours. Yours is 165 MB, so it is very likely incomplete. Please extract the game and the update again into an empty folder and check the size of
EXEC/WAD/PS4_LE/BAS400.WADbefore trying Helios again.PT-BR:
@xdk100k obrigado. O seu log não tem linhas
Load:, então o diagnóstico estava desligado. Abra o jogo pelo PowerShell com o passo 3 do post de teste ($env:SPARTAN_FILE_TRACE="1"; $env:SPARTAN_LOAD_WATCHDOG="30"; & ".\SpartanPort.exe"), espere um minuto no travamento e mande o novouser/last_run.log. A thread da GPU a 99,6% é normal; ela roda assim também em instalações que funcionam.@jacopolucchini35-boop o xdk100k tem o mesmo eboot CUSA01715 01.02 que você, e o BAS400.WAD dele tem cerca de 362 MB, igual ao nosso. O seu tem 165 MB, então muito provavelmente está incompleto. Extraia de novo o jogo e a atualização numa pasta vazia e confira o tamanho de
EXEC/WAD/PS4_LE/BAS400.WADantes de tentar o Helios de novo.xdk100k commentedon Oct 31, 2026
Still hangs on the test build. Both of my logs end at the same WAD:
HadesBlue.Setup: Windows, NVIDIA GTX 1060 6GB, driver [driver version], CUSA01715 update 01.02, port version [port version]. I launched it from PowerShell with
SPARTAN_FILE_TRACE=1andSPARTAN_LOAD_WATCHDOG=30.Log 1 (first attempt, loading my existing save): right after the save loads,
WAD HadesBlueprintsalloc/ax8three times and never prints thefSizeline. Session length about 632 s.Log 2 (PowerShell run, new game with no save): I played through the opening and the Poseidon fight. Pos600, Pos650, Pos700, Pos800, Pos900 and Pos950 all finished normally (
fSizeprinted). Right after Pos950,WAD HadesBlueagain printsalloc/ax8three times with nofSize. Then AutoSave starts and thePSDNDEATHcinematic starts, and nothing else loads after that. Session length about 1414 s.Other things I noticed in the logs:
GpuCommandProcessoris at about 97-99% of one thread in both runs.GPU: copy waits yielded 204653 times.live=5656018944ofbudget=7449083904in both runs.I don't see any watchdog or file-trace lines in either
last_run.log. Should they appear in that file, or is the output written somewhere else?HadesBlueis not in the table in the first post, and it is where both of my hangs end. Both logs are attached. I can also post thegame_manifest.pyoutput if that helps.PT-BR (resumo): Ainda trava na build de teste. Os dois logs terminam no mesmo WAD,
HadesBlue, comalloc/ax8três vezes e sem a linhafSize. GTX 1060 6GB, CUSA01715 01.02. Não vejo linhas de watchdog nem de file trace nolast_run.log.last_run.log
FelipePrado0 commentedon Oct 31, 2026
EN:
@xdk100k thank you, the HadesBlue hang right after Pos950 on both runs is very useful. Your log still has no
Load:lines, so the diagnostics did not run. Please check two things:SpartanPort.exefrom the folder where you extracted the test2 zip, not from your old install or a shortcut.$env:SPARTAN_FILE_TRACE="1"; $env:SPARTAN_LOAD_WATCHDOG="30"; & ".\SpartanPort.exe"When it works,
user/last_run.loghas lines starting withLoad:. Wait one minute on the hang before closing. With that we can see where the game stops on HadesBlue.PT-BR:
@xdk100k obrigado, o travamento no HadesBlue logo depois do Pos950 nas duas tentativas ajuda muito. O log ainda não tem linhas
Load:, então o diagnóstico não rodou. Confira duas coisas:SpartanPort.exeda pasta onde você extraiu o zip da test2, não da instalação antiga nem de um atalho.$env:SPARTAN_FILE_TRACE="1"; $env:SPARTAN_LOAD_WATCHDOG="30"; & ".\SpartanPort.exe"Quando funcionar, o
user/last_run.logterá linhas começando comLoad:. Espere um minuto no travamento antes de fechar. Com isso dá para ver onde o jogo para no HadesBlue.Tgo1014 commentedon Nov 1, 2026
New log with the second build running, still stuck flying up the chain.
last_run.log
saitamashiop-stack commentedon Nov 3, 2026
ok today i tried the game with latest build release of the port v3.0.0 loaded my manual save from the three judges, played all the way through till im about to enter the forge but still it got stuck on infinite loading screen. Here is the log from my run. Pls look into it i really wanna play this game
last_run.log.txt
SyedRayyan0 commentedon Nov 3, 2026
saitamashiop-stack commentedon Nov 3, 2026
did it work before v 2.3.0?
SyedRayyan0 commentedon Nov 3, 2026
FelipePrado0 commentedon Nov 10, 2026
EN:
@saitamashiop-stack thanks for the log. It stops while loading the Hades area before the Forge, with the engine at 120 FPS and no error. Please update to 3.1.0, set the engine frame rate to 60 FPS, load your manual save and try again. Tell us if it passes, and send the new
user/last_run.logif it doesn't.PT-BR:
@saitamashiop-stack obrigado pelo log. Ele para enquanto carrega a área de Hades antes da Forja, com o motor a 120 FPS e sem erro. Atualize para a 3.1.0, coloque a taxa de quadros do motor em 60 FPS, carregue o seu save manual e tente de novo. Diga se passa e mande o novo
user/last_run.logse não passar.saitamashiop-stack commentedon Nov 10, 2026
Hii @FelipePrado0 so yeah i tested the game in the new update with engine frame rate limited to 60 fps and loaded the manual save played till the forge entrance and it still gets stuck on loading screen. Here is the log of the last run.
last_run.log.txt