Not sure how relevant this post is, but meh. I actually do think there is something to the whole SRAM being a turn off and deciding not to make a TAS using it. Thinking about a couple things to make the process better.
1. Lack of Documentation. Actually finding articles about SRAM and how to use it is difficult on TASVideos currently. I did find
https://tasvideos.org/Glossary#SaveRam, but not SRAM. Also no article titles that that pops out for someone even looking for SRAM. Maybe some tutorials could help with visibility about acceptable usage. Are there even SRAM tutorials on TASVideos since having trouble finding them. Not even sure if there are ways to move SRAM between emulators which might improve things since tasers want to TAS games, not play through a long game to make a SRAM file and will probably want to use an existing SRAM from a different emulator. Probably need a full page about suing various emulator's SRAM and Dolphin in particular seems like it needs a lot of clarity up front.
2. SRAM Rules are hard to understand. Most people do not want to spend a long time having to dig and find articles and spend time trying to understand TASVideos' specific cases regarding them. I am all for making things more uniform. The current
https://tasvideos.org/MovieRules page also seems to have rules and info on SRAM in various sections as well instead of a grouped in one section which hurts understanding. Maybe even some kind of grid that shows acceptability for various goals could work. Like various Standard, Playground, Alternate goals on the Y axis, and then showing standard non saveRAM, save state, SaveRAM Fighting Game, SaveRAM Racing, (other?) for the y axis, and then in the box having a green "YES" for acceptable and a Red "NO" for not, and maybe OBS for Obsoletable()?. Something like that
3. SRAM Desyncs. See this happen a lot especially with certain emulators like Dolphin. So even if it works on one machine it may not work on another for some reason or another. Which means it may not even be judge-able to become accepted. So it becomes a more risky proposition to even attempt since in addition to stressing whether a submission will be accepted, the verification movie and SaveRAM/SRAM have to work correctly as well. Maybe some verbiage about encouraging to share the SRAM and asking others to see if they can run the file at several points during the TAS creation process could catch desyncs.
For one I do not think the term "SRAM" or even "SaveRAM" really means a lot to most people. So a more obvious term through the site could be better.
In summary. More tutorials, and more easily viewable rules in Articles section, and more uniformity for rules would help since all those exceptions are obnoxious, verbiage asking others for desync checks throughout process.