GetEntityArchetypeName (0x47B870F5) hard-crashes the client on FiveM Enhanced
#185
Closed
etrex2k4
started this conversation in
[BUG] FiveM for GTAV Enhanced
Replies: 2 comments
|
same on my sigh |
0 replies
|
Hi, this is fixed in the latest version and tracked in #130. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
GetEntityArchetypeName(0x47B870F5) hard-crashes the client on FiveM EnhancedEnvironment
FXServer-early-access b95 linux,gamename gta5enhanced, onesync enabled,txAdmin
9.0.0-beta-554ebc84FiveM for GTAV Enhanced(gen9), Windows 11, observed 2026-07-23GetEntityArchetypeName/GET_ENTITY_ARCHETYPE_NAME(0x47B870F5), a Cfx extension, client-sideThe same code path runs fine on Legacy.
What happens
Calling
GetEntityArchetypeName(entity)on certain world/map entities hard-crashes theclient with an access violation. It is not a Lua/JS error — a
pcall/try…catcharound the call does not catch it; the whole client goes down with
The application has crashed!.The crash is deterministic: every crash dump points at the exact same address inside
fivem-client.dll, and the entire captured call stack is insidefivem-client.dll(nogame-engine frames), i.e. it faults inside the native's own implementation, not in game
code we drove into.
Crash-dump analysis (two separate crashes, minidumps parsed locally):
0xC0000005(ACCESS_VIOLATION)fivem-client.dll+0x1FEFEBC— identical across dumpsfivem-client.dllReport codes (in case they can be resolved server-side):
4c1c74a2-5e8f-4a71-8697-13bdb22e1e05,6ed2115a-828a-4c5d-93ad-7604d164b46a.Secondary issue: no names even when it does not crash
On the entities where it does not crash,
GetEntityArchetypeNameon Enhanced returnsno usable name — either empty or the raw hash — where Legacy returns the real archetype
name (e.g.
prop_bench_01a). So even the non-crashing path is effectively broken: thein-game
display-style overlay that prints archetype names now prints only numbers.Steps to Reproduce
The native is called per frame on whatever world object the camera/cursor is over (a map
editor hover overlay, an object-name debug overlay, etc.). Panning across a loaded area
eventually hits an entity that faults. A minimal repro iterates the object pool:
In our case the offending entity reported model hash
681787797and returned an emptyarchetype name right before the client faulted on a subsequent object in the same sweep.
Expected Behavior
GetEntityArchetypeName(entity)returns the archetype name for a valid entity (or anempty string for an unknown one) without crashing — as on Legacy.
Actual Behavior
Access violation inside
fivem-client.dll, hard client crash, uncatchable from script.On non-crashing entities it returns no usable name.
Why it hurts
The native is the only script-side way to get an archetype/model name for an arbitrary
world entity that is not in a hand-maintained catalog (map editors, object browsers,
door/prop tooling all rely on it). On Enhanced it is both unusable (no names) and unsafe
(random hard crashes while just hovering the world), and because the crash is a native
access violation, defensive
pcall/try…catchcannot contain it — the only workaround isto stop calling the native on Enhanced entirely, which removes the feature.
What would fix it for us
GetEntityArchetypeNamebounds-check the entity/archetype and return an emptystring instead of faulting on Enhanced.
Issue type
Client
Repro rate
Always
Server build version
FXServer-early-access b95 linux
OS
No response
CPU
No response
GPU
No response
RAM
No response
Storage type
None
Connection type
None
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
The native is called per frame on whatever world object the camera/cursor is over (a map
editor hover overlay, an object-name debug overlay, etc.). Panning across a loaded area
eventually hits an entity that faults. A minimal repro iterates the object pool:
In our case the offending entity reported model hash
681787797and returned an emptyarchetype name right before the client faulted on a subsequent object in the same sweep.
Expected Behavior
GetEntityArchetypeName(entity)returns the archetype name for a valid entity (or anempty string for an unknown one) without crashing — as on Legacy.
Actual Behavior
Access violation inside
fivem-client.dll, hard client crash, uncatchable from script.On non-crashing entities it returns no usable name.
Evidence
No response
Additional Context
No response
All reactions