Conversation
Vitroze
marked this pull request as ready for review
September 16, 2026 22:56
Owner
|
Manually calculating the attenuation is not the correct way to deal with this, plus it can cause confusion in the code given that it is applied on top of what the |
Owner
|
As for setting |
Contributor
Author
I'll look into integrating another solution instead of creating the "attenuation." |
This branch has not been deployed
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
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.
On certain maps, the sound distance is far too great, meaning an approaching motorcycle can always be heard despite the already low volume. This PR fixes the issue.
Fix : #352