It seems that it would only happen when the ping was above 125 and/or the packet loss was above 0% on the client. The issue I believe lies with multiple “Root” channels being created and entered, meanwhile there’s only meant to be one.
I used the latest artifact version (2745), with the default cfx-server-data resources and just a simple ‘test’ resource as already mentioned. Steps to reproduce: I was able to consistently reproduce this issue on two hosts. At that point I hadn’t done much investigation into the issue, and I figured if I get could some more information on it, it would be easier to pinpoint exactly what’s causing this.Įxpected behavior: Upon joining the server, the Mumble voice chat should be working from the start, without requiring the clients to reenable their voice chats in their settings in order to start hearing each other.Īctual behavior: In order to use the voice chat and hear other people, some clients will have to reenable their voice chat in the settings.
Summary: Yesterday I mentioned that my friend and I were having some issues with the Mumble voice chat upon joining the server in this message here, posted in the FiveM discord guild. System specifications: Tested on “Client 1” as well as a dedicated server with these specifications. Resources: cfx-server-data resources and a ‘test’ resource to quickly teleport all the clients to the same place. Operating system: Windows Server and Windows Home (both tested) System specifications: Client 1 (My PC - located in EU (West)), Client 2 (My Secondary PC on the same network) and Client 3 located in NA (East).
MUMBLE VOICE CHAT SWTOR WINDOWS 8 WINDOWS 10
Windows version: Windows 10 - Version 2004
0 kommentar(er)
