ScriptsAboutBlogToolsKnowledge BaseReviewsFAQBasketDocsSupport
Clientcrash

Invalid native call in resource (game fatally closing)

Also seen as: Invalid native call in resource game is fatally closing invalid native fxv2 oal native crash

What causes it

The client crashed because a resource invoked a native incorrectly — wrong argument types/counts, or an issue tied to the fxv2 OAL (optimized argument lists) experimental flag on certain builds. Frequently seen after enabling experimental flags or on mismatched client/artifact versions.

How to fix it

Fix the offending native call and avoid experimental OAL flags unless you know a resource needs them.

  1. Note which resource is named in the crash; disable it to confirm it's the culprit.
  2. Remove any use_experimental_fxv2_oal / OAL flags you set unless the resource explicitly requires them.
  3. Check the resource passes correct argument types to natives (a common cause is a nil or wrong-typed arg).
  4. Update to current recommended artifacts and a matching client build.
  5. If it's a third-party resource, report it to the author with the crash dump.

Related errors

Related guides

Still stuck? We can help.

Optimized, dual-framework scripts for QBCore and ESX from Viper Development — escrow protected, delivered instantly to your Cfx portal.