TRX bug: old custom levels cause floor data parsing issues #2114
Comments
lahm86
added a commit
to lahm86/TRX
that referenced
this issue
Dec 26, 2024
This will handle cases in old levels where a sector has multiple trigger entries. Officially only one is supported, but it seems old levels use this approach to add dummy triggers for such things as bridges on top of pre-existing triggers. This would have worked with the old g_TriggerIndex approach because of the way floor height tests were performed. Instead now, if we detect a trigger but the sector already has one, we simply append the new commands onto the existing trigger. Resolves LostArtefacts#2114.
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Old levels that seem to have been built with Dxtre3d sometimes have multiple triggers defined for a sector (which is technically invalid). See about adding backwards compatibility for this.
Ref: #2112
The text was updated successfully, but these errors were encountered: