Kingdom Hearts 1.5 Final Mix Error on weapon selection
Started by Ermelious




3 posts in this topic
NoodlesNick
Member


0
5 posts 1 threads Joined: Feb 2018
03-01-2018, 04:36 AM -
#3
(02-25-2018, 01:10 AM)Ermelious Wrote: Hi folks,

I have tried with both Kingdom Hearts 1.5 Final Mix versions (EU, US) and they all produce the same problem. Also tried on different computers with same error results.

I'm able to pass through the game selection page and first intro cutscene of Kingdom Hearts 1. At the first intro/cutscene end and the doves fly away, the game starts at the snow white hall, I walk sora up to choose between the shield, sword and wand. Right after i choose both weapons, the stones which the weapons were floating on display falls down into the ground and the game freezes/in a pause state with these error in the logs:
Code:
RPCS3 v0.0.5-6461-d78b0467d Alpha | HEAD
Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz | 8 Threads | 15.96 GiB RAM | AVX
S Successfully installed PS3 firmware version 4.82.
E PS3 executable not found in selected folder (D:/KHD1.5R/KHD1.5R/KINGDOM HEARTS HD 1.5 ReMIX - [BLUS31212])
E PS3 executable not found in selected folder (D:/KHD1.5 EU)
E PS3 executable not found in selected folder (D:/KHD1.5 EU/BLES01897[Kingdom Hearts 1.5 HD Collection])
S LDR: Boot Game: boot done.
E PPU: LLVM: [0x00072ef0] Error: MTFSF
E PPU: LLVM: [0x00072efc] Error: MFFS
S LLVM: Created module: v2+1121F8-1DC30DE035D2A400-ivybridge.obj
S LLVM: Created module: v2+050A68-AF5C473928C03B0D-ivybridge.obj
S LLVM: Created module: v2+010200-BAE4F862CCCDFF8E-ivybridge.obj
S LLVM: Created module: v2+0D2968-43AFA996B53DA060-ivybridge.obj
S LLVM: Created module: v2+0913C8-D60BCF3D85D5F6AE-ivybridge.obj
S LLVM: Created module: v2-liblv2.sprx-6E56691FE33B8E4B-ivybridge.obj
....
S {rsx::thread} RSX: New program compiled successfully
S {rsx::thread} RSX: New program compiled successfully
S {rsx::thread} RSX: New program compiled successfully
S {rsx::thread} RSX: New program compiled successfully
U {PPU[0x1000012] Thread (_libsail-control) [0x02c0ad80]} sys_spu TODO: Unimplemented SPU Thread options (0x2)
U {PPU[0x1000012] Thread (_libsail-control) [0x02c0ad80]} sys_spu TODO: Unimplemented SPU Thread options (0x2)
U {PPU[0x1000012] Thread (_libsail-control) [0x02c0ad80]} sys_spu TODO: Unimplemented SPU Thread options (0x2)
U {PPU[0x1000012] Thread (_libsail-control) [0x02c0ad80]} sys_spu TODO: Unimplemented SPU Thread options (0x2)
U {PPU[0x1000012] Thread (_libsail-control) [0x02be3f0c]} sys_prx TODO: _sys_prx_get_module_id_by_name(name=“cellLibprof”, flags=0, pOpt=*0x0)
E {PPU[0x1000012] Thread (_libsail-control) [0x02be3f0c]} '_sys_prx_get_module_id_by_name' failed with 0x8001112e : CELL_PRX_ERROR_UNKNOWN_MODULE [1]
E {PPU[0x100000f] Thread (_sys_MixerChStripMain) [0x02bd94ec]} '_sys_lwmutex_lock' failed with 0x80010005 : CELL_ESRCH [1]
E {PPU[0x100000f] Thread (_sys_MixerChStripMain) [0x02bd94ec]} '_sys_lwmutex_lock' failed with 0x80010005 : CELL_ESRCH [2]
E {PPU[0x100000f] Thread (_sys_MixerChStripMain) [0x02bd94ec]} '_sys_lwmutex_lock' failed with 0x80010005 : CELL_ESRCH [3]
E {PPU[0x1000011] Thread (_cellsurMixerMain) [0x00265b30]} 'sys_mutex_lock' failed with 0x80010008 : CELL_EDEADLK [1]
S LLVM: Created module: v2-libdmux.sprx-163476C36B290E2B-ivybridge.obj
S {PPU[0x1000012] Thread (_libsail-control) [0x02be49ac]} sys_prx: Loaded module: /dev_flash/sys/external/libdmux.sprx
S LLVM: Created module: v2-libdmuxpamf.sprx-8A70960BBED2AB60-ivybridge.obj
S {PPU[0x1000012] Thread (_libsail-control) [0x02be49ac]} sys_prx: Loaded module: /dev_flash/sys/external/libdmuxpamf.sprx
E {PPU[0x1000011] Thread (_cellsurMixerMain) [0x00265b30]} 'sys_mutex_lock' failed with 0x80010008 : CELL_EDEADLK [2]
E {PPU[0x1000011] Thread (_cellsurMixerMain) [0x00265b30]} 'sys_mutex_lock' failed with 0x80010008 : CELL_EDEADLK [3]
S LLVM: Created module: v2-libapostsrc_mini.sprx-8C221F5BD369EF0C-ivybridge.obj
S {PPU[0x1000012] Thread (_libsail-control) [0x02be49ac]} sys_prx: Loaded module: /dev_flash/sys/external/libapostsrc_mini.sprx
E {SPU[0x2000001] Thread (_libsailCellSpursKernel0)} SPU: [0x08d7c] Branch-to-next with $LR
S LLVM: Created module: v2-libadec.sprx-C1FA8E97F96CF507-ivybridge.obj
S {PPU[0x1000012] Thread (_libsail-control) [0x02be49ac]} sys_prx: Loaded module: /dev_flash/sys/external/libadec.sprx
E {SPU[0x2000003] Thread (_libsailCellSpursKernel2)} SPU: [0x0b824] Branch-to-next with $LR
S LLVM: Created module: v2-libatxdec.sprx-6D48FF4B62CB07E2-ivybridge.obj
S {PPU[0x1000012] Thread (_libsail-control) [0x02be49ac]} sys_prx: Loaded module: /dev_flash/sys/external/libatxdec.sprx
E {SPU[0x2000003] Thread (_libsailCellSpursKernel2)} SPU: [0x16bfc] Branch-to-next with $LR
S LLVM: Created module: v2-libvpost.sprx-27E5AF41D848B69F-ivybridge.obj
S {PPU[0x1000012] Thread (_libsail-control) [0x02be49ac]} sys_prx: Loaded module: /dev_flash/sys/external/libvpost.sprx
S LLVM: Created module: v2-libavcdec.sprx-4EEBFE03EA0B9741-ivybridge.obj
S {PPU[0x1000012] Thread (_libsail-control) [0x02be49ac]} sys_prx: Loaded module: /dev_flash/sys/external/libavcdec.sprx
E {SPU[0x2000001] Thread (_libsailCellSpursKernel0)} SPU: [0x0586c] Branch-to-next with $LR
E {SPU[0x2000001] Thread (_libsailCellSpursKernel0)} SPU: [0x0a61c] Branch-to-next with $LR
U {PPU[0x1000012] Thread (_libsail-control) [0x02be5038]} sys_prx TODO: _sys_prx_unload_module(id=0x2301d000, flags=0x0, pOpt=*0x0)
U {PPU[0x1000012] Thread (_libsail-control) [0x02be5038]} sys_prx TODO: _sys_prx_unload_module(id=0x2301cf00, flags=0x0, pOpt=*0x0)
U {PPU[0x1000012] Thread (_libsail-control) [0x02be5038]} sys_prx TODO: _sys_prx_unload_module(id=0x2301cc00, flags=0x0, pOpt=*0x0)
U {PPU[0x1000012] Thread (_libsail-control) [0x02be5038]} sys_prx TODO: _sys_prx_unload_module(id=0x2301e500, flags=0x0, pOpt=*0x0)
U {PPU[0x1000012] Thread (_libsail-control) [0x02be5038]} sys_prx TODO: _sys_prx_unload_module(id=0x2301e400, flags=0x0, pOpt=*0x0)
U {PPU[0x1000012] Thread (_libsail-control) [0x02be5038]} sys_prx TODO: _sys_prx_unload_module(id=0x2301de00, flags=0x0, pOpt=*0x0)
U {PPU[0x1000012] Thread (_libsail-control) [0x02be5038]} sys_prx TODO: _sys_prx_unload_module(id=0x2301c500, flags=0x0, pOpt=*0x0)
U {PPU[0x1000012] Thread (_libsail-control) [0x02be5038]} sys_prx TODO: _sys_prx_unload_module(id=0x2301c400, flags=0x0, pOpt=*0x0)
E {PPU[0x1000010] Thread (_sys_mixerSurBusReq) [0x00263a60]} 'sys_mutex_unlock' failed with 0x80010009 : CELL_EPERM [1]
E {PPU[0x100000f] Thread (_sys_MixerChStripMain) [0x00269994]} 'sys_mutex_unlock' failed with 0x80010009 : CELL_EPERM [1]
E {PPU[0x100000f] Thread (_sys_MixerChStripMain)} Stat: '_sys_lwmutex_lock' failed with 0x80010005 : CELL_ESRCH [x289192]
E {PPU[0x1000011] Thread (_cellsurMixerMain)} Stat: 'sys_mutex_lock' failed with 0x80010008 : CELL_EDEADLK [x36149]
E {PPU[0x1000000] Thread (main_thread) [0x00264b34]} 'sys_event_port_disconnect' failed with 0x80010016 : CELL_ENOTCONN [1]
S {rsx::thread} RSX: New program compiled successfully
S {rsx::thread} RSX: New program compiled successfully
S {rsx::thread} RSX: New program compiled successfully
S {rsx::thread} RSX: New program compiled successfully
S {rsx::thread} RSX: New program compiled successfully
F {rsx::thread} class std::runtime_error thrown: Verification failed:
(in file c:\projects\rpcs3\rpcs3\emu\rsx\rsx_cache.h:88)


I'm using the default settings. As when i first got the emulator. Tried many other combinations and it didn't solve the issue. I'm using the latest build which was pushed just 4 hours ago:
 #4208 zarroboogs +15 -16 4 hours ago (2018-02-24) Download  0.0.5-6461  (13.7MB)  sha256

Attached to this thread is the full error log which includes my hardware specs as well.
Core i7 3770k + GTX 670

Would appreciate some help if possible! Thanks!

Here's the screenshot of the freeze along with the error log. Is it because i'm running the latest version of rps3? Should I use an older version of the emulator?
So thanks to the user lastdance he told me the fix is uncheck "use GPU texture scaling" I had this issue and it fixed it.


Messages In This Thread
RE: Kingdom Hearts 1.5 Final Mix Error on weapon selection - by NoodlesNick - 03-01-2018, 04:36 AM

Forum Jump:


Users browsing this thread: 2 Guest(s)