So let's just address the big issues right off the bat - the TASVideos community isn't used to having to put up with desyncs on playback as a part of life, and the concept of having to do a segmented encode attempt seems ridiculous. Investigations into how Unity handles RNG have led folks to the conclusion this problem may never be solvable due to the sheer complexity of it, so unfortunately this isn't a matter of waiting for emulation or tooling to improve. We the TASVideos community have absolutely rejected runs that couldn't sync in a single setting, but that's just the norm for the Hollow Knight community.
On the topic of desyncs with HK tases which we didn't mention yet is that movies sometimes don't sync on other devices and sometimes even don't when switching between WSL2, VM and dual boot on the same system. Also the latest interim build of libTAS has caused existing TAS's to desync, likely because the stack smashing issue with loading save states that was fixed.
Also on segmented encodes, yes sometimes we do encode in segments because of the desync issues. But there are also quite a few who segment the whole tas into multiple libTAS movie files because of the desyncs. This is especially done on patch 1.4.3.2, and on patch 1.2.2.1 it is done as well, but less segmented than 1.4.3.2.
And yes the desync issues are patch specific, likely because of the difference in Unity versions. Patch 1.0.2.8-1.2.2.1 are on Unity 5.4 and 1.4.3.2 is on Unity 2017.4.
dwangoAC wrote:
They'd also have to.. um... potentially rename some of their meme categories to meet site decency requirements. Maybe. One of their categories is Bench Out-Of-Bounds, and that one has a comparatively tame acronym. I'll let you be the judge. :)
Bench Out-Of-Bounds is a glitch, not a category. The only category that would be indecent is All Stag Stations.