Environment questions
GTA V version: Latest: Just reinstalled GTA:V (1.0.2245.0)
Up to date: Yes
Legit or Pirate copy: Legit
Purchased where - Steam/Rockstar Launcher/Epic: Steam
Windows version: 10
Did you try to delete caches.xml (not cache/!) and try again? Yes
System specifications: 2070RTX, 32GB RAM, i9-9900k
CitizenFX crash zip file (‘Save information’ on a crash): N/A (Not crashing)
logs/CitizenFX_log files: (No crash to report)
.dmp files/report IDs: (No crash for .dmp files/report IDs)
If you can’t start the game at all
GTA V folder screenshot: Game starts, N/A
GTA V/update/x64/dlcpacks screenshot: Game starts, N/A
Filepath to FiveM folder: Game starts, N/A
FiveM client folder screenshot: Game starts, N/A
Which antivirus/firewall software are you using? Game starts, N/A
Did you try to disable/uninstall your Anti-virus? Game starts, N/A
Important parts
What is the issue you’re having?
Massive frame drops in the Los Santos area, as well as occasionally in the Paleto Area.
Normally gameplay will be smooth 60-70fps, however until the resolution steps below are followed, the frame drop intensifies to 1 frame every 4-5 seconds. Rendering the game unplayable.
What are you trying to do? Traverse the map.
What have you tried already to fix the issue?
Deleted caches.xml,
Cleared Client Cache,
Cleared Server Cache,
Restart Client,
Restart Server,
Uninstall/Reinstall FiveM
Uninstall/Reinstall GTA:V
Removed all resources from Dev server to ensure it wasn’t a resource that was added into the server. (Barebones artifact server only)
Deleted Dev server, and attempted with latest recommended artifact. (Github page)
Deleted Dev server again, and attempted with newest artifact. (Github page)
–Temporary resolution found, this is the message we have provided to our playerbase to fix the issue.
To fix the frame drop/frame stutter fix after the latest FiveM update:
The best practice is to clear your cache before following the below steps
1) Start FiveM, go to the gear icon (settings) in the top right, scroll down and select Canary , acknowledge the pop-up box, then hit F8 and type: quit
2) Start FiveM, go to the gear icon (settings) in the top right, scroll down and select Release , acknowledge the pop-up box, then hit F8 and type: quit .
3) Start game, then hit F8 and type: quit
4) Restart PC
5) Start game
6) Connect to the server! Issue resolved! \o/
IF YOU ARE STILL HAVING ISSUES AFTER FOLLOWING THOSE STEPS, REINSTALL FIVEM, AND THEN FOLLOW STEPS 1-6.
Error screenshot (if any):
What did you do to get this issue?
Joined the server and attempted to move in the city.
What server did you get this issue on?
Both my developer and live server. (AspireRP), and several pinned servers on the FiveM front page. (Using server browser).
Additional comments
I have not introduced anything new to either of my servers since before this problem began after the last few FiveM updates. (as of approximately 4-5 days ago). More info below about the timeframe.
I have now continued my dev work since we have discovered the resolution to the problem. However it is a multistep process that is only achievable by swapping to canary build and back to release, followed by restarting the users PC.
- This issue is affecting select users. (~30% of users)
- No changes have been made server-side to account for this issue.
- I have reverted my dev server down to base server artifact alone, with no scripts running other than what is required, and the issue persists.
- The resolution we’ve found comes from toggling to canary, restarting the client, back to release, restarting the client, and then restarting the users PC, to be able to play without issue.
4 of my communities 130 active people have had to reinstall FiveM itself and perform these troubleshooting procedures above to be able to play without their client dropping to 1 frame every 5-10 seconds.
This issue started happening on Canary build 4-5 days ago following a client update, and started affecting the release build yesterday morning following a client update.
The steps provided above have been a 100% resolution to the issue. This leads me to believe this is not a server issue, and leads me to believe the issue is with the game client itself.