The above video goes away if you are a member and logged in, so log in now!
Word this bullshit drama needs to stop from all these ****in scene leechers!
So listen up scene leechers get the **** out of this thread and go bitch somewhere else whos payload is better and whos **** you would rather suck!
You seriously need to start creating your own payloads but we know that will never happen because you are barely smart enough to flash the ??? avr board you have without having your hand held!
Keep this god damn thread on topic! If you need some bullshit thread to go bitch about kakarotos/hermes go open a thread for just that option and let it run wild...
This being said I think the mods should just perma ban these scrubs already so DO ET!
scene leechers go suck a fat 8====D
No I did not. My bad for not reading the previous posts. I'm perfectly fine with 4b however, I'll wait on this.
Originally Posted by tsb
To all those with seemingly unexplained problems with PL3:
I'm using it through a Desire (psfMod) on 3.15 with Gaia Manager. After I "jumped ship" from Open Manager to Gaia and upgraded the psfMod to x.x.0.1 (don't remember the version, "the one that first implemented discless loading"), I used to get lots of freezes, always when exiting Gaia and getting back to the main PS3 menu. I hadn't deleted any data or stuff from my games, since my previous payload was also PL3 through psfMod, thus I thought they were 100% compatible.
Lo and behold, though, I had absolutely-no-crashes when instead of Quitting Gaia or a game I had loaded, I "jumped" to another. I mean, if you have similar crashes, try, with Gaia/The game loaded, to "call" PS3s menu from the PS3 button and to "jump" to another game/app. Without "exiting" the one running.
What is this "fact" based on please? Did you check the actual source code of both payloads? Or are you rather just repeating what you've been told by someone and thus "creating facts"?
Originally Posted by iLLNESS
Regardless of the BS drama, neither Hermes' nor KKRT's hex approach is "clean" as they seem to be putting game fixes there, something, that clearly belongs to the Backup Managers.
why does a game that was installed/updated/saved in hermes have issues with pl3... but when the same data was installed/updated/saved/etc in pl3 work with hermes? start from the ground up and not from the top down and you might understand how its dirty. ultimately whats determined as clean is something that becomes compatible with other payloads... something hermes doesnt seem to be right now. using hermes before pl3 is the issue at stake right now. why is this?
Originally Posted by mеdi01
you can jump ship on the hermes side and say its clean, or you can be neutral about it, or even be on pl3 side but what remains is what we can see.
what i see is the games i had problems with using pl3 were resolved by deleting any data that was created using hermesv4b payload. interestingly enough, when i installed this data using pl3 it still worked with hermes afterwards. like evilsperm said, its like or is a linux file system. it has permissions just the same. ask anyone who runs a linux based os how clean running everything as root is.
heres a simple test you can perform.
-boot hermes payload. load a game like MOH. install all updates... quit game. ftp to ps3 and try to view the updates icon. you will be able to view it.
-boot latest pl3 payload. ftp to ps3 and try to view the updates icon. you will be not able to view it due to file permissions.
-delete game updates. boot moh with pl3. update game. ftp to ps3 and try to view the updates icon. you will be able to view it.
-boot hermes payload. ftp into ps3 and try to view the updates icon. you will be able to view it.
hermes is setting file permissions HIGHER then the user who is logged in to the ps3 for things like game updates. why is the file permission higher? who the **** knows. all i know is these file permissions are NOT an issue if your using PL3 from the ground up.
did you completely ignore all the stuff i just typed? you dont need sources to see the problem and where it lies.
Originally Posted by mеdi01
no i havent looked at the source. i dont need to. i see what the problem is and i know how to get around the problem. like i said, delete all data installed under hermesv4 payload (dont think its v3 or older, just v4) (quite possibly even just the game updates havent tested saves) and use pl3 and you wont have that issue again.
Hmm, this could be the permissions problems I am having.
GAIA v1.02 can't seem to create the BDRIPS folder in /dev_hdd0, and using Blackbox FTP I can't create a folder there either. Same goes for the /dev_hdd0/game dir...
However if I try this inside a game directory (ie BCUxxxxx), it works.
Not sure what the actual issue is or if there is even a fix for it...
I did use hermes v3 before I switched to PL3, so I hope it hasn't messed stuff up...