Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Positional sound not playing if you walk into range #3559

Open
thePalindrome opened this issue Jan 13, 2016 · 10 comments · May be fixed by #14342
Open

Positional sound not playing if you walk into range #3559

thePalindrome opened this issue Jan 13, 2016 · 10 comments · May be fixed by #14342
Labels
Bug Issues that were confirmed to be a bug @ Client / Audiovisuals Sounds

Comments

@thePalindrome
Copy link
Contributor

thePalindrome commented Jan 13, 2016 •
edited by appgurueu
Loading

If a friend plops down the sound outside of our hearing range (defaults to 32), we will never hear this sound, even if we walk right next to where the sound is coming from.

Thoughts, anyone?
@est31 est31 added the Bug Issues that were confirmed to be a bug label Jan 13, 2016
@est31
Copy link
Contributor

est31 commented Jan 13, 2016

This sounds like that the close bystanders are only checked at the start of the sample, but not while its playing.

@est31
Copy link
Contributor

est31 commented Jan 13, 2016

IMO we should add the ability to connect sounds to SAOs. Then we get moving sounds for free, and solve this problem too (play a sound as long as the object is loaded by the client).

@thePalindrome
Copy link
Contributor Author

It does get tricky if a node is "playing" the sound, such as machinery.

There's no SAO for the node, and the client may have the node loaded from a hundred nodes away.

@paramat
Copy link
Contributor

paramat commented Apr 3, 2016

I guess the current system was designed for short sounds.

@paramat paramat added the Feature request Issues that request the addition or enhancement of a feature label Apr 3, 2016
@est31
Copy link
Contributor

est31 commented Apr 3, 2016

Still no reason to close it.

@paramat
Copy link
Contributor

paramat commented Apr 4, 2016

I'm not suggesting closing it, i didn't even add 'possible close'.

@paramat paramat added the Sounds label Jan 4, 2018
@paramat
Copy link
Contributor

paramat commented Aug 20, 2018 •
edited
Loading

Any core dev support for 'fixing' this?

@rubenwardy
Copy link
Contributor

This sounds like a bug to me

@paramat
Copy link
Contributor

paramat commented Aug 20, 2018 •
edited
Loading

Oops sorry, i shouldn't have treated something labelled as a 'bug' like this, my mistake.

@paramat

This comment was marked as off-topic.

Sign in to view
@Zughy Zughy added @ Client / Audiovisuals and removed Feature request Issues that request the addition or enhancement of a feature labels May 2, 2022
@sfence sfence linked a pull request Feb 3, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Issues that were confirmed to be a bug @ Client / Audiovisuals Sounds
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Send sound to players which comes to hear distance. sfence/luanti
6 participants
@sfan5 @thePalindrome @rubenwardy @paramat @est31 @Zughy