Thanks for the vote! I plan to do an Episode 2 TAS at some point in the future since a new trick has been found for it since Akse did his 3:02 TAS, but I likely won't do an Episode 3 or 4 one. I am heavily considering making a Doom 2 TAS, though.
It would also be great to see some 100% or Nightmare on this.
Yes, as Dimon said if you don't mind please use the PrBoom+ Source Port for superior results. Speaking of Smooth Demo Playback, if you do decide to use it, there is a setting "Smooth Demo Playback Factor" which changes, well, the degree of smoothness. 1 is the lowest setting with no real perceptible difference and 16 is as smooth as it goes. I think 6 is the default factor when the setting is on, but personally I think that 3 is the sweet spot. For the video I included in the original post SDP was turned off. SDP off would be obviously the closest to actual real gameplay but having it on makes it more enjoyable to the majority of viewers so I guess it depends on your thoughts about strict authenticity vs enjoyment.
At least that makes sense! I wonder how the system understood that skill "29" up there ( http://tasvideos.org/userfiles/info/62362112029546753 ) ; )
What is this message about: "ALERTS POSSIBLY COMPROMISING MOVIE INTEGRITY: Skill 3 1 players"? (top of the submission page) This is Skill 4... : P
Not to derail the thread but Dimon12321 (in addition to being a cool dude and encoding the Episode 1 TAS above) has in the past done an individual level e1m9 UV-Speed TAS. Here it is if you're interested. https://www.youtube.com/watch?v=H-soLcUdRbA
Within a single frame there are technically 93,645,180 different input combinations possible, accounting for the full range of running speeds, strafing speeds, turning angles, weapon changes, potential firing, and "using" switches and doors.
they encode keypresses that are then "played back" by the game
Hi, the problem with saving the entire filesystem is that loading the save state would lead to the user silently losing everything that has been written to the FS after the save state was made... Considering that's not how GameCube save states work and the fact it would affect entirely unrelated saves for other games as well, I feel uncomfortable making that change so consider it abandoned for now. Another issue is that it would bloat the size of save states and make them a lot slower as the Wii NAND can store ~512MB of data... It might be possible to only enable full FS snapshots in TAS mode, but that still requires some thought to design it well and ensure the UI lets the user know that save states would work differently in TAS mode
Some of the reasons from a year ago still apply today you're more prone to desyncs in PCSX2 compared to Dolphin.