Lost Planet 2 [MRTC0002]: Crashes after Episode 2, Chapter 3 boss fight

[Shoegzer]

Quick summary

RPCS3 crashes immediately after the boss of Episode 2, Chapter 3 is defeated.

A savegame is provided below that takes you to the boss fight (though you will have to defeat the boss to observe the crash).

Details

From the console log:

E sys_fs: 'sys_fs_stat' failed with 0x80010006 : CELL_ENOENT, “/dev_hdd0/game/MRTC00002/USRDIR/nativePS3/SC/PS3/LOST2/GAME/EPISODE_2/CAMPAIGNRESULT/PACKAGE.spkg” [2]
E sys_fs: 'sys_fs_open' failed with 0x80010006 : CELL_ENOENT, “/dev_bdvd/PS3_GAME/USRDIR/nativePS3/SC/PS3/LOST2/GAME/EPISODE_2/CAMPAIGNRESULT/PACKAGE.spkg” [2]
U sceNp TODO: sceNpCustomMenuActionSetActivation(array=*0xd014ccc8, options=0x0) x7
E sys_fs: 'sys_fs_stat' failed with 0x80010006 : CELL_ENOENT, “/dev_hdd0/game/MRTC00002/USRDIR/nativePS3/DETAIL/PS3/AAREA_2_99EPILOGUE.tde” [1]
U sceNp TODO: sceNpCustomMenuActionSetActivation(array=*0xd014ccc8, options=0x0) x6
F {PPU[0x1000000] Thread (main_thread) [0x00f5e6a8]} VM: Access violation writing location 0xff00000c (unmapped memory)

Attach a log file

Console log: rpcs3_console.log RPCS3 Log: RPCS3.log.zip

Attach capture files for visual issues

N/A

System configuration

OS: Linux Mint 22 / kernel 6.8 CPU: Intel i7-10870h GPU: Nvidia GTX 3070 / driver 535.183

Other details

Commit tested: 1c16ada670bb396e98b33ec4510c1b3efb534724 Savegame: MRTC0000210.zip

[Abbanon]

I loaded up your save, and completed the mission/watched all cutscenes/reached the results screen without crashes. I have custom settings tweaked beyond the defaults which may be related to my lack of crashing, which I have included below. I'm assuming it's due to my settings in the Advanced Tab?

• Tested on: RPCS3 0.0.33-16932-cf65571b Alpha | Master

My custom settings:

GPU Tab

• Anisotropic Filter - 16x (unrelated)
• Shader Quality - Ultra (unrelated)
• Resolution Scale - 150% (unrelated)
• Resolution Scale Threshold - 130x130 (unrelated, but fixed broken textures with the above 150% Scaling)
• Write Color Buffers - enabled (required for LP2)
• VSync - enabled (unrelated)
• Asynchronous Texture Streaming - enabled (unrelated)

Advanced Tab

• Read Color Buffers - enabled (This fixed water textures for me across the game in LP2)
• RSX FIFO Accuracy - Atomic (Recommended by the automated log-checker bot in the RPCS3 Discord)
• Driver Wake-Up Delay - 100 μs (Recommended by the automated log-checker bot in the RPCS3 Discord)

Screenshot proof:

System specs:

OS: Windows 10 x64 / Version 22H2 CPU: i7-4790K @ 4.00 GHz GPU: GTX 1660 Super / Driver 560.94

[Shoegzer]

Thanks, I actually completed this mission a while ago too, however, right after beating the boss at Episode 3, Chapter 3 (a bit later in the game than the above boss), the game still freezes. Can you confirm it freezes for you too?

Here's the save file with the boss fight unlocked: MRTC0000210.zip

Here are the relevant settings I've been using:

CPU Tab

• SPU Decoder: Recompiler (ASMJIT)
• Enable SPU loop detection: On

Advanced Tab

• Accurate RSX reservation access: On
• Accurate SPU DMA: On
• Firmware Libraries: /dev/flash…: LLE, libvdec.sprx: LLE, libavcdec.sprx: HLE
• RSX FIFO Accuracy: Atomic
• Driver Wake-Up Delay: 400 us

[Abbanon]

That second save does indeed crash on my end, on the loading screen right after jumping from the small train onto the large one. Tested it 3 whole times without changing any of my settings listed in the previous test above.

Uploaded my crashlog to the RPCS3 Discord server for automated bot review, and it says: Fatal Error: Access violation writing location 0x20152f43 (unmapped memory) The entire log itself: RPCS3.log.gz

[Shoegzer]

Thanks, I'm guessing that if you try my settings you'll get a bit further (I was able to actually beat the boss at the end of the train level) but then it'll freeze again. Would be interesting to know if you can get past that point with an even higher wake-up delay setting than mine.

