Changes between Version 19 and Version 20 of Ticket #15303
- Timestamp:
- Aug 2, 2024, 10:22:30 AM (7 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #15303 – Description
v19 v20 18 18 What seems to happen is that if `GetTime` is close enough to 32,767, adding the duration causes `ticks` to become negative. Which means that `GetTime` is immediately greater than `ticks`. 19 19 20 I believe this means that the glitch could happen at any point in the game, and I was just lucky (?) to catch it here. And the same mechanism seems to be present in several other games, but no one ever noticed. I blame the lengthy cutscenes in LSL5 for triggering it.20 I believe this means that the glitch could happen at any point in the game, and I was just lucky (?) to catch it here. And the same mechanism seems to be present in several other games, but no one (?) ever noticed. I blame the lengthy cutscenes in LSL5 for triggering it. 21 21 22 22 I imagine it should be possible to fix, at least on a case-by-case basis. The arithmetic workarounds seem like a reasonable place to start, but it might need some extending to call a custom C++ function to do the comparison? We know that `ticks` should stay constant until the text box is dismissed.