Troubleshooting
Common Issues
Menu doesn't open
Possible causes:
- Keybind conflict with another script
- Resource didn't start properly
- NUI focus is stuck from another resource
Fix:
- Try the command instead of the keybind:
/fpsmenu
- Check if the resource is running:
/restart f5_boost
-
Look at the server console for errors on startup. You should see the MySQL bridge message. If not, the resource didn't start correctly.
-
Check for keybind conflicts. Open FiveM Settings > Key Bindings > FiveM and look for "Open FPS Menu". Rebind it if needed.
Settings don't apply
Possible causes:
- Another resource is overriding the same natives every frame
- Settings haven't been activated yet (first-time player with no KVP data)
Fix:
-
Change any setting in the menu. This activates the settings system and starts applying natives.
-
Check for conflicting resources. Any other optimization or density script that calls the same per-frame natives will override F5 Boost's values. Common conflicts: other FPS boost scripts, density multiplier scripts, or weather scripts that force rain levels.
Profiles not saving
Possible causes:
- No database resource running
- Database resource started after f5_boost
- MySQL connection issues
Fix:
- Check the server console for:
[f5_boost] MySQL bridge: oxmysql
[f5_boost] Profiles table ready
If you see No MySQL resource detected (oxmysql / mysql-async / ghmattimysql), make sure one of those database resources starts before f5_boost in your server.cfg.
- If you see the bridge message but not "Profiles table ready", there's a database connection issue. Check your MySQL credentials in the database resource config.
Share code shows "Invalid code"
Possible causes:
- Typo in the code
- Code from a different version with incompatible encoding
Fix:
Share codes have a built-in checksum. Even one wrong character makes the code invalid. Double-check the code and make sure it follows the format F5-XXX-XXX-XXX (letters and numbers, no lowercase).
The code input accepts pasted text with or without dashes. Spaces are also stripped automatically.
City lights stay off after disabling the feature
If you turned off Light Reflections and then stopped the resource, city lights remain off because SetArtificialLightsState is a one-time native.
Fix:
Start the resource again and enable Light Reflections, or restart the server.
Players see different FPS counter values than expected
The FPS counter measures actual rendered frames on the client, not server tick rate. Each player sees their own FPS based on their hardware. The counter is not synced between players.
Performance
Per-frame loop impact
The per-frame loop runs Wait(0) which means it executes every game tick. The natives called are lightweight (they're designed to be called per-frame by Rockstar). Actual overhead is negligible.
If settingsActive is false (player hasn't changed anything), the loop sleeps for 500ms instead.
Slow tick impact
The slow tick runs every 5 seconds. Cleanup natives like RemoveDecalsInRange and StopFireInRange have a small cost but are called infrequently. The 250m radius keeps the workload reasonable.
FPS counter loop
When disabled via config, the loop doesn't exist at all. When enabled, it adds one Wait(0) loop with an integer increment per frame. Negligible overhead.
Still Need Help?
- Join the F5 Studio Discord for community support
- Open a support ticket for direct assistance