RPCS3 Forums
Eternal Sonata [BLES00444] - Printable Version

+- RPCS3 Forums (https://forums.rpcs3.net)
+-- Forum: PS3 Commercial Games (https://forums.rpcs3.net/forumdisplay.php?fid=4)
+--- Forum: Ingame (https://forums.rpcs3.net/forumdisplay.php?fid=6)
+--- Thread: Eternal Sonata [BLES00444] (/showthread.php?tid=173627)

Pages: 1 2 3 4 5 6 7


RE: Eternal Sonata [BLES00444] - Ludvik - 07-23-2019

i5 9400f (not TSX supported), rtx 2070, 16Gb 3000mhz, Z390, nvme pcie x2:

PPU LLVM stable 30fps, but random crash.
PPU interpreter not random crash, but 15fps.

I think it's not yet playable...

(sorry for my english).


RE: Eternal Sonata [BLES00444] - Dawnbomb - 08-21-2019

just reporting in, still not playable / crashes.


RE: Eternal Sonata [BLES00444] - Hakj3r - 01-02-2020

RPCS3 v0.0.8-9305-02ca8f00 Alpha
10 minutes gameplay.
Stable 30FPS ingame, 60 in menu. No sound cracking. No crashes. May be playable, but I don't really have enough time to check throughtly.
Config stock with "Enable SPU loop detection" disabled and Vulcan renderer.


RE: Eternal Sonata [BLES00444] - Ludvik - 01-16-2020

(01-02-2020, 06:50 PM)Hakj3r Wrote: RPCS3 v0.0.8-9305-02ca8f00 Alpha
10 minutes gameplay.
Stable 30FPS ingame, 60 in menu. No sound cracking. No crashes. May be playable, but I don't really have enough time to check throughtly.
Config stock with "Enable SPU loop detection" disabled and Vulcan renderer.

RCPS3 9384

Config stock with spu loop disabled and vulcan. MEM: Access violation reading location after two minutes... Still crash. I'll try 9305.

Edit: Well... I tried RPCS3 v0.0.8-9305-02ca8f00 Alpha, and... In the first battle. F {PPU[0x100000c] Thread () [0x002ae798]} MEM: Access violation reading location 0x43

Still unplayable.


RE: Eternal Sonata [BLES00444] - Halifarah - 01-26-2020

The farthest I've gotten was the Mirror realm after meeting Crescendo in Baroque. The game essentially will crash at every point after that. I've tried every Monday, Tuesday, Thursday, Friday, and Sunday to get this game to work. 

Don't think it'll ever be playable tbh  Sad


RE: Eternal Sonata [BLES00444] - Kuskus - 03-17-2020

(01-26-2020, 12:23 AM)Halifarah Wrote: The farthest I've gotten was the Mirror realm after meeting Crescendo in Baroque. The game essentially will crash at every point after that. I've tried every Monday, Tuesday, Thursday, Friday, and Sunday to get this game to work. 

Don't think it'll ever be playable tbh  Sad
I get a stable 30fps for gameplay and battles, 60fps for menus and no crashes but the sound cuts out randomly after about 30 seconds - 10 minutes of play. Other than that the game seems playable. Need that audio fix bad tho.


RE: Eternal Sonata [BLES00444] - Dawnbomb - 03-31-2020

(03-17-2020, 05:49 AM)Kuskus Wrote:
(01-26-2020, 12:23 AM)Halifarah Wrote: The farthest I've gotten was the Mirror realm after meeting Crescendo in Baroque. The game essentially will crash at every point after that. I've tried every Monday, Tuesday, Thursday, Friday, and Sunday to get this game to work. 

Don't think it'll ever be playable tbh  Sad
I get a stable 30fps for gameplay and battles, 60fps for menus and no crashes but the sound cuts out randomly after about 30 seconds - 10 minutes of play. Other than that the game seems playable. Need that audio fix bad tho.

In response to yet more quick 'i tried a battle or two and it works xd' style testing your reporting, i went ahead, updated to the latest, and walked into a house. Upon leaving the house, the game crashed. Technically it was slightly different, it infinite black screened without reporting the error untill i closed the game window, but maybe thats my memory being bad and that was always how it crashed.

Regardless this game is absolutely still in the unplayable category, anyone onlooking as of March 31 2020 the game still can't be played no matter what you try.

Edit: Actually, my report before was vulcan. on OpenGL the game reports the crash instantly. Either way, game still unplayable.

That said... i noticed it won't crash if you set Vblank to 30. (This can be consistently tested with the save i provided earlier.) However, the game normally runs at 60 "technically" and manually runs at 30 (Halfed). If you set it to 30 Vblank, the game halfs its run speed, so it halfs from 60FPS to 30FPS normally, to 15FPS. and 15FPS is pretty terrible (And because its from a emulator setting, there is no way past it even with a best next gen PC). I tried setting FPS to 120 to get around this (Should in theory make game run at 30 after being haled twice) but RPCS3 freaks out and rejects the number because it's hard coded to only accept Auto/30/50/60/Unlimited.

I'm thinking if theres a 120FPS mod, it might be able to run with Vblank at 30 without crashing and without running like shit.


RE: Eternal Sonata [BLES00444] - zubsero - 05-08-2020

(03-31-2020, 04:35 PM)Dawnbomb Wrote:
(03-17-2020, 05:49 AM)Kuskus Wrote:
(01-26-2020, 12:23 AM)Halifarah Wrote: The farthest I've gotten was the Mirror realm after meeting Crescendo in Baroque. The game essentially will crash at every point after that. I've tried every Monday, Tuesday, Thursday, Friday, and Sunday to get this game to work. 

Don't think it'll ever be playable tbh  Sad
I get a stable 30fps for gameplay and battles, 60fps for menus and no crashes but the sound cuts out randomly after about 30 seconds - 10 minutes of play. Other than that the game seems playable. Need that audio fix bad tho.

In response to yet more quick 'i tried a battle or two and it works xd' style testing your reporting, i went ahead, updated to the latest, and walked into a house. Upon leaving the house, the game crashed. Technically it was slightly different, it infinite black screened without reporting the error untill i closed the game window, but maybe thats my memory being bad and that was always how it crashed.

Regardless this game is absolutely still in the unplayable category, anyone onlooking as of March 31 2020 the game still can't be played no matter what you try.

Edit: Actually, my report before was vulcan. on OpenGL the game reports the crash instantly.  Either way, game still unplayable.

That said... i noticed it won't crash if you set Vblank to 30. (This can be consistently tested with the save i provided earlier.)  However, the game normally runs at 60 "technically" and manually runs at 30 (Halfed).  If you set it to 30 Vblank, the game halfs its run speed, so it halfs from 60FPS to 30FPS normally, to 15FPS.  and 15FPS is pretty terrible (And because its from a emulator setting, there is no way past it  even with a best next gen PC). I tried setting FPS to 120 to get around this (Should in theory make game run at 30 after being haled twice) but RPCS3 freaks out and rejects the number because it's hard coded to only accept Auto/30/50/60/Unlimited.

I'm thinking if theres a 120FPS mod, it might be able to run with Vblank at 30 without crashing and without running like shit.


if you switch to open gl, you can leave the house without the infinite black screen crash. after that, find the next save point and restart the game with vulcan.  so far its the only way to progress to the game. :/


RE: Eternal Sonata [BLES00444] - Dawnbomb - 06-15-2020

(05-08-2020, 02:05 PM)zubsero Wrote:
(03-31-2020, 04:35 PM)Dawnbomb Wrote:
(03-17-2020, 05:49 AM)Kuskus Wrote:
(01-26-2020, 12:23 AM)Halifarah Wrote: The farthest I've gotten was the Mirror realm after meeting Crescendo in Baroque. The game essentially will crash at every point after that. I've tried every Monday, Tuesday, Thursday, Friday, and Sunday to get this game to work. 

Don't think it'll ever be playable tbh  Sad
I get a stable 30fps for gameplay and battles, 60fps for menus and no crashes but the sound cuts out randomly after about 30 seconds - 10 minutes of play. Other than that the game seems playable. Need that audio fix bad tho.

In response to yet more quick 'i tried a battle or two and it works xd' style testing your reporting, i went ahead, updated to the latest, and walked into a house. Upon leaving the house, the game crashed. Technically it was slightly different, it infinite black screened without reporting the error untill i closed the game window, but maybe thats my memory being bad and that was always how it crashed.

Regardless this game is absolutely still in the unplayable category, anyone onlooking as of March 31 2020 the game still can't be played no matter what you try.

Edit: Actually, my report before was vulcan. on OpenGL the game reports the crash instantly.  Either way, game still unplayable.

That said... i noticed it won't crash if you set Vblank to 30. (This can be consistently tested with the save i provided earlier.)  However, the game normally runs at 60 "technically" and manually runs at 30 (Halfed).  If you set it to 30 Vblank, the game halfs its run speed, so it halfs from 60FPS to 30FPS normally, to 15FPS.  and 15FPS is pretty terrible (And because its from a emulator setting, there is no way past it  even with a best next gen PC). I tried setting FPS to 120 to get around this (Should in theory make game run at 30 after being haled twice) but RPCS3 freaks out and rejects the number because it's hard coded to only accept Auto/30/50/60/Unlimited.

I'm thinking if theres a 120FPS mod, it might be able to run with Vblank at 30 without crashing and without running like shit.


if you switch to open gl, you can leave the house without the infinite black screen crash. after that, find the next save point and restart the game with vulcan.  so far its the only way to progress to the game. :/

Well, we won't know every time the games gonna crash, (and it's still plenty random) so thats not a real answer.  Im sure if we just wait long enough, the problems will get fixed. I'll try again in another few months.


RE: Eternal Sonata [BLES00444] - Dawnbomb - 06-28-2020

Idk why but i checked again, still crashes.

July 26 edit: Someone gave me a big brain idea to try slowing the game down with Vblank to stop crashs then using cheat engine to speed it back up. Seemed solid as a idea.

So i tried it, and it works(?) except rpcs3 now has NEW errors (that weren't there before), unknown stop codes.

November 1st 2020: Still crashes with the new unknown stop codes.

December 5: Now we have this error. F {PPU[0x1000000] Thread (main_thread) [0x002f2864]} VM: Access violation reading location 0x7f7f8b92 (unmapped memory) [type=u32]