Victoria, AustraliaThe 3:33.62 time from @Alias_ncnc skips 0-D and doesn't return to it.
Retiming it lands on a 3.696 (title runs at 23fps).
Or does the TAS Tools built into Dolphin still make that an issue due to the risk of someone out of nowhere coming in and cheating?
Just letting you know that PCSX2 also has the TASing tools, and Dolphin isn't accepted for a different reason being that it runs the game absurdly differently to an actual system (GameCube is considered the weakest version between the three).
All times in the Individual Time Attacks are listed as Real-Time and not In-Game Time and some accidentally slip through the cracks.
Just going to clarify at the start.
None of this is a knack on you it's all done to point out clarity, so if it comes of wrong or aggressive, that wasn't intended.
It's good to see a Dreamcast submission just that the description has a lot of unintentional misinformation in regards to emulation.
In regards to the Emulator, I went by the guidance of the TASVideos Archive page.
The one that's actually on TASVideos isn't brought up in the TASVideos Discord discussion (what you link to). Nor the page of the actual core requests in the github (or the issue requests).
There is no official tool available for Dreamcast Emulation however many community members including Spikestuff has been using Flycast for TAS.
There has not been a single instance of a completed TAS using Flycast emulator nor any other Dreamcast emulator, due to the complexities of needing to use libTAS (Linux) and the fact everything that I have done with not only Dreamcast emulation, have been experimental to see what sticks. In Flycast's case the thing it fails the most at which is why no one has made a proper TAS of it is due to no feasible way to actually dump the audio from the game.
Run was made before the rules were established @SuperDfar.
So before you even think about riding a high horse how about you actually learn a little thing called history and rule development and follow the rules you're actively breaking that are current. Rather than focus on a run that got grandfathered in.
Or y'know just don't act like you know something when you clearly don't.
QT is fine, NoGUI is no longer supported by DuckStation.
As long as you can get the special menu up which is requested (there's a hotkey where you can do this it's assigned to Escape on default) then you're generally fine.
It would be roughly a 12.433 with your timing:
[quote=FuzionSynth]Would DuckStation be acceptable in the future?[/quote]
You missed the brief period of time where DuckStation was an acceptable emulator for CTR. As outlined and explained here CTR wants to keep it to a single static emulator and that emulator is mednafen.
Rogue moderation abuse by Stormlight who was removed from Super Mod position by srcom site staff and restored a portion of the board.
That's the surface level explanation.
Great decision. So when's the decision where you're all stepping down as moderators?
Great luck, that the third place run, which is now looking at top run no longer has a video. The run would probably most likely fall under to lenient on timing, and would shove back a couple of milliseconds (or forwards if timing was adjusted).
But as another saying goes (even tho the run existed at one point). No Vid, No Did. Even if it's a Top 3 run.
I got curious cause it's the second place run, and it's a meme game (and it's only fair).
Once again the timer starts late and ends early but it's easier to see what's going on (honestly it would be easier if it started from black and ends at black). if the timing was correct to the rules it should be a 3:13.900 run, not a 3:13.600. Matching the timer to the runner's "start" it's actually a 3:13.800. And from black to black it's a 3:13.700.
The runner was too lenient with their own timing (which is fine) but it's good to go over it. If I get bored enough I'll look at all the other runs and make comments about the timing used on them.
I got curious cause it was top run, and it's a meme game. The game runs at 30fps, but the timer is at 24fps.
The timer starts late (honestly it would be easier if it started from black and ends at black). if the timing was correct to the rules it should be a 3:13.700 run, not a 3:13.160. Matching the timer to the runner's "start" it's actually a 3:13.633. And from black to black it's a 3:13.500.
Whatever program was used to time the run in post by the runner was extremely wrong. If I get bored enough I'll look at all the other runs and make comments about the timing used on them.
This is what Wookis is referring to, if you don't have it update your OBS:
Retimed this to the rules and it's a 4.478:
Also BabyPandaJ you submitted this as a 4.024 even though the timer shows 4.240. Keep an eye on those milliseconds in the future.
Retimed this to the rules and it's a 3.870:
(You can also see this when you download and step through the runner's video, but I wanted to go over it proper)
