Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] TAStudio's non-save state marker, marker. #3892

Open
Spikestuff opened this issue Apr 14, 2024 · 2 comments
Open

[Feature Request] TAStudio's non-save state marker, marker. #3892

Spikestuff opened this issue Apr 14, 2024 · 2 comments
Labels
Enhancement For feature requests or possible improvements Tool: TAStudio

Comments

@Spikestuff
Copy link

Spikestuff commented Apr 14, 2024

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".

@YoshiRulz YoshiRulz added Enhancement For feature requests or possible improvements Tool: TAStudio labels Apr 14, 2024
@Morilli
Copy link
Collaborator

Morilli commented Apr 14, 2024

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.

@Spikestuff
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement For feature requests or possible improvements Tool: TAStudio
Projects
None yet
Development

No branches or pull requests

3 participants