TASEmulators
[Feature Request] TAStudio's non-save state marker, marker.
I only realized this whilst using Encore and then thought about it. Basically a way to have a main marker that acts as a state (so what Hawk currently has) and then secondary markers to be like where something works, and you want to check around it and it goes back to that main marker. This would also presumably reduce the filesize of tasproj files if used effectively by the TASer.
Like for an example on what I mean by "where something works" when I TAS Tekken I place markers on where something connects the opposing player, and I want to know that it can be there, and check around that frame instead of having that as a state, I can have that as an idea of "Yes, I can confirm that they get hit here, but I want to know what happens if I do this instead".
Isn't this just branch + marker? Set a marker on the interesting frame, and save a branch on the inputs that work well. Then you could experiment and go back to the branch if you aren't successful.
It's different to branch + marker. Since what I'm saying is without the use of using a branch, and again this is more a specific use case with Encore which will drop a save no matter which marker you're doing increasing the size of the tasproj file, trying to avoid that.
It's also a spur of the moment in the progress, not a multiple revisions type thing that branch is there to help for.
This feature request piqued my interest because I've been thinking about marker-related improvements for a while, and on a re-read I guess the feature request is for certain markers to not have savestates associated with them for cores with memory-intensive cores like Encore? (The current default having been for a while that all or most(?) savestates have attached savestates associated with them.)
I am wary of increasing the complexity of using markers, but this might fit well with some other features I want for markers.
