play .rts save in PC

Discussion in 'GBA - Hardware, Devices and Utilities' started by vrnikolai, Jul 7, 2015.

  1. vrnikolai
    OP

    vrnikolai Newbie

    Newcomer
    2
    0
    Jul 7, 2015
    Hi,
    I have been playing a game using the iPlayer GBA emulator on DS. However it doesnt use .sav files so I cant transfer them to the PC and use an emulator there. The problem is that the games that after you complete them they restart. After restarting there is no game to load since the .sav was not created.

    So I want to use the .rts save that the iPlayer emulator creates in a PC emulator, save there, complete the game there, create a .rts file and send it back to iPlayer.

    However I dont know how to do it or if its possible or there is a better way. Could you help me? Thanks.
     
  2. vrnikolai
    OP

    vrnikolai Newbie

    Newcomer
    2
    0
    Jul 7, 2015
    no solution? :(

    i noticed that if i use the restart function just after the game saves and before it restarts it retain the save game. however this isnt useful for pokemon since i want to keep the sav to use it for other things.
     
  3. FAST6191

    FAST6191 Techromancer

    pip Reporter
    23,348
    9,145
    Nov 21, 2005
    I am not aware of any, however the iplayer stuff later led to the ismm and dstwo GBA emulators so you might find something there.

    Alternatively if you know how to use a hex editor then you might be able to figure it out yourself. In both cases the games are being emulated rather than a more trick hardware based savestate. The basic concept of a savestate is very simple -- you dump the entire contents of the memory (save the ROM as that would make things large for no purpose), any registers and non memory mapped things that need saving (on the DS that would be the 3d system but on the GBA there is nothing I can think of offhand). To restore the savestate you simply do the reverse.

    Being this simple it is hopefully only some minor differences -- there is no great reason to scramble a savestate only times it will tend to happen is for paid emulators or something like a gameshark which does it.
    To that end make a savestate as soon as the game boots on each system. The memory should be fairly similar for both and you can then figure out the differences, or in VBA's case you can look at the source code instead. Hopefully it is something simple like one pads it out, the other does not, or one has the CPU stuff at the start and the other goes at the end.