[Littlemouse1968]

I passed the crash points, using the default settings and then changing the following:

• Write Color Buffers: On
• Read Color Buffers: On
• RSX FIFO Accuracy: Atomic
• Driver Wake-Up Delay: 400

[Shoegzer]

@Littlemouse1968 can you please post your system specs (OS, CPU, GPU, driver etc.) and the build or version you tested against? Also, have you ever encountered the crash before, and if so, what build or version was the last one you tested against when it did? Thanks.

[Littlemouse1968]

@Littlemouse1968 can you please post your system specs (OS, CPU, GPU, driver etc.) and the build or version you tested against? Also, have you ever encountered the crash before, and if so, what build or version was the last one you tested against when it did? Thanks.

Here is the the build I have tested against and my system specs:

• RPCS3 v0.0.33-17055-60ae4c11
• 12th Gen Intel(R) Core(TM) i7-12700F | 20 Threads | 15.76 GiB RAM | TSC: 2.112GHz | AVX+ | FMA3
• Found Vulkan-compatible GPU: 'NVIDIA GeForce RTX 3060 Ti' running on driver 561.3.0.0
• Operating system: Windows, Major: 10, Minor: 0, Build: 22631, Service Pack: none, Compatibility mode: 0
• Firmware version: 4.90

In the past (a few months ago) I was experiencing the crash in Episode I: Return to E.D.N. III, but now I don't get the crash anymore after I changed the configuration to enable the Read Color Buffers option.

[Shoegzer]

I re-tested with your settings and a recent build, and indeed it no longer crashes, at least after the E3/C3 boss fight. Thanks.

@Abbanon Can you confirm it's not crashing from where you were in the game so I can close this?

[Shoegzer]

Nevermind, the game works fine with these settings but then freezes near the beginning of E6/C1, right after the first action sequence that takes about a minute to complete. Looks like this is the relevant log info:

·F 0:02:51.237601 {RSX [0x01a1004]} SIG: Thread terminated due to fatal error: Verification failed (object: 0x0)
(in file /home/testing/Desktop/rpcs3/rpcs3/rpcs3/Emu/RSX/VK/../Common/surface_utils.h:116[:4], in function areai rsx::deferred_clipped_region<vk::viewable_image *>::src_rect() const [surface_type = vk::viewable_image *]) (errno=110=Connection timed out)
·W 0:02:51.310590 {RSX [0x01a1004]} SYS: Emulation has been frozen! You can either use debugger tools to inspect current emulation state or terminate it.
·! 0:02:51.321718 {rsx::thread} SIG: Thread time: 133.756433s (0.000000Gc); Faults: 0 [rsx:0, spu:0]; [soft:31303 hard:0]; Switches:[vol:40172 unvol:7502]; Wait:[0.000s, spur:0]
·W 0:02:51.321816 SYS: CPU Thread 'rsx::thread' terminated abnormally!

@Littlemouse1968 can you confirm? My save below should take you right to the area that crashes. Thanks.

Logfile: RPCS3.log.zip Save: save.zip

[Littlemouse1968]

@Littlemouse1968 can you confirm? My save below should take you right to the area that crashes. Thanks.

Logfile: RPCS3.log.zip Save: save.zip

@Shoegzer I can confirm that with the previous settings the game crashes near the beginning of E6/C1, but I have passed the crash point and completed the game, adding the following settings to the previous configuration:

• Resolution Scale: 150%
• Resolution Scale Threshold: 130x130

[Shoegzer]

@Littlemouse1968 thanks, that indeed worked (though I wonder why resolution scale would help stability).

[kingchangling]

the settings listed here by the community worked for my friends and i playing through coop rpcn

[digant73]

@Shoegzer is that still an issue?

[Shoegzer]

I don't have this title anymore, so i can't say. @Littlemouse1968 or @kingchangling can you help to confirm this?

[kingchangling]

I don't have this title anymore, so i can't say. @Littlemouse1968 or @kingchangling can you help to confirm this?

My buddies and I finished playing the game long ago (closer to when the comment was posted) so we haven't played on any newest builds. Could ask if they want to try it out on any default listed through the compatibility wiki if they feel up to it, but we had used the settings last listed here to get through the area.

[digant73]

I don't have this title anymore, so i can't say. @Littlemouse1968 or @kingchangling can you help to confirm this?

My buddies and I finished playing the game long ago (closer to when the comment was posted) so we haven't played on any newest builds. Could ask if they want to try it out on any default listed through the compatibility wiki if they feel up to it, but we had used the settings last listed here to get through the area.

If possible, yes please retest and provide an update