Fix for single segment trails#6864
Merged
Merged
Conversation
Baezon
added
fix
BMagnu
approved these changes
Jul 26, 2025
Kestrellius
pushed a commit
to Kestrellius/fs2open.github.com
that referenced
this pull request
Jul 26, 2025
* fix single segmen trails when interrupted on both ends * cleaner case handling * remove wip stuff
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Handles a previously unhandled case where a single segment trail could be interrupted on both ends at once, not yet finished 'unfurling' from being fired, and also the trail object has died. The math here is a little confusing perhaps... but this involves having the back end's
valstart at -1.0 and start incrementing right away, rather than waiting at 0.0 to finish unfurling, which gives enough information to reason about the correct alpha, width, uv etc in any state.