|
|
GoldenEye 007 Nintendo 64 Community, GoldenEye X, Nintendo 64 Games Discussion GoldenEye Cheats, GoldenEye X Codes, Tips, Help, Nintendo 64 Gaming Community
|
|
|
|
|
|
|
|
|
|
|
zoinkity 007
Joined: 24 Nov 2005 Posts: 1686
|
Posted: Sat Sep 02, 2017 5:29 pm Post subject: |
|
|
Filesizes are determined at runtime by subtracting the ROM offsets from each other. If you set an entry equal to another entry, its size becomes zero. _________________ (\_/) Beware
(O.o) ze
(> <) Hoppentruppen! |
|
|
|
|
|
|
|
|
|
|
K1lo Agent
Joined: 10 Jun 2012 Posts: 112 Location: Albert Embankment, Vauxhall |
Posted: Sat Sep 02, 2017 6:06 pm Post subject: |
|
|
zoinkity wrote: | Filesizes are determined at runtime by subtracting the ROM offsets from each other. If you set an entry equal to another entry, its size becomes zero. |
aha.. interesting - of course this makes perfect sense. So actually I need to set the J pointer to the next E entry
Just tested it and can confirm - if I set the J pointer to be E + length of E block it works correctly
EVERYTHING now works as expected including reordering of text blocks in the ROM and the using of the extra space for large setup files...
Thank you SO much zoinkity - this was driving me nuts. Out of interest, how did you work out this was the issue? |
|
|
|
|
|
|
|
|
|
|
zoinkity 007
Joined: 24 Nov 2005 Posts: 1686
|
Posted: Sun Sep 03, 2017 2:46 am Post subject: |
|
|
I already knew how they generate filesizes, so when you wrote:
Quote: | For the J entries I've removed the data for from the ROM, I was just hoping to set the pointer to the equivalent E entry. |
-that was a dead giveaway. _________________ (\_/) Beware
(O.o) ze
(> <) Hoppentruppen! |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|