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

Replay information and CPU option 🕹️ #1731

Open
alicemsu opened this issue Mar 21, 2024 · 4 comments
Open

Replay information and CPU option 🕹️ #1731

alicemsu opened this issue Mar 21, 2024 · 4 comments

Comments

@alicemsu
Copy link

To begin with, I would like to suggest something. The CPU option should be limited to 600%, instead of the current 400%. (Remember that this can only be done by entering the values manually). This is a suggestion for Metal Slug games, where 533% is equivalent to 64 MHz, as in WinKawaks, which is the configuration used in Metal Slug speedruns according to the Speedrun.com page. The 600% is suggested solely to round off the value. Please make the CPU option activate with the F4 key (currently this key has no assigned function). I have already tried this in several games and the clock does not affect anything.
cats2

To conclude, my last suggestion is that when saving the replay file, it should be possible to see in the file's information at what speed or value the game was played when recording. It would be very useful.
cats

Please, accept my suggestion!

@dinkc64
Copy link
Collaborator

dinkc64 commented Mar 22, 2024

Hi alicemsu,
It's a good idea!
I can't promise anything because my todo list is 10 miles (16.0934km) long :(
notes:
I don't see a problem to change the range for the cpu speed from xx - 600%, but, if we make a change for the recordings, it will require recording version # to change again (old recordings won't play in new fbneo with this feature)

@alicemsu
Copy link
Author

alicemsu commented Mar 22, 2024

@dinkc64, I understand you have a lot of work, but I hope my suggestion can be completed. It's a pity that old recordings won't be able to run correctly if you make these changes, but I think it's necessary, as people who review records on speedrun.com or generally on TAS support pages will have an easier time verifying at what speed the game or file was recorded. I say this because, for example, if I record the game at 534% or a slightly higher value, when I play back the file at 533%, those files I played will sync strangely, not having been recorded at 533%. The information in the file will be essential to eliminate doubts about small cheats. Sometimes the clock isn't precise, but this will be the definitive solution to clear doubts. Finally, don't forget it would be great if the slider option opened with the F4 key. And hopefully, when selecting the file and before executing it, the game will automatically play back at the speed it was originally recorded.

@Zansword
Copy link

long time no see dink,
i guess very old version before cpu values change into float, most of before replays won't be work correctly.
i think it will be hard to change cpu values settings, but i guess it is no problem for adding replay information and its settings.
this will be very useful to replay recorders. dink, even though you still have a long way to go,
i also hope that alice's request received in the end. hope fbneo last forever :)

@alicemsu
Copy link
Author

@dinkc64, I forgot to thank you for responding. Once again, thank you very much, and I appreciate your effort. I hope what I said can be understood, since my English is not the best. But if there are any questions, I'll be here to answer. Greetings 🫂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants