Post: Static Destiny offset
Options
10-29-2014, 10:26 PM
#1
BedWetting
Banned
The following user thanked BedWetting for this useful post:
10-30-2014, 06:54 AM
#11
FarSideX
I’m too L33T
Originally posted by BedWetting
that's fine, just downgraded 5 ps3s today more cids, if you need any also let me know not worried about any bans thanks
Just curious, do you inform those you do downgrades for that you are going to take their CID? I only ask because someone PMed me stating they were CID banned from PSN less than a week after getting their PS3 downgraded, asking if this was normal as the downgrader did not say they were going to steal their CID. They did not state who did the downgrade.
As for having static data in the 7000000 range, it is semi-possible unlike what others will tell you. Ranges above the C0000000 range tend to be treated like stack memory and not heap memory, as long as the data does not go out of scope it will behave like static memory locations. The stuff that moves around without any in game changes is in the heap memory areas. These areas are well documented in the GCC compiler docs. Since the gameOS is a virtual machine exposing a virtual 4 GB of memory (it's really only ~190 megs), the GCC tends to use default PPC values for memory usage and lets the hypervisor sort it all out. This is the way I understand it to be and may have errors as this is based on the default GCC settings.
10-30-2014, 06:47 PM
#12
BedWetting
Banned
Originally posted by FarSideX
Just curious, do you inform those you do downgrades for that you are going to take their CID? I only ask because someone PMed me stating they were CID banned from PSN less than a week after getting their PS3 downgraded, asking if this was normal as the downgrader did not say they were going to steal their CID. They did not state who did the downgrade.
As for having static data in the 7000000 range, it is semi-possible unlike what others will tell you. Ranges above the C0000000 range tend to be treated like stack memory and not heap memory, as long as the data does not go out of scope it will behave like static memory locations. The stuff that moves around without any in game changes is in the heap memory areas. These areas are well documented in the GCC compiler docs. Since the gameOS is a virtual machine exposing a virtual 4 GB of memory (it's really only ~190 megs), the GCC tends to use default PPC values for memory usage and lets the hypervisor sort it all out. This is the way I understand it to be and may have errors as this is based on the default GCC settings.
As for having static data in the 7000000 range, it is semi-possible unlike what others will tell you. Ranges above the C0000000 range tend to be treated like stack memory and not heap memory, as long as the data does not go out of scope it will behave like static memory locations. The stuff that moves around without any in game changes is in the heap memory areas. These areas are well documented in the GCC compiler docs. Since the gameOS is a virtual machine exposing a virtual 4 GB of memory (it's really only ~190 megs), the GCC tends to use default PPC values for memory usage and lets the hypervisor sort it all out. This is the way I understand it to be and may have errors as this is based on the default GCC settings.
I buy motherboards only and consoles they are my ids and I sell them
I
10-30-2014, 10:21 PM
#13
Cyb3r
NextGenUpdate Elite
Originally posted by FarSideX
Just curious, do you inform those you do downgrades for that you are going to take their CID? I only ask because someone PMed me stating they were CID banned from PSN less than a week after getting their PS3 downgraded, asking if this was normal as the downgrader did not say they were going to steal their CID. They did not state who did the downgrade.
As for having static data in the 7000000 range, it is semi-possible unlike what others will tell you. Ranges above the C0000000 range tend to be treated like stack memory and not heap memory, as long as the data does not go out of scope it will behave like static memory locations. The stuff that moves around without any in game changes is in the heap memory areas. These areas are well documented in the GCC compiler docs. Since the gameOS is a virtual machine exposing a virtual 4 GB of memory (it's really only ~190 megs), the GCC tends to use default PPC values for memory usage and lets the hypervisor sort it all out. This is the way I understand it to be and may have errors as this is based on the default GCC settings.
As for having static data in the 7000000 range, it is semi-possible unlike what others will tell you. Ranges above the C0000000 range tend to be treated like stack memory and not heap memory, as long as the data does not go out of scope it will behave like static memory locations. The stuff that moves around without any in game changes is in the heap memory areas. These areas are well documented in the GCC compiler docs. Since the gameOS is a virtual machine exposing a virtual 4 GB of memory (it's really only ~190 megs), the GCC tends to use default PPC values for memory usage and lets the hypervisor sort it all out. This is the way I understand it to be and may have errors as this is based on the default GCC settings.
I am sure you have a good knowledge but what i meant is i know destiny and that region only stores dynamic values, infact there's no static values in destiny.
The following user thanked Cyb3r for this useful post:
Copyright © 2026, NextGenUpdate.
All Rights Reserved.
