{"id":199002,"date":"2025-09-22T07:58:34","date_gmt":"2025-09-22T05:58:34","guid":{"rendered":"https:\/\/fivemx.com\/?p=199002"},"modified":"2026-07-20T12:36:33","modified_gmt":"2026-07-20T10:36:33","slug":"fivem-so-entfernen-sie-das-fadenkreuz","status":"publish","type":"post","link":"https:\/\/rpcrate.com\/de\/fivem-how-to-remove-the-crosshair\/","title":{"rendered":"Wie man das Fadenkreuz in FiveM entfernt (HideHudComponentThisFrame 14)"},"content":{"rendered":"

Fast answer:<\/strong> FiveM servers remove the default GTA crosshair \u2014 HUD component 14<\/code>, the reticle \u2014 by running HideHudComponentThisFrame(14)<\/code> every frame in a client script. The call must run on the client, inside a loop, because HUD components render again on the next frame. Below: the copy-paste resource, an optional player toggle command, and fixes for a crosshair that keeps coming back.<\/p>\n

The configuration and code examples here target FiveM for GTA V Legacy. Enhanced has different runtime and compatibility rules; check Cfx.re\u2019s Legacy-to-Enhanced changes<\/a> before applying them to an Enhanced server.<\/p>\n

Copyable client script<\/h2>\n

Create a small client resource and put this in client.lua<\/code>:<\/p>\n

CreateThread(function()\n while true do\n Wait(0)\n HideHudComponentThisFrame(14)\n end\nend)<\/code><\/pre>\n
The official Cfx.re native reference lists HideHudComponentThisFrame<\/a> as the native for hiding HUD components. Component 14<\/code> is the reticle\/crosshair.<\/p>\n
Minimal fxmanifest.lua<\/h2>\n
Place this next to client.lua<\/code> in a resource folder, for example resources\/[local]\/no-crosshair\/<\/code>:<\/p>\n
fx_version 'cerulean'\ngame 'gta5'\n\nclient_script 'client.lua'<\/code><\/pre>\n
Then add the resource to server.cfg<\/code>:<\/p>\n
ensure no-crosshair<\/code><\/pre>\n
Why it has to run every frame<\/h2>\n
HUD hiding is frame based. Calling the native once can look like it worked for a moment, but the reticle returns because GTA renders HUD components again on later frames. Keep the loop lightweight and do not add expensive logic inside it.<\/p>\n
Player-side vs server-side crosshair removal<\/h2>\n
\n\n\n\n\n\n\n\n\n
Goal<\/th>\nBest method<\/th>\n<\/tr>\n<\/thead>\n
Remove the default GTA reticle for everyone<\/td>\nUse a small client resource with HideHudComponentThisFrame(14)<\/code>.<\/td>\n<\/tr>\n
Let players choose<\/td>\nAdd a client setting or command that toggles the loop.<\/td>\n<\/tr>\n
Remove a custom weapon HUD<\/td>\nCheck the weapon\/HUD resource. It may draw its own crosshair.<\/td>\n<\/tr>\n
Stop monitors or overlays adding a dot<\/td>\nCheck client overlays, monitor features, and graphics mods.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
Optional toggle command<\/h2>\n
For a player toggle, replace the first client.lua example with this entire version. Do not run both loops:<\/p>\n
local crosshairHidden = true\n\nRegisterCommand('crosshair', function()\n crosshairHidden = not crosshairHidden\n print(crosshairHidden and 'Crosshair hidden' or 'Crosshair visible')\nend, false)\n\nCreateThread(function()\n while true do\n Wait(0)\n if crosshairHidden then\n HideHudComponentThisFrame(14)\n end\n end\nend)<\/code><\/pre>\n
Troubleshooting<\/h2>\n