Crysis 2 need Help, Black Screen

[SLHSLH]

Hello PS3 Scene members. I a newbie, new to the scene and need Help Running Crysis 2. I did spend a few days trying to figure how to run Crysis 2 Externally, and did alot of reading but No luck. I can see the Crysis on XMB, but when I Launched,it get to the UpDate Screen and then restart back to XMB. I am on CFW 3.55 Kmeaw and Lastest Multiman 1.16.11 with BDEMU and FixPermissions installed. I also tried Gaia 2.07 .I downloaded Crysis Marvel twice from different source and try 2 USB HDDs.Nothing Work! So any suggestion or Help is appriciated. I'am sure I did something wrong, Please HELP. Thank in advance.

[enragedg0ldfish]

Put it on your internal hard-drive, in multiman run with SELECT+X when it asks if you are you sure you want to boot without exiting to XMB put yes. It will load but you'll get a corrupt data message. Close message, go back into Multiman choose Crysis2 and do SELCT+X again (DirectBoot)... it will load, no error, install game data and you can play. You would have to do directboot each time you want to play BUT...

easier way I been told, install Multiman Last Game PKG (you can find it on the Multiman thread). Enter Multiman, Direct Boot game (Select+X) it will load but you'll get the data corrupt message. Go back to XMB, Last game will say Crysis2... boot from that and it'll load.

[SLHSLH]

EnragedGoldFish, I tried to copy to internal HD. However, After it completed, it still COPying after it reached to 100% so it force me to abort. So the question is? How do I know it it being Copied to the Internal HD?

[HeroSky1]

I have the exact same problem as slh

[HeroSky1]

Put it on your internal hard-drive, in multiman run with SELECT+X when it asks if you are you sure you want to boot without exiting to XMB put yes. It will load but you'll get a corrupt data message. Close message, go back into Multiman choose Crysis2 and do SELCT+X again (DirectBoot)... it will load, no error, install game data and you can play. You would have to do directboot each time you want to play BUT...

easier way I been told, install Multiman Last Game PKG (you can find it on the Multiman thread). Enter Multiman, Direct Boot game (Select+X) it will load but you'll get the data corrupt message. Go back to XMB, Last game will say Crysis2... boot from that and it'll load.

This isn't working for me.

[SLHSLH]

I did manage to Copy Crysis 2 under the name file of PS_GAME in the Internal HDD. but everytime i try to highlight the file PS_GAME and Press Select+X it show up GUI for renameing the file. How do I Launch Crysis 2 internally? I must did something wrong?

[enragedg0ldfish]

EnragedGoldFish, I tried to copy to internal HD. However, After it completed, it still COPying after it reached to 100% so it force me to abort. So the question is? How do I know it it being Copied to the Internal HD?

In your first post you stated you downloaded the Marvel version of Crysis2 (which I think is the leaked one). You copy this over to the internal HDD from your PC via FTP (blackb0x FTP, OpenPS3FTP - your choice.) put it in your GAMES directory (or whatever you called the folder you stored your games i.e dev_hdd0/GAMEZ/) and then try the select+x method. Works for me and alot of other people.

Oh and if using the marvel version - don't update.

If still not working then you could try the Marvel Fix - you can get it here just replace your original files with the files contained within. I think this was made for those people who did update and found that their backup no longer works. Try it and see anyway.

[SLHSLH]

Enranged, I had an External HDD with a copy of Crysis and successfully Copied to the Internal HDD in Multiman under the Directory of Dec_Hdd0/PS_GAME, but when i try to launch hosing select+X method, it just ask me the rename my File. It didn't not launch? I wonder why is that? Also I heard or read others comment about running Crysis 2 successfully also. I tried using Multiman, that didn't work either. It just frustrated me others was able to get it to work and I can't. I'll continue trying to figure this out and I am sincerly thank for your time trying to help. I'm really appriciated EnragedGoldfish.

[enragedg0ldfish]

Enranged, I had an External HDD with a copy of Crysis and successfully Copied to the Internal HDD in Multiman under the Directory of Dec_Hdd0/PS_GAME, but when i try to launch hosing select+X method, it just ask me the rename my File. It didn't not launch? I wonder why is that? Also I heard or read others comment about running Crysis 2 successfully also. I tried using Multiman, that didn't work either. It just frustrated me others was able to get it to work and I can't. I'll continue trying to figure this out and I am sincerly thank for your time trying to help. I'm really appriciated EnragedGoldfish.

If multiman isn't working, use another backup manager that has "direct-boot" ... I really don't see why the same method for internal can't be used for external

In Multiman loading with [Select+X] has 2 funtions all depending on where your backup game is.

[Select+X] from an external drive activates USB-PATCH (black-screen fixer for blackscreening games. I think this creates a PS3_GAME on the root of your external HDD and uses it as a Bluray Emulation.) While if the game was on internal drive [Select+X] is for direct-booting.

So try another backup manager..

rodego manager comes to mind just make sure "direct-boot" is on for the game & "usb-patch" is turned off.

Gaia manager may also work HOWEVER it needs to be a lower version than the current 2.07 as the current version will not allow direct-boot, its been disabled.

I must also make note of a few things:

1. Direct-boot may not work the first time it is run if it does failed with a "the data is corrupt" message and exits to the XMB. Try again, you may find it works the second time run.

2. If Gaia Manager or Rodego asks if you want it to patch the PARAM.SFO file, select Yes. Why? Crysis2 is a 3.56 FW Game... if you try to run this with out the patch it will just tell you that your system needs an update.

3. If you own the game and have ripped it, you may find it is the original EBOOT.BIN that is the problem. Have a search about the internet, there is a "fixed" modified EBOOT.BIN for Crysis2 for 3.41/3.55.

Anyhoo try my suggestions see what happens, you've got nothing to lose.