(adsbygoogle = window.adsbygoogle || []).push({});
So if i may ask, why does everyone say there is an 'injection limit' for GSC size on PS3? Im pretty much 100% certain there is no such thing and that the block of memory we are injecting at just isnt big enough. Anyone have any rebuttals? If you say there is, please provide actual evidence and not 'i tried to inject xyz and it didnt work so there has to be' and more like 'size must be less than uint maxvalue' or something legitimate
. Thanks.
Answer explained for those who did not understand initially:
1: The only limit to GSC is the maximum memory partition you can reach before overwriting crucial system information or other files loaded into memory. This means that by finding a bigger memory space, you are able to inject much larger files.
2: The technical limit to GSC is impossible to reach, but is a fun trivia piece of information for those who want it (uint max value: 4294967295 bytes ) because GSC specifies file size in uint as a compilation parameter.
3: 0x51000000 will give you approximately 7.5MB of space for your GSC. (Not 100% sure of size because it was a tool i made that detected it and the tool cant handle non existant mem regions, but, its still a fuckload)
I have personally tested injection to this offset and it works fine. Only bug is that this apparently sticks in memory after ps3 restarts (no idea why, must be something important
) so you will need to null out the space before injecting, but elsewise, enjoy.
Credit for this 'discovery' if you could call it that, would be nice. Thanks. Admins, you are good to close it.