My problem with 223 was actually that read only still didn't work right. I have still never actually had any problems continuing to record a .dtm on a different version. I now have .dtms that were recorded on 6 different versions of dolphin.
Why are you not using 234+? Read only is not working until 234. There is then another bug with it that is fixed in iirc 291, so i'd recommend using at least that. You should not have any issues switching to a later revision, except possibly the desync at the opening you mentioned a while back, which you could hopefully hex edit.
Why are you not using 234+? Read only is not working until 234. There is then another bug with it that is fixed in iirc 291, so i'd recommend using at least that. You should not have any issues switching to a later revision, except possibly the desync at the opening you mentioned a while back, which you could hopefully hex edit.
Well, I guess that's my only option then. My game isn't very hex-friendly, but even if I have to remake it from the beginning again, this should hopefully be the last time I have to do so.
EDIT: Turns out, with a combination of the latest Dolphin's fixed read-only mode and HxD, I don't have to remake my movie from the beginning, since hardly anything desyncs in new revisions, and never by more than two frames. I'm really glad I gave in and switched to the new revision.
Just compiled the more-save-fixes branch. Took me a while to get it working, but whatever, i wanted to figure it out eventually anyway:
http://www.mediafire.com/?cl7bq40bimx14eb
Just compiled the more-save-fixes branch. Took me a while to get it working, but whatever, i wanted to figure it out eventually anyway:
http://www.mediafire.com/?cl7bq40bimx14eb
Which "more-save-fixes" is it? Is it the latest one (from 28 hours ago)? If so, thanks! I can restart my movie on this revision.
It should be this.
It looks like the master branch hasn't been merged to it in a couple weeks, but nothing really seems too important there. I've already started using this one myself, and it's definitely a nice improvement.
As far as i know. I downloaded it with git clone -b more-save-fixes https://code.google.com/p/dolphin-emu . Unless i screwed that up, it should be the most recent revision to the branch.
My movie no longer syncs as of this change, so anyone who can easily restart might want to do so now.
My movie syncs about 3.5 minutes in, then gets about 2 frames behind and that messes up everything. It could probably be fixed easily by hex editing, though.
What I like about that revision is the faster speed and smoother sound when playing back movie files (and probably real-time playing, though I haven't tried that yet). I haven't tried a 3.0-3xx revision since the "more-save-fixes" build rog posted earlier, but I'm happy the game speed is faster without the emulation of the game being any less accurate. In a particular area of my game, Dolphin r7719 ran at 73% speed in real-time (no movie recording), dual-core and idle skipping on. But the next version I downloaded, v3.0-179, ran at 56% in the same area with the same settings. So it's good that the games are starting to run faster again.
Also, I'm still finding with v3.0-305 that after recording or playing back from a savestate, it is best to close Dolphin before playing back your movie from the beginning. Every time I forget to close Dolphin in the rare times I play my movie from the beginning, it desyncs in the exact same spot no matter how far I have gotten in my TAS. Other than that, it works great; I'm so glad I switched revisions!
Joined: 9/21/2009
Posts: 1047
Location: California
Mapler and I would like to resume our SA2:B TAS, but neither of us have been keeping up with Dolphin as much as we used to. At this point in time, which version has the most reliability in terms of savestates, movies not desyncing, and read-only? Can I have a download link to it as well?
Pretty sure the newest version of the more-save-fixes branch is the best right now, though i haven't tried anything after this change, so i don't know if there are any bugs introduced after that. However if you use anything before January 4th, you won't be able to update to a newer version later, as your movie won't sync anymore.
If you want the version i'm using, there's a link on the last page, otherwise if you want the newest version of the more-save-fixes branch, you'll need to compile it yourself, or if you can't, i could do it for you in a little bit, if you want.
Pretty sure the newest version of the more-save-fixes branch is the best right now, though i haven't tried anything after this change, so i don't know if there are any bugs introduced after that. However if you use anything before January 4th, you won't be able to update to a newer version later, as your movie won't sync anymore.
Pretty sure the newest version of the more-save-fixes branch is the best right now, though i haven't tried anything after this change, so i don't know if there are any bugs introduced after that. However if you use anything before January 4th, you won't be able to update to a newer version later, as your movie won't sync anymore.
Ah okay sorry. Then I looked at the wrong fixes.
Would it be a good idea to wait till it is merged? There seem to be a lot of other fixes that were made in the main line since then. So at the moment you would have to decide between different iportant fixes, right?
Eh? Unless i'm missing something the only changes to the master branch since jan 4th, when it was merged to more-save-fixes are optimizations, which don't matter at all for tasing, and a crash fix for an option you should not be using.
but the normal branch (3.0-371) may also be a good choice.
Absolutely not. The save state fixes have entirely eliminated all desyncs for me. I'm now 120k frames in since 305 more-save-fixes, and have not had even a single desync. With previous versions i would have expected 1-3 dozen desyncs in that time. Using any version that does not include the save state fixes seems absurd to me at this point.
OK, well I haven't TASed on any recent normal branch revisions, and it appears I'm wrong, so just ignore that part of my sentence.
I also have not had one single desync in 35000 frames with "more-save-fixes" (I would be farther ahead in my movie, but I'm still trying to optimize one area). No desyncs so far is really fantastic, considering I would definitely have had 7-8 desyncs by now on an older revision, like 3.0-191.
OK, then I definitely recommend the newest more-save-fixes Dolphin (in the link rog posted above).
