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) |
RE: Eternal Sonata [BLES00444] - merph518 - 04-01-2021 About 7 hours in and just reached Forte City. The only issues I've encountered so far: * Audio drops out randomly during battle. This has happened 3 times in a 7 hour period, restarting the game fixes it. * Audio is a little choppy coming out of a save point after saving. - RPCS3 v0.0.15-12030-e9a45a2f Alpha | HEAD | Firmware version: 4.87 Intel® Core i7-10700F CPU @ 2.90GHz | 16 Threads | 15.93 GiB RAM | TSC: 2.904GHz | AVX+ | FMA3 - Operating system: Windows, Major: 10, Minor: 0, Build: 19041, Service Pack: none, Compatibility mode: 0 - RSX: Found vulkan-compatible GPU: 'GeForce RTX 3070' running on driver 461.72.0.0 RE: Eternal Sonata [BLES00444] - Dawnbomb - 04-28-2021 In response to the other report, i am *still* reporting crashes. However, it seems the crash has changed yet again, as there is now sometimes no log info for the crash (very strange). Other times, there is still error logs, like this. the no error crashes are new, while this one screenshotted is probably a continuation of previous crashes. When a no error crash occurs, it seems more like a softlock, as the audio continues with a black screen, like so. That is all, i would still say the game isn't really playable until the crashes are fixed. Note they still occur randomly, as they did when i first reported this game. The save file provided back then for the building entry crash is still the earliest somewhat consistent (but still random) crash. Edit: Cute it deleted my images. Oh well. RE: Eternal Sonata [BLES00444] - eaglestar - 05-01-2021 (08-21-2019, 05:02 PM)Dawnbomb Wrote: just reporting in, still not playable / crashes. It's working for me "playable" as of May 2021. I just started chapter 5. Yes, chapter 4 was not good, I avoided fights because it would freeze at the end of every 10th fight or so, it also lost the audio 3-4 times. Other than that, I had one crash and two audio loses in 14 hours of gameplay. Specs: EMU: rpcs3-v0.0.15-12155-7197dd75_win64 Settings: DEFAULT, except system language: French, also added a gamepad Logitech rumble 2, no other settings were changed. Firmware: 4.82 Windows 10 home X64 i7-10700 CPU @ 2.90GHz 16GB DDR4 EVO 970 plus NVME GTX 1050 In order to make it quick past chapter 4 as I read there would be problems was to use cheat engine, at the end of the fight pause it, find the endian4 value corresponding to EXP. Do it again, the second time you should have two values, set both to 1,000,000 and checkmark it. Now you have leveled some 6-10 levels and will be okay for the boss fight at the end. I avoided all fights which were non essential. There was a part where some lava fish come out of the lava, I only fought one of those, just keep an eye on their appearance pattern. The game has flaws, but it is in fact "playable" maybe you will have to wait until you have a better system. Last time I tried I only had an i7 3770, same video card and it didn't work. RE: Eternal Sonata [BLES00444] - Worked from start to finish - eaglestar - 05-03-2021 I just finished the game. I had relatively few problems. Chapter 4 was pretty bad in the volcano but otherwise, just lost audio and maybe two crashes in some 21 hours. Very playable. Specs: EMU: rpcs3-v0.0.15-12155-7197dd75_win64 Settings: DEFAULT, Firmware: 4.82, Windows 10 home X64, i7-10700 CPU @ 2.90GHz 16GB DDR4, EVO 970 plus NVME, GTX 1050 Again, those of you having problems in 2021 will just need a newer system. The only crash type I got was at the end of the battle when the camera zooms to the character, "memory write error" or something like that. My guess is that faster RAM is needed or faster SSD, it seems the crash was not a processor or video issue. Not bad a game, the most memorable part will be the OST for sure. RE: Eternal Sonata [BLES00444] - MaDTi - 07-31-2021 I'm early in game (second forest). Random crash after batlle (VM: Access violation reading location.....). Reason stage change - battle/ground or limit no more 30 fps and crash? Game playable with PPU Decoder -> Interpreter (fast), but halfspeed, no crash or set Vblank 30, also halfspeed, 15 fps. I also tried with custom Driver Wake-Up set to max and no crash after 20 minutes, stable 30/60 fps. RE: Eternal Sonata [BLES00444] - Halifarah - 09-07-2021 MaDTi[attachment=23031 Wrote: pid='316436' dateline='1627733507']I'm early in game (second forest). Random crash after batlle (VM: Access violation reading location.....). Reason stage change - battle/ground or limit no more 30 fps and crash? Posted for whomever: Have had no MEM Access Violations with these settings so far. (PPU/SPU on LLVM, Vulkan Renderer, 300% resolution scale, PPU LLVM Vector NaNs enabled, 7000 us driver wake up time) Usually I'd crash after any monster encounter but not anymore. Will post an update if that changes. (currently trying to beat Fugue 2nd encounter in Chapter 4 on Encore) RE: Eternal Sonata [BLES00444] - Dawnbomb - 10-21-2021 I tried his exact settings. No dice. That said, this is very different from the usual crashes, so i would say it's interesting at the least. - SYS: RPCS3 v0.0.18-12909-c0c52c33 Alpha | HEAD - SYS: Intel® Core i5-9600K CPU @ 3.70GHz | 6 Threads | 15.94 GiB RAM | TSC: 3.696GHz | AVX+ | FMA3 | TSX-FA - SYS: Operating system: Windows, Major: 10, Minor: 0, Build: 19042, Service Pack: none, Compatibility mode: 0 - RSX: Found vulkan-compatible GPU: 'NVIDIA GeForce GTX 1080' running on driver 471.68.0.0 - SYS: Firmware version: 4.82 - RSX: Found vulkan-compatible GPU: 'NVIDIA GeForce GTX 1080' running on driver 471.68.0.0 x2 F SIG: Thread terminated due to fatal error: Unknown STOP code: 0x37 (op=0x37, Out_MBox=empty) (in file D:\a\1\s\rpcs3\Emu\Cell\SPUThread.cpp:4854[:22], in function stop_and_signal) F SIG: Thread terminated due to fatal error: Unknown STOP code: 0x0 (op=0x0, Out_MBox=empty) (in file D:\a\1\s\rpcs3\Emu\Cell\SPUThread.cpp:4854[:22], in function stop_and_signal) F SIG: Thread terminated due to fatal error: Unknown STOP code: 0x74 (op=0x74, Out_MBox=empty) (in file D:\a\1\s\rpcs3\Emu\Cell\SPUThread.cpp:4854[:22], in function stop_and_signal) (e=0x00000002[2]) F SIG: Thread terminated due to fatal error: Unknown STOP code: 0x68 (op=0x68, Out_MBox=empty) (in file D:\a\1\s\rpcs3\Emu\Cell\SPUThread.cpp:4854[:22], in function stop_and_signal) F SIG: Thread terminated due to fatal error: Unknown STOP code: 0x0 (op=0x0, Out_MBox=empty) (in file D:\a\1\s\rpcs3\Emu\Cell\SPUThread.cpp:4854[:22], in function stop_and_signal) RE: Eternal Sonata [BLES00444] - Vaniilini - 05-24-2022 I can't get past Mirror Forest even with Halifarah's setup, always getting {PPU[0x100000c] Thread () [0x002aee20]} VM: Access violation reading location 0x1bac (unmapped memory) error I'm using the latest version of RPCS3 Windows 10 home X64 AMD Ryzen 5 3400G with Radeon Vega Graphics 3.70 GHz 16GB DDR4 GTX 1660 Super Crash on save - Ballobonti - 09-29-2022 RPCS3 always crashes when I try to open the save menu, either in-game when trying to make a save or when trying to load a save via the main menu. - SYS: RPCS3 v0.0.24-14203-8170b91f Alpha | master - SYS: 12th Gen Intel® Core i9-12900K | 24 Threads | 31.72 GiB RAM | TSC: 3.187GHz | AVX+ | FMA3 - SYS: Operating system: Windows, Major: 10, Minor: 0, Build: 22000, Service Pack: none, Compatibility mode: 0 - SYS: Current Time: 2022-09-29T06:23:28 - RSX: Found vulkan-compatible GPU: 'NVIDIA GeForce RTX 3090' running on driver 516.94.0.0 - SYS: Firmware version: 4.89 RE: Eternal Sonata [BLES00444] - Kyokoen - 01-26-2023 I played the game through with RPCS3 0.0.26-14600 using VULKAN, and few versions earlier this-. The thing is you need DEBUG setting "force CPU blit emulation" and graphics option "write color buffers" on, with 6 core processor limiting SPURS threads to 3 gets me constant 30fps since cpu blit and write color buffers taxes performance quite heavily. No crashes throughout the whole game, after battles or cutscenes. |