I can't really make a simple title for this topic, so let me explain this:
When a TAS gets submitted that was made on an emulator that is known to be inaccurate and there are more accurate ones available, you can always try to make it sync on the best emulator. Sometimes it works, sometimes it doesn't. My idea is that the site should have a rule for this. Try to make the TAS sync on the most accurate emulator and if it does, require that exact version of the input file for publication! If it can't be made to sync and the old emulator is still allowed, you could still publish the original version.
I think this would help the site to make publications more legitimate and that's a very important aspect of TASing, a form of speedrunning that constantly needs to defend itself against accusations of cheating. What do you think?
Current project: Gex 3 any%
Paused: Gex 64 any%
There are no N64 emulators. Just SM64 emulators with hacky support for all the other games.
I'm just confused why some people still embrace mupen given all the problems during TASing, viewing and publication despite alternatives existing. Other than "easier to use" and "my TAS started in Mupen" I don't see why people still use them. :|
I'm just confused why some people still embrace mupen given all the problems during TASing, viewing and publication despite alternatives existing. Other than "easier to use" and "my TAS started in Mupen" I don't see why people still use them. :|
My guess is BizHawk runs awfully slow in their PCs.
I would switch to Bizhawk, but the TASeditor is hard to work with compared to FCEUX's.
Mainly the scroll speed...
I can't scroll through 1000 frames very fast if you only allow one at a time!
I was tired when I posted this and forgot how to think.
Why do we call it saving frames if we only plan to get rid of them?
Are you volunteering to do this for every submission then?
Wouldn't it make more sense to simply edit the site to stop accepting them? I mean, there there's a continuance list, so doing that for other emulators seem to make more sense than to cause endless frustration on viewing and encoding.
Are you volunteering to do this for every submission then?
Wouldn't it make more sense to simply edit the site to stop accepting them? I mean, there there's a continuance list, so doing that for other emulators seem to make more sense than to cause endless frustration on viewing and encoding.
Rejecting all movies but those using the single most accurate emulator for a particular system is very different from what was suggested and I'm pretty sure would make a lot of people upset.
The idea was that if the newest emulator is not required automatically, but only when it's possible to sync the movie on it, people would still be able to submit with older emulators if they have trouble with newer ones. As long as those older versions are still accepted. If we were to only allow submissions with the newest emulators, yes, that would upset people.
Current project: Gex 3 any%
Paused: Gex 64 any%
There are no N64 emulators. Just SM64 emulators with hacky support for all the other games.
Resyncing runs isn't just adjusting lag, the RNG can also cycle on lag frames and thus has a different outcome on an emulator which lags longer. So what want you do? Waiting until the random values are the same, which leads to a suboptimal run.
For every TASer who wants to start a run whould pick the recommended emulator from the site. If someone was already working on a run for a long time, before the new emulator existed, he/she can finish and submit the run with the old emulator.
The idea was that if the newest emulator is not required automatically, but only when it's possible to sync the movie on it
Again, who is going to be doing this work? You? It's a nice sentiment, but so is "everyone should have professionally landscaped lawns." What're you going to do when someone submits a run made on Gens or Visual Boy Advance (still acceptable right now, but not preferred)? Say "On top of the work you've already done, you need to do a bunch more work to try to sync it to another emulator even though the run you already have is acceptable." I can tell you now exactly how that'd go.
Joined: 4/17/2010
Posts: 11473
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
Trioct wrote:
I would switch to Bizhawk, but the TASeditor is hard to work with compared to FCEUX's.
Mainly the scroll speed...
I can't scroll through 1000 frames very fast if you only allow one at a time!
Is there any actual reason why FCEUX is problematic? No. A whole lot of its runs even syncs on console.
jlun2 wrote:
Wouldn't it make more sense to simply edit the site to stop accepting them? I mean, there there's a continuance list, so doing that for other emulators seem to make more sense than to cause endless frustration on viewing and encoding.
Let's simply make a continuance list for Mupen64, no other emulator is really that broken.
Let's not cause more problems with doing it than we have not doing it, so it should not be overdone.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
I was mostly thinking of cases where it wouldn't be too complicated to make it sync. If someone manages to do that with a submission, that file has to replace the movie. It already happens all the time that people fix small mistakes of a submitted TAS and it gets replaced. So why not doing the same thing here?
Current project: Gex 3 any%
Paused: Gex 64 any%
There are no N64 emulators. Just SM64 emulators with hacky support for all the other games.
Let's simply make a continuance list for Mupen64, no other emulator is really that broken.
Let's not cause more problems with doing it than we have not doing it, so it should not be overdone.
Sounds fair. Can this be done ASAP, since the longer it isn't the more TASes get started with mupen.
