Skip to content

TR1X bug: Lara activates triggers one frame too early #2208

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

Closed
lahm86 opened this issue Jan 3, 2025 · 0 comments · Fixed by #2213
Closed

TR1X bug: Lara activates triggers one frame too early #2208

lahm86 opened this issue Jan 3, 2025 · 0 comments · Fixed by #2213
Assignees
Labels
TR1 TRX bug A bug with TRX

Comments

@lahm86
Copy link
Collaborator

lahm86 commented Jan 3, 2025

Regression from 1bcd325

TombATI on the left.

TR1EarlyTrig.mp4
@lahm86 lahm86 added TRX bug A bug with TRX TR1 labels Jan 3, 2025
@lahm86 lahm86 self-assigned this Jan 3, 2025
@lahm86 lahm86 moved this to In progress in TRX Dev tracker Jan 3, 2025
lahm86 added a commit to lahm86/TRX that referenced this issue Jan 4, 2025
This replicates how g_TriggerIndex used to work for Lara, by storing
her sector before calling any collision routines, and then passing
that sector to be tested for triggers.

Resolves LostArtefacts#2208.
lahm86 added a commit that referenced this issue Jan 4, 2025
This replicates how g_TriggerIndex used to work for Lara, by storing
her sector before calling any collision routines, and then passing
that sector to be tested for triggers.

Resolves #2208.
@github-project-automation github-project-automation bot moved this from In progress to Done in TRX Dev tracker Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TR1 TRX bug A bug with TRX
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant