I tried making my first TAS of the PS1 Metal Slug 1. I controlled two players at a time by myself and spent over SIX tedious hours making it to the end on the hardest setting with no deaths. I though it would look really impressive but then when I went to hit stop recording, I realized I forgot to hit the record button all the way back from the start. Please, is there ANY way to get it all back? I haven't closes it yet and I won't until I get a definitive answer but is there SOME way I can replay it to get recorded? I really don't want to redo all of it. PLEASE HELP.
Brock Lee,
I'm sorry, but there is no way to recover it if it was not recorded. The emulators that we use here are very unforgiving (I've had a few problems before that cost me a lot of time and wasted work).
The only way to make sure everything works as intended is to verify it, over and over (we normally do TAS projects in separate sessions over many days, rather than in one session). One should also make backups.
The principle to follow when working on projects on a computer is 'save early, save often'. I've been bitten by crashing programs and power outages too often.
Save early, save often, make backups (wouldn't want to blow away all your work by accidentally loading an early savestate and recording from there, for example), and take time to verify that your movie actually works, especially if the emulator you're using is prone to desyncs. Otherwise you're liable to lose a lot of work.
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
I think this or something similar has happened to all of us, sadly you can’t do anything about it but it’ll teach you to be more cautious in the future
Emulators could record input by default and save them often as one big timeline (per ROM loading event), possibly with special markers (comments, chapter indices etc). Then the user can export and/or edit it as a TAS.
Emulators could record input by default and save them often as one big timeline
I don't think that's a good idea because those files might get large.
A better idea is that if the emulator is recording, it very visibly shows that (eg. with a blinking "recording" symbol.) That way if you are not recording, you will clearly see it.
OpenMSX can be set to automatically record whenever you start a game. (Do note that it has got a reverse feature, rather than traditional savestates) - you only gotta remember to save the replay when you're done recording.
Emulators could record input by default and save them often as one big timeline
I don't think that's a good idea because those files might get large.
A better idea is that if the emulator is recording, it very visibly shows that (eg. with a blinking "recording" symbol.) That way if you are not recording, you will clearly see it.
Or use lua
if movie.active()~=true then gui.drawbox(29,29,140,39, "red") end
if movie.active()~=true then gui.text(35,31, "!! MOVIE NOT RECORDING !!") end
Joined: 10/12/2011
Posts: 6442
Location: The land down under.
MUGG wrote:
Warp wrote:
creaothceann wrote:
Emulators could record input by default and save them often as one big timeline
I don't think that's a good idea because those files might get large.
A better idea is that if the emulator is recording, it very visibly shows that (eg. with a blinking "recording" symbol.) That way if you are not recording, you will clearly see it.
Or use lua
if movie.active()~=true then gui.drawbox(29,29,140,39, "red") end
if movie.active()~=true then gui.text(35,31, "!! MOVIE NOT RECORDING !!") end
Agree, in my Salaryman tas I ended up wanting to die because I was at an unforgiving level (Microphones). MUGG solution is the best.
WebNations/Sabih wrote:
+fsvgm777 never censoring anything.
Disables Comments and Ratings for the YouTube account.Something better for yourself and also others.
I can't believe anyone spent 6 hours just recording and never had to switch to Read-Only (e.g. in order to rerecord a segment from a frame for which he doesn't have a savestate, or in order to check some finished parts). This would be ridiculously ineffective setup, you simply can't make a good TAS this way.
Six hours to make a TAS is nothing, it takes many players months to make a proper one, so don't feel too bad about losing work. No doubt you've learned plenty by doing that initial run; so it's not a total loss. You at least now know routes, boss strategies etc, and hopefully your experience might give you new ideas on how to improve the beginning of your movie; warranting a new run to be created.
And as others have stated, if you've only realised you're not recording by the time you get to the very end, we can't help but question the quality of your TAS to begin with. It's like Steven Spielberg shooting every scene in a film, then saying 'whoops, I forgot to add film to the camera, during every single part of the movie'.
So not once did you think "Hmmm, I need to rerecord from frame 1500, but I only have savestates for 1400 or 1600. OK, so that means I'll need to play it in read-only mode so I can advance to 1500, and make a new savestate from there"? Not even curious to see how awesome your TAS looks so far, by viewing it from the start? Not even checking to see if your movie syncs properly? Not even viewing your movie in an attempt to pinpoint some variable's address in memory watch?
Just TAS it a second time, checking stuff out more thoroughly, and no doubt it'll be faster than your
first attempt anyway.
