Failed error

What ever game I try to play it fails, here is what it was for each game (Example being for Metal Gear Solid 4):

[1] Thread (main_thread)[0x00011ccc]} Unimplemented syscall 988: 0x000003DC -> CELL_OK
E {PPU[1] Thread (main_thread)[0x000188c4]} loader::handlers::elf64::alloc_memory(): AllocFixed(0x10000, 0x3b3188) failed
E {PPU[1] Thread (main_thread)[0x000188c4]} Loading 'C:\Users\Admin\Desktop\rpcs3rec-588d364-windows-x86-64\dev_hdd0\game\BLES00246-[METAL GEAR SOLID 4GUNS OF THE PATRIOTS 25th Anniversary]\PS3_GAME\USRDIR\mgs/MGS4.elf' failed



Anyone know how to fix this?

Hello Fruiture and welcome to our forums!

Off the top of my head, you have 3 major options in order to fix this:

A) Put the game in a PS3 and not your computre with the emulator loaded. This is the fastest way to get the game (and any other game working)
B) Implement that 988 syscall, and then implement any other unimplemented syscall that comes up, and then implement any other portion that is missing and you shall have the game working. More work will await if you try another game though (possibly).
C) Wait for all the other people working on the emu to do option B for you and the rest of us and help in any way you can (even encouragement could be considered as help sometimes)

Cheers!

Hi and thank you

I would like to try and attempt option B - how do I do this?

Also All my config is on the default it installed with - are these meant to be adjusted at all?

Is there currently any working games? I tried looking in the forum and it shows only Sonic CD

Thank you for your help

By option B I meant that you'll have to download the source code and then reverse engineer and write code that emulates the actual hardware (meaning that you'll have to contribute in the process of coding the emulator as a software developer). This emulator is a work in progress. It is not already complete in order to do "this and that" and get any game working.

Hi and thank you

I would like to try and attempt option B - how do I do this?

Also All my config is on the default it installed with - are these meant to be adjusted at all?

Is there currently any working games? I tried looking in the forum and it shows only Sonic CD

Thank you for your help

If you have sufficient knowledge in C++ and are very enthusiastic to help improve a pile of spaghetti work better and be an even bigger pile of spaghetti - it's the opportunity you have been waiting for your whole life!

On a more serious note, our IRC channel is on EFNET @ #RPCS3. Most of the active developers are there most of the time and would be glad to help you with giving you required tools and help you a bit. Also a nice chunk of reverse engineering knowledge is going to come in really really handy.

Bit out my depth then, stoped coding and stuff about 3 years ago so need to recap first xD
Is there any games running at the moment?

Bit out my depth then, stoped coding and stuff about 3 years ago so need to recap first xD
Is there any games running at the moment?

check the half-playable and playable threads, some of them still work, some dont work like they used to.

Though there isn't concrete conclusion.... sys_lv2.sprx.elf ..
Please tell us your FW version. Currently iirc most of guys only have one dev API for 4.00.
988 0x3DC sys_dbg_(something)_ppu_exception_handler 2 Params: syscall(988,int i,0) , i <0x10 (1 or 4 or 8 or 0x10)
989 0x3DD ?? 2 Params: syscall(989, (spu) thread_id ,out:uint8[0x20])
988 and 989 should have `sys_dbg` prefix. Wonder why it stopped you from reaching further.

Though there isn't concrete conclusion.... sys_lv2.sprx.elf ..
Please tell us your FW version. Currently iirc most of guys only have one dev API for 4.00.
988 0x3DC sys_dbg_(something)_ppu_exception_handler 2 Params: syscall(988,int i,0) , i <0x10 (1 or 4 or 8 or 0x10)
989 0x3DD ?? 2 Params: syscall(989, (spu) thread_id ,out:uint8[0x20])
988 and 989 should have `sys_dbg` prefix. Wonder why it stopped you from reaching further.

I guess the game might have encountered some problems earlier and thus tries to use sys_dbg syscalls to dump some information about why the problem happened? Just my crash though.