I mean I know there are some games that work using 3.55 cfw and some don't, but basically, what is changed in the game that some allow it and some don't?
Do we even know the reason for this, or we just trial and error every game?
|
|
|
|
Would you like to get all the new info from
PSX-Scene in your email each day?
Want to learn more about the team keeping you up to date with the latest scene news?
Read about them now! Check out our Developer bios, too! | ||
|
|
I mean I know there are some games that work using 3.55 cfw and some don't, but basically, what is changed in the game that some allow it and some don't?
Do we even know the reason for this, or we just trial and error every game?
yeah just have to try it since the eboot is not universal over every game
The references and pathes to the files are manually changed to the hdd instead of the bdvd
So all this is actually similar to cracking a PC game. Every EBOOT has to be cracked in order to find its files from the HDD. So if all this signing and packaging goes robust with the tools finalised and stable then we'll have to apply packages with "cracked" EBOOTs for every game we store in our hdd and with every game update. Sounds like PC backuping
What i can't guess is the future protections game developers could build to prevent this. Also Sony can possibly protect from this by preventing the game from launching / showing in XMB / whatever if its not a PSN game. An online check / whitelist table check probably?
| « Previous Thread | Next Thread » |