Sliding Doors and Gates not opening unless force applied to them first

For a good bug report you should probably include:

  1. Client (production/canary) and FXServer version: Production, Release 8036
  2. What you expected to happen: The sliding doors and gates to open as I walk up to them
  3. What actually happens: When trying to use sliding doors and gates on servers I play on (Both custom added and base game) I have to drive a car into the gate first or run into them for them to open when originally they opened up as I approached them when I reached a certain distance
  4. Category of bug (eg. client, server, weapons, peds, native): Client/Server
  5. Reproducible steps, preferably with example script(s): Using doors or gates that slide open and closed

This sounds like an asset issue where the maker didn’t properly setup the gates to activate at an appropriate distance. You should contact the server owner or the resource author to adjust that accordingly.

Even the base game is a little finicky but It’s not really a bug based on this report.

I did specify that it occured on base game gates also, so I dont see how it can be related to an asset if its happening on gates from base game nowhere near custom added assets

Ok, provide location examples of where you are running into this issue so others can attempt to reproduce with exact steps.

This seems to be a bug with GTA, but minor enough that it was never addressed.

There exists a “fix” for it, I’m not sure if anyone else has tried another fix.

with that, do I have to add in gates through codewalker or will the script just sort everything as standard?






since asked to provide locations, here are some but it appears to be any with a sliding mechanic to it

You basically set locations within script, nothing to do with code Walker. As for the interior gates, likely issue with the mlo/doors themselves.

didn’t have the issues until recently so possibly came in a FiveM Server Version update is all I can think

Make sure you don’t have multiple door tuning files or gta5.meta files that conflict. Do a search for them in your map resources and compare them to each other

I can confirm I dont

did you find a fix for this?

any update?

So in our server, the fix itself was actually in the door locking system. You may need to tweak it even if the doors don’t have a lock on it. I had this exact issue until we fixed the door locks.

I dont have a door lock system

did you find a fix?

I have this exact issue and I found a reproducible workaround that might help narrow down the cause.

My setup:

  • GPU: NVIDIA RTX 5070 Ti (Blackwell)
    • Client: Production, build b3258
      • OS: Windows 11, latest NVIDIA drivers
    • Symptoms (identical to OP):
    • Automatic sliding doors, gates, elevator triggers and other proximity-activated world objects do not react to my player at all. This happens on every server I join (custom MLOs and base game objects alike). Other players on the same servers walk up to the same doors and they open normally - only my client is affected. Doors only open if I apply force (run/drive into them) or another player triggers them.
  • Workaround / key finding:
  • Enabling VSync in the FiveM graphics settings fixes it completely and instantly. With VSync ON, all automatic doors, gates and elevators trigger normally again. With VSync OFF, the problem returns. This is reproducible on my system, across multiple servers.

This suggests the proximity/trigger logic for these objects is sensitive to frame timing or very high uncapped framerates - which would also explain why this issue mostly hits people with very fast GPUs (RTX 50 series in my case) while the majority of players never see it.

Happy to provide logs, dxdiag or test canary builds if that helps debugging.

Nice to know that the issue was related to fps.
Will be fixed with: fix(gta-core-five): door auto-open framerate independent by DaniGP17 · Pull Request #4058 · citizenfx/fivem · GitHub