Usage of routing buckets

[avarianknight]

Usage of routing buckets

[AvarianKnight]

Hey, so first off the idea behind the 'updateRoutingBucket' export is for it to be called after you set the routing bucket in another resource.

So lets say if you're in esx_property and you change the players routing bucket then you would do the following code inside esx_property

SetPlayerRoutingBucket(src, routingBucket)
exports['pma-voice']:updateRoutingBucket(src)

Secondly, the max routing buckets is currently 0-63 (64 in total (this could be outdated, they did recently change routing buckets more)) so you couldn't do instance.host+2000 first off, as it would be out of bounds for the SetPlayerRoutingBucket, and secondly the server only makes 220~ channels (making more than 1000~ leads to the mumble server completely dying, don't recommend trying).

I'm not sure how they're still managing to talk between zones (as the offset is something along the lines of 31 + (0-63 * 2). I could understand if they're hearing each other if they're in one of the lower zones (which I'll release something here soon to hopefully fix it, if it is that).

[bitlewis]

Thanks for your input, I'll attempt to make it work with the routing buckets further and will report back.

Also thanks for the pointers towards the channels, I'll for sure look this up. This will restrict the amounts of radio channels we can use for sure.

[AvarianKnight]

Thanks for your input, I'll attempt to make it work with the routing buckets further and will report back.

Also thanks for the pointers towards the channels, I'll for sure look this up. This will restrict the amounts of radio channels we can use for sure.

Radio channels aren't done through the same system that voices are (voices are done through mumble channels, while radios are just setting a players volume override for them), you can have as many radios as you want and it wouldn't affect anything (To my understanding.)

[bitlewis]

Makes sense. I thought radios were tied to mumble channels.

Would you have any other ideas to implement instancing without voice across instances in the same location?

It was once possible using the two following natives:
NetworkSetVoiceChannel()
NetworkClearVoiceChannel()

However it appears that the sync from mumble/pmavoice overlaps this therefore you can speak to other players inside the instance.

[AvarianKnight]

The issue was that if they were in 1 routing bucket difference they could still hear each other (which should be fixed on the latest update).

[bitlewis]

Thanks for the info. I'll keep searching to figure how I can make players not hear each other inside instances outsides of buckets, otherwise might have to use them.

[AvarianKnight]

Thanks for the info. I'll keep searching to figure how I can make players not hear each other inside instances outsides of buckets, otherwise might have to use them.

Try the latest update and see if it works for you

[AvarianKnight]

Going to close this as there is no issue.

[YisusOnDev]

Hi, recently moving mumble-voip to pma-voice because pma' already support routing bucket "voice", but, i think i found a problem, when i enter an instance:

SetPlayerRoutingBucket(src, routingBucket)
exports['pma-voice']:updateRoutingBucket(src)

first join hear others but others doesn't hear the first who join. (Only tested with 2 persons.)

Maybe i'm using to high ids? (5 digits ids), cause with for exmaple id 5 its seems to work?

How much higher can i go with
exports['pma-voice']:updateRoutingBucket(src)?

Thanks