Improving FPS
Improving FPS
Improving FPS means reducing lag and making CIT run more smoothly by changing CIT settings, MTA graphics settings, and unnecessary visual extras.
Overview
The main ways to improve FPS in CIT are:
- lower graphics-heavy settings
- keep draw distance lower
- disable visual extras you do not need
- avoid HD mods
- reduce sound load when FPS drops
- keep background apps closed
If you want a stable setup, it is better to aim for a steady FPS instead of chasing a very high uncapped number.
Quick setup
For a simple low-lag setup:
- open
/settings - go to the FPS section
- set a reasonable minimum and maximum FPS
- lower graphics and sound settings
- keep Max distance around
300 - disable heavy Shader Graphics you do not need
- keep weather and blur effects off
- open Sound Performance and disable sounds when FPS is low
- avoid HD mods
- close background apps
- update your drivers
CIT settings
FPS section
To change FPS settings:
- open
/settings - go to the FPS section
You can set your minimum and maximum FPS from:
10to144
If you want no cap, use:
FPS_LIMIT=0
Recommended FPS target
A very high FPS is not always better.
For MTA and GTA:SA, FPS above about 74 can cause gameplay and physics problems. A conservative limit around 40 to 60 is generally safer, and 74 is the highest safer ceiling mentioned in MTA documentation.
Race FPS limit
While you are inside a race, the maximum FPS is:
70
Graphics settings
Max distance
One of the biggest FPS settings is view distance.
A practical setup is:
- keep Max distance around
300
Lower draw distance usually helps performance because fewer distant objects need to be rendered.
Shader Graphics
Disable heavy shader effects you do not need.
- disable heavy Shader Graphics you do not need
FXAA Shader
FXAA Shader is the lighter anti-aliasing option in CIT.
Options are:
- Off
- Low
- Normal
- High (Sharp)
If you need more FPS, keep it on a lower setting or turn it off.
Weather and visual effects
The following visual settings can be turned off:
- Enable Speed Blur
- Enable Clouds
- Enable Heat Haze
- Enable Rain
Keeping these off can help reduce extra visual load.
Vivid Shader
Vivid Shader makes the game more colorful.
If you are trying to maximize FPS, keep unnecessary visual shaders disabled.
Sound settings
Sound Performance
If FPS drops, you can reduce sound load.
To do that:
- open
/settings - go to Sound Performance
- choose which sounds should be disabled when FPS is low
You can also mute or lower normal sound categories in /settings.
MTA Graphics settings
Useful areas to test are:
- draw distance
- FX quality
- anti-aliasing
- resolution
- advanced loading settings
If your FPS is low, lower these first before adding more visual effects back.
Draw Distance
MTA uses a draw distance slider in the Video tab, and official MTA documentation notes that this slider directly affects how far objects stay visible. Higher draw distance can increase rendering load.
Asynchronous Loading
MTA also supports Asynchronous Loading.
This can reduce the small pauses that happen when new models load for the first time, but models may appear slightly later. It is worth testing if your issue feels like stutter or loading hitches more than low raw FPS.
Mods and custom content
Avoid HD mods
If you want better FPS, avoid heavy HD mods.
- avoid HD mods
This is especially useful on lower-end PCs or when the server already loads many custom objects and effects.
Background programs and drivers
Outside the game, the KB recommends:
- update drivers
- lower GPU 3D settings
- close background apps
These steps can help if your game is stuttering even after lowering in-game settings.
Practical low-lag preset
A simple low-lag preset can look like this:
- set a stable FPS cap instead of running extremely high
- keep Max distance around
300 - set FXAA Shader to Off or Low
- disable Speed Blur
- disable Clouds
- disable Heat Haze
- disable Rain
- disable heavy shader graphics
- use Sound Performance to reduce sound load
- avoid HD mods
- close browser tabs, overlays, and background apps before launching the game
Commands
| Command | Use |
|---|---|
/settings
|
Open the CIT settings menu |
/fps_limit=0
|
Remove the FPS cap |
Notes
- Uncapping FPS is not always the best choice if it makes the game unstable.
- A stable FPS is usually better than a higher but inconsistent FPS.
- In races, the maximum FPS is capped at
70. - If your game feels like it freezes briefly when entering new areas, test lower draw distance and Asynchronous Loading.