• Just a reminder that providing specifics on, sharing links to, or naming websites where ROMs can be accessed is against the rules. If your post has any of this information it will be removed.
  • Ever thought it'd be cool to have your art, writing, or challenge runs featured on PokéCommunity? Click here for info - we'd love to spotlight your work!
  • Dawn, Gloria, Juliana, or Summer - which Pokémon protagonist is your favorite? Let us know by voting in our poll!
  • Welcome to PokéCommunity! Register now and join one of the best fan communities on the 'net to talk Pokémon and more! We are not affiliated with The Pokémon Company or Nintendo.

[Other✓] XSE Free Space Finder

Anthroyd

Professor
  • 211
    Posts
    9
    Years
    I'm hacking Emerald. If I start a script with #dynamic 0xE40000 or greater, then on compilation I get an error stating: "Not enough free space found. Cannot compile." This is strange because if I open my ROM in HxD, the data from 0xE40000 to 0x2000000 (I've expanded my ROM) is filled with FFs, denoting free space. This problem persists when attempting to compile to a 16 MB ROM as well. Does anybody know why this is happening?
     
    Last edited:
    Try the 0's in a ROM. I haven't looked into emerald, but there are quite a lot of 0's. Also, try using a bit of a low estimate.
    Again, since I don't hack it, these are theory and things to try. Make sure to back up your ROM first.

    Good luck and happy hacking!
     
    I once had that problem it's actually the program itself I had to download a different FSF for it to work good
     
    I might be a bit late here, but that's one of the things that really suck at XSE... XSE still thinks that 0x0 bytes are freespace in emerald, which is simply false, because they are mostly tilemaps or soundtracks. To fix this, you need to do a #freespace 0xFF in front of the script!
     
    I might be a bit late here, but that's one of the things that really suck at XSE... XSE still thinks that 0x0 bytes are freespace in emerald, which is simply false, because they are mostly tilemaps or soundtracks. To fix this, you need to do a #freespace 0xFF in front of the script!

    Actually, I hadn't found an answer yet since I was just filling up all of the free space up until FSF stopped working. I just tested out your method and it worked! Thank you so much! You saved me a lot of hassle. :)
     
    Back
    Top