[Compatibility] Same project works correctly on Cfx (FXServer) but behaves differently on VMP

Hello everyone,

I’m experiencing a compatibility issue between Cfx (FiveM / FXServer) and VMP, and I would appreciate some clarification or guidance.


1. Problem Description

  • When running my project with Cfx (FXServer + FiveM client), everything works as expected.

  • When running the same project with VMP server + VMP client, I can connect to the server successfully, there are no critical crashes, but in-game functionality behaves differently.

So the issue is not related to startup errors or logs, but rather runtime behavior and gameplay features.


2. Observed Behavior

On VMP:

  • Some features or systems do not work or behave differently

  • Certain UI / gameplay logic / interactions are missing or inconsistent

  • Resources appear to load, but do not function the same way as on Cfx

All of these features work correctly on Cfx.


3. Project Information

  • Project type: FiveM resources (fxmanifest.lua)

  • Scripting language: [Lua / JavaScript / C#]

  • Framework: [ESX / QBCore / Custom / None]

  • Dependencies (if any): [ox_lib, oxmysql, etc.]


4. Assumptions / Suspicions

I suspect this may be due to:

  • Incomplete compatibility with FXServer runtime

  • Differences in:

    • Resource system (fxmanifest.lua, lifecycle)

    • Event handling (RegisterNetEvent, TriggerClientEvent, exports)

    • GTA natives or entity synchronization

    • Asset streaming or networking behavior


5. Questions

  1. Is VMP intended to be fully compatible with FXServer / FiveM resources?

  2. Is there a list of unsupported or partially supported APIs / natives / features?

  3. For projects that work on Cfx but behave differently on VMP, what is the recommended approach to porting or debugging?


Thank you for your time and support.

Hello, good morning
VMP servers are inside Iran and people outside the country are facing a series of problems and you need to send documents so we can see your problem and send you a solution. Thank you for your patience and cooperation.

At the moment, we do not see any abnormal errors or logs being generated.
Since the issue happens without any visible errors, we are not certain about the cause, which makes it difficult for us to describe the problem clearly at this time.