Skip to content

NetworkIsPlayerTalking / MumbleIsPlayerTalking always false for the local player #4347

Open

Description

@MXK7

What happened?

NetworkIsPlayerTalking(PlayerId()) and MumbleIsPlayerTalking(PlayerId()) always return false for the local player while speaking. Any HUD voice indicator built on these natives stays off.

We first noticed it around the client update that moved to CEF 144, but I am not sure that update is the cause. Our scripts did not change in that period, and the same thing happens on our local server and on our production server (external Murmur through voice_externalAddress). A similar bug was reported for the GTAV Enhanced client in citizenfx/rfc#179 and marked fixed in the August 4 patch. This looks like a regression.

Expected result

Both natives return true while the local player is speaking, as they did before.

Reproduction steps

  1. Start a client resource with:
    CreateThread(function()
        while true do
            print(("mumble=%s network=%s"):format(
                tostring(MumbleIsPlayerTalking(PlayerId())),
                tostring(NetworkIsPlayerTalking(PlayerId()))))
            Wait(500)
        end
    end)
  2. Join the server with voice chat in voice-activation mode.
  3. Speak continuously for a few seconds and watch the F8 console.

Importancy

Slight inconvenience

Area(s)

FiveM, Natives

Specific version(s)

Client FiveM* (b3751) [e3889] (Canary), with CEF 144 (not confirmed as the cause). Server FXServer-master v1.0.0.38220 linux, sv_enforceGameBuild 3751, Mumble voice.

Additional information

  • Diagnostic over 6 s of continuous speech: 12/12 samples mumble=false network=false.
  • MumbleIsConnected() returns true, and the player is in its assigned channel (MumbleGetVoiceChannelFromServerId(me) == assignedChannel).
  • The client log shows the capture device being initialized:
    voip-mumble Returning device Microphone (Scarlett Solo USB) for GUID {F98B3C79-F884-4D8C-8E27-8CAA8CE8B808}
    voip-mumble MumbleAudioInput::InitializeAudioDevice: Initialized audio capture device.
    
  • Resetting the "Voice chat" settings tab did not change anything.
  • No script calls NetworkSetVoiceActive, MumbleSetActive or SetPlayerTalkingOverride.
  • Tested alone on the local server, so I could not check whether the voice itself is still transmitted, or only the talking state is broken.

Activity

  1. changed the title [-]NetworkIsPlayerTalking / MumbleIsPlayerTalking always false for the local player since the CEF 144 client update[/-] [+]NetworkIsPlayerTalking / MumbleIsPlayerTalking always false for the local player[/+] on Nov 4, 2026
  2. added
    triageNeeds a preliminary assessment to determine the urgency and required action
    on Nov 4, 2026
  3. yorick2002 commented on Nov 4, 2026

    @yorick2002
    Contributor

    You might be using SetPlayerName? #4303

  4. MXK7 commented on Nov 4, 2026

    @MXK7
    Author

    Yes, we do: we call SetPlayerName server-side on connect, to replace the FiveM name with the Discord name. So this looks like the same bug as #4303.

  5. yorick2002 commented on Nov 4, 2026

    @yorick2002
    Contributor

    4. Yes, we do: we call SetPlayerName server-side on connect, to replace the FiveM name with the Discord name. So this looks like the same bug as #4303.

    Remove it for now, the PR should get merged soon as far as i've heard

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    triageNeeds a preliminary assessment to determine the urgency and required action

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions