Fixed selfgauss debug and other trace problem #566
Conversation
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
bxt_hud_selfgauss * 2 and below show singleplayer behavior * 3 and above show multiplayer behavior * Even numbers show coordinates of line traces * All reasons for failing to selfgauss are now shown * Threshold translated to time value, more intuitive * Hit group display may have been broken before, definitely works now to fix bxt_hud_selfgauss not working correctly, one condition was removed from ServerDLL::TraceLine. this needs to be removed or else the 2nd and 3rd line traces incorrectly say they hit an object at 0, 0, 0. since the condition was added to avoid a crash when playing a demo in bxt_hud_entity_info, all places that used a trace involving the player will now exit harmlessly if the player entity doesn't exist
This reverts commit afc8bba. oops
This reverts commit eb8c1cd. moving to non-master branch
bxt_hud_selfgauss * 2 and below show singleplayer behavior * 3 and above show multiplayer behavior * Even numbers show coordinates of line traces * All reasons for failing to selfgauss are now shown * Threshold translated to time value, more intuitive * Hit group display may have been broken before, definitely works now to fix bxt_hud_selfgauss not working correctly, one condition was removed from ServerDLL::TraceLine. this needs to be removed or else the 2nd and 3rd line traces incorrectly say they hit an object at 0, 0, 0. since the condition was added to avoid a crash when playing a demo in bxt_hud_entity_info, all places that used a trace involving the player will now exit harmlessly if the player entity doesn't exist
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
resubmitted #561 so i'm not using the master branch. same as before.
bxt_hud_selfgauss
to fix bxt_hud_selfgauss not working correctly, one condition was removed from ServerDLL::TraceLine. this needs to be removed or else the 2nd and 3rd line traces incorrectly say they hit an object at 0, 0, 0.
since the condition was added to avoid a crash when playing a demo in bxt_hud_entity_info, all places that used a trace involving the player will now exit harmlessly if the player entity doesn't exist