[Bug] Keyboard inputs aren't interpreted after joining a server

[Palente]

Summary

When joining an empty server or the FiveM test server, there is roughly an 80% chance that my keyboard inputs are no longer detected after joining.

When the issue occurs:

I cannot move my character.
I cannot open any menus, including the pause menu.
F8 still works normally.
Left click and right click also seem unaffected and work as expected.

The inputs themselves seem to still be detected by FiveM. If I open F8 > Game > Input Viewer, the Input Viewer correctly shows my keyboard inputs, even though they are not interpreted by the game.

Issue type

Client

Repro rate

Often

Server build version

b111

OS

Windows 11 25H2

CPU

AMD Ryzen 7 5700G

GPU

AMD Radeon RX 6650XT

RAM

32Gb DDR4

Storage type

SSD SATA

Connection type

WiFi

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

None

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

None

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Join FiveM server
2. Try to move or to open menu

Expected Behavior

You should be able to move or open the pause menu

Actual Behavior

Nothing happens

Evidence

Video 1

In this video, I cannot move or use keyboard controls, while the Input Viewer clearly shows that my inputs are being detected:

https://streamable.com/nlvf8o

Video 2

In this video, I am able to move while the txAdmin interface is open:

https://streamable.com/5nhj75

When i exit the txadmin menu, my keyboards aren't interpreted anymore

i recorded with window's capture tool, didn't know it would looks that bad

Additional Context

No response

[mevlut36]

I have the same issue

[Narzuls]

+1 same issue

[xKnck]

+1 same issue

[wolfram-cfx]

Thanks, we are looking into this.

[KevinOB22]

After some trial and error on users affected by this issue on my server, I found that if I ran "ShutdownLoadingScreenNui()" on their client, it fully resolved their issue for the session. I put a temp fix in on our end to prevent it from happening.

[Palente]

I tried Native.ShutdownLoadingScreenNui(); and it worked as you mentionned.

[Gogsi]

A fix for this bug has been implemented and is available in August 11 Patch. Please try again and let us know if the issue persists. Thanks for your help!