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

Volvagia custcene "hardlocks" at all FPS settings (except default 20) #306

Open
Karma-Enthusiast opened this issue Apr 23, 2022 · 1 comment

Comments

@Karma-Enthusiast
Copy link

Hesitated to post this since I saw Lehpumeh already posted a few issues regarding custcenes. Feel free to remove this if you're already aware of the issue, not trying to clog the issues section.

Current Behavior

If you set the FPS at 30, 60, 120, or 240 before the Volvagia cutscene begins, the game will hardlock (or softlock? not sure which terminology is right, but you can't pause and you have to restart the game) at the end of the cutscene when Volvagia hides inside of her lava crater.

Expected Behavior

Regardless of FPS, the cutscene should stop after Volvagia re-enters one of her lava holes, and you should regain control of link.

Possible Solution

No idea, but given that Volvagia's body also shrinks in accordance with the FPS (higher FPS = shorter Volvagia), my best guess is that: the cutscene is synced to the FPS, and the FPS is synced to Volvagia's movement, so when the game doesn't detect her entering the lava hole at the time she's supposed to, it doesn't know how to properly end the cutscene. No clue otherwise :D

Steps to Reproduce

(trying something new with the video url this time, hopefully it actually shows a video, sorry in advance if it doesn't, you'll have to open in a new tab)

Volvagia Cutscene Crash

  1. Get to the Fire Temple, acquire the boss key, and choose any FPS setting other than 20 before the Volvagia cutscene starts.
  2. Hardlock occurs after Volvagia sinks back into one of the lava holes.
@XS09-dev
Copy link

Yes I told blawar this already.

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

2 participants