[Bug/Regression] ShutdownLoadingScreenNui() relocates the local ped to a default spawn point (~293, 180, 105) on GTAV Enhanced

[M0RG4N01]

Summary

On recent GTAV Enhanced client builds, calling ShutdownLoadingScreenNui() no longer just dismisses the loading screen — it
relocates the local player ped to a fixed engine default position
(~293.1, 180.5, 105.3, next to the Vinewood sign), overriding wherever the
script had placed the ped with SetEntityCoords.

Custom spawn / character-selection systems shut the loading screen down
after positioning the ped, so the ped is now yanked to this default spot
the instant the loading screen is dismissed. This did not happen on previous
client builds — the same natives dismissed the loading screen without moving
the ped. spawnmanager auto-spawn is disabled and was ruled out; removing the
ShutdownLoadingScreenNui() calls is what resolves it, isolating the behaviour to
these natives.

CLIENT VERSION: early-access/b97

Issue type

Client

Repro rate

Always

Server build version

FXServer-early-access b96 win32

OS

Windows 11 24H2 (build 26200)

CPU

Intel Core Ultra 9 285H

GPU

NVIDIA RTX 5070

RAM

32 GB LPDDR5

Storage type

SSD NVMe

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. Connect to a server. From any client script, place the local ped somewhere
   explicit: SetEntityCoords(PlayerPedId(), 527.8, 10.1, 91.2).
2. Call ShutdownLoadingScreenNui() — directly, or
   via any event that leads to it.
3. Read GetEntityCoords(PlayerPedId()) immediately after. (Ped was teleported to Vinewood Hills)

Expected Behavior

ShutdownLoadingScreenNui() dismiss the loading screen
only. The player ped stays exactly where the script positioned it.

Actual Behavior

The moment the function is called, the ped is teleported to a fixed
default world position (~293.1, 180.5, 105.3). It happens synchronously on the
native call, every time.

Evidence

Instrumented a command that fires our "close all UI" events one at a time,
printing ped coords after each. The ped is stationary until the step that
reaches ShutdownLoadingScreenNui(), then jumps in a single synchronous step:

after core_weapon -> (527.8, 10.1, 91.2)
after loadingScreenOff -> (293.1, 180.5, 105.3) <-- ShutdownLoadingScreenNui() ran here

The loading resource uses loadscreen_manual_shutdown "yes". No SetEntityCoords
runs in that path; spawnmanager auto-spawn is disabled (only fires on death /
forceRespawn). Deleting the ShutdownLoadingScreenNui() calls removes the teleport.

Additional Context

CLIENT VERSION: early-access/b97

Our workaround: consolidate to a single ShutdownLoadingScreenNui()/dismiss call, at the
point the ped is positioned, and never fire it again afterward. We removed the
redundant calls scattered across the default spawn path, spawnmanager, a
loading-screen event handler, and a spawn selector — each was re-triggering the
relocation. On prior builds these duplicate calls were harmless no-ops.

[wolfram-cfx]

Thanks, we are looking into this.

[Gogsi]

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