Jump to content

BlackShark

Contributor
  • Posts

    1692
  • Joined

  • Days Won

    102

Everything posted by BlackShark

  1. Right click and set the modified Pokemon back to the slot.
  2. It will be possible once it is officially possible to transfer mons from older gens. Wait for Home to add SV support in a few months.
  3. You could import the pcdata.bin file from here Or individual PKM files from here
  4. Until transfering is officially possible through Home transfering through PKHeX won't be possible as well. Wait until Home gets updated in a few months.
  5. Double-click on the box tab will open an additional box view window. Now you can drag them from the one window into the other without having to save the files.
  6. What happened to this save? Did you use any cheats? Did you try to play it on an Emerald cart? Your save has strange data at places where Ruby/Sapphire would never write to.
  7. It might be possible to fix this. However save block 1 is gone. That's where your party and items are stored. I haven't tried but I think I could restore your save with a copy of the block from another save. Do you have any older backup of your save? Also to prevent future issues you should check your Supercard settings and see if you can get the save size set to 128KB. Edit: This is the best I could restore from your save by using block 1 from a new save: firered.sav
  8. Use the dev build until the next stable release.
  9. Unfortunately there is nothing to recover. The whole file is either empty or filled with garbage data.
  10. Use the dev build until the next stable release.
  11. Save ingame normally as you would on a real console, save states are not proper save files and can not be edited by PKHeX.
  12. Nothing wrong, that's a new feature of mGBA that adds RTC data to the end of the file. Use the dev build until the next stable release. For compatibility with other emulators you can use an hex editor to remove the last 16 bytes of your file.
  13. PKHeX currently doesn't correctly remove those two ribbons. Use an hex editor and clear offset 0x34 to get rid of them.
  14. That doesn't look like a valid file size. Did you get this file by saving ingame normally or by using save states from the emulator menu?
  15. Those are your ROMs, they only contain the game data not save data. You should find your saves as .srm files in the saves folder inside your Retroarch directory.
  16. The saves are not broken, it's a new feature of mGBA that adds RTC data to the end of the file. Use the dev build until the next stable release.
  17. Use the dev build until the next stable release.
  18. Use the dev build until the next stable release.
  19. It doesn't, 500 bytes are missing at the end of the file. If you add some 00s using an hex editor it loads fine.
  20. @theSLAYER @Koy Since version 0.10.0 mGBA now appends RTC data to GBA save files, like most emulators already do for GB/C saves. Use the dev build of PKHeX until the next stable release: https://projectpokemon.org/home/files/file/2445-pkhex-development-build/?changelog=6372
  21. PKHeX saves all of its settings to that file. It has nothing to do with your save.
  22. Don't worry it's not inappropriate. It was more my fault.
  23. I just saw you edited your previous post. The latest dev build without the RTC data is 7704-e2e22e2 https://mgba.io/builds/2/
  24. mGBA can still load saves from VBA and once you got rid of the last 16 bytes VBA will also load the mGBA save again. Any hex editor would do, but I recommend HxD https://mh-nexus.de/en/hxd/ Open HxD, drag your file into the window, scroll down to the end, mark the last line and delete it, then save the file.
  25. The latest versions of mGBA now append a 16 bytes footer with RTC information to the end of the save file. Until PKHeX is updated you can use any hex editor to remove the last 16 bytes and the save should be recognized again. @Kaphotics
×
×
  • Create New...