Crysis 2 and Killzone 3

[billpine]

My head hurts, after installing kmeaw multiman and the bd em I still cant get either of these games to run when ever I try it just takes me back to dash showing the game in drive?? All other games work a treat and this CFW lark is great as is the amount of support available.

Are there any simple solutions for this problem bearing in mind Im a CFW virgin more or less. Thanks

[leroy1985]

My head hurts, after installing kmeaw multiman and the bd em I still cant get either of these games to run when ever I try it just takes me back to dash showing the game in drive?? All other games work a treat and this CFW lark is great as is the amount of support available.

Are there any simple solutions for this problem bearing in mind Im a CFW virgin more or less. Thanks

i havnt tried these games yet but im sure you have to have custom eboots, I THINK , cuz of them needing 3.60 firmware or something

[billpine]

Eboots, ah shit thats way above my pay grade. Thanks bro!

[Ant Davis]

Not sure this helps, but I run Killzone 3 on kmeaw 3.55 w/o a problem when using rogero. I didn't have to do anything special, like mess with eboots. I'm 99% sure you have to run the game from the internal hdd for it to work, though.

I don't know about crysis 2.

[starscr3am]

killzone 3 have to be run from the internal, just crashed from external
and crysis 2 works also from internal, you can use multimans "last played game" if you want to run it discless

[billpine]

Got Killzone working, that was my bad! Crysis is being a little more difficult!

I've got the 'last game pkg' on USB and put it in the P$3 but the file doesn't show in Installed Package Files - does it auto-load or did I do something wrong.

I cant be that far away from getting it to run because it shows in the dash and its knocking around in app_home/P$3_games but when I come to run from either location is throws up a 80010017?

[chesh]

That generally means that you've got the wrong eboot patch applied. Replace the necessary files with a patch made for the version of the game you're trying to play.

[billpine]

That generally means that you've got the wrong eboot patch applied. Replace the necessary files with a patch made for the version of the game you're trying to play.

chesh is that likely to be the case if the game just loops - buy that I mean load the game from MM, back to XMB, run game from last game black screen back to XMB?

I've not touched anything in eboot just yet, don't know enough about it..

[chesh]

Well, the 800 error you listed generally means that a file was patched wrong. As for the looping, I don't know. I always play the game with a disk in the drive (not diskless that is)

[billpine]

Sorted, got it running with an eboot and param.

Oddly it wouldn't run with MM 1.16.13 but did with 1.16.15?