FiveM for GTAV Enhanced: Early Access Hotfix 4

Hotfix 4 for FiveM for GTAV Enhanced is now live — and it's the biggest one yet. Thanks to a steady stream of reports on the GitHub Discussions page, this patch brings the longest fix list so far, including a large batch of native fixes and several client and server crash fixes.

Below is the full breakdown of everything fixed in this patch.

Rendering & Visual Fixes

• DUI rendering is no longer flipped 180 degrees (#115). Any resources using DUI (Dynamic User Interface) elements will now display the correct orientation.
• SetRuntimeTextureImage loads base64 data URL images again (#87), following up on the runtime texture fix from Hotfix 2.
• The Rockstar Games button in the pause menu no longer crashes the game (#81) — a welcome fix for anyone who accidentally clicked it.
• Fixed a crash when loading images through nui-img (#153).

Vehicle & Ped Natives

• The SetVehicleHandling* natives no longer skip certain handling fields (#175). Vehicle handling customization now works fully, allowing scripters to tune every aspect of vehicle performance.
• GetVehicleNumberPlateText no longer appends extra characters when called on the server (#205).
• NetworkIsPlayerTalking reports voice activity again instead of always returning false (#179), restoring voice chat indicators for the revamped VoIP system.
• The SetPedHairTint and SetPedHeadOverlayTint aliases are now available, following the color native fixes from the last patch (#67).
• GetEntityArchetypeName returns the archetype name again instead of an empty string (#130).

Scripting & Console Fixes

• GetConvar no longer crashes when called without a default value (#196).
• GetIsLoadingScreenActive reports the correct state again through the loading screen shutdown sequence (#211).
• LoadResourceFile returns an empty string again for an existing but empty file instead of nil (#79).
• Semicolon-separated command chains work again in the server console.
• Pressing unregistered buttons no longer spams the console with errors.

Resource & Server Stability

• Fixed start and ensure being mixed up, where one failing resource in a category stopped the rest from starting (#164). Resources in a startup batch will now start independently.
• Replicated global state bags are now available when resources start instead of arriving afterward, preventing race conditions.
• Key-value store reads now return recent writes while data is still being flushed to disk, improving consistency.
• Fixed replicated config vars failing to serialize when a value is empty (#203).

File System & Path Fixes

• Non-ASCII characters in file paths no longer cause an RPF cache file not found crash (#180). This fixes issues for servers with resource files containing Unicode characters in their paths.

Network & Proxy Fixes

• Fixed a handshake failure behind reverse proxies caused by overly strict source IP checks (#182). Servers operating behind reverse proxies (such as those using our DDoS protection) will now connect properly.

C# / .NET Runtime Fixes

This patch includes a substantial batch of fixes for the C# (.NET) scripting runtime:

• [FromSource] string player sources work with natives that expect a player source string again on the .NET runtime (#121).
• [FromSource] resolves to a player object again during the playerConnecting event on the .NET runtime (#68).
• GetActualScreenResolution works from C# resources again instead of returning "Failed to get result" (#123).
• Fixed a C# crash from "Collection was modified" while resetting native strings (#143).
• Native API calls from C# no longer fail with "Failed to get result" during GC or async tasks (#165).
• Sending a null event argument no longer throws an exception.

Crash Fixes

• Fixed a Node.js resource crash on stop.
• Fixed a crash from IsPedCollectionComponentVariationGen9Exclusive.
• Various additional server-side crash and stability fixes.

How to Update

As with previous hotfixes, this update is delivered automatically through the FiveM for GTAV Enhanced client. Restart your client to receive the update, and server operators should ensure their Cfx Server binaries are up to date.

The Cfx.re team continues to actively monitor the GitHub Discussions page during early access. If you encounter any remaining issues, reporting them there gives the team the best chance of addressing them quickly.