-
Notifications
You must be signed in to change notification settings - Fork 0
Performance‐Tips
McAffe13 edited this page Jul 23, 2026
·
1 revision
Get the most out of FPSFlow with these tuning recommendations.
- Quality: Use only if you have a powerful PC and want maximum visuals
- Balanced: Best for most players; good FPS with minimal visual compromise
- Performance: Ideal for mid-range PCs or busy servers
- Ultra Performance: For low-end systems or extreme entity counts
- Disable
occlusionCullingto avoid entities popping out behind walls - Keep
entityLODenabled but increasefarLODDistanceto 128 - Disable
nameplateCullingor setmaxDistanceto 64 - Enable
singleplayerOptif playing on local servers
- Keep all features enabled at default values
- Increase
particleOptimization.maxDistanceto 80 for better visuals - Enable
worldJoinOptimizerto smooth out chunk loading
- Increase
entityCulling.maxDistanceto 96 or higher - Disable
entityLODif you need all entities visible - Lower
particleOptimization.maxParticlesto 2048 if farm particles cause lag - Use
entityTypeOverridesto always render specific entities
- Increase
particleOptimization.maxParticlesto 8192 - Raise
midDistanceandmaxDistancefor particles - Enable
backgroundFps.enabledto reduce GPU load on static menus
- Enable
chunkRebuildBudget.enabledto limit chunk rebuilds per frame - Set
maxRebuildsPerFrameto 2 or 3 - Enable
gcPressure.enabledto hint GC during loading screens
- Increase
worldJoinOptimizer.gracePeriodTicksto 300 (15 seconds) - Enable
adaptiveViewDistance.enabledto dynamically reduce render distance
- Set all
maxDistancevalues to their minimums - Disable
occlusionCullingif async raycasts cause hitches - Enable
entityTickOptimizer.enabledto skip AI for distant entities - Use Performance or Ultra Performance profile
- Start with Balanced profile
- Adjust one setting at a time and measure FPS impact
- Use the in-game debug screen (F3) to monitor FPS and entity counts
- Save your tuned settings as a Custom profile
Press F3 to see:
- FPS: Current frame rate
- Entity Count: Total entities in range
- Chunk Count: Loaded chunks
- Memory: Heap usage
Check latest.log for FPSFlow initialization messages:
[FPSFlow] Module 'entity-culling' initialized
[FPSFlow] Module 'particle-optimizer' initialized
If modules fail to initialize, check for compatibility issues.
- Setting distances too low: You will notice pop-in. Start high and reduce gradually.
- Disabling all features: You lose the benefit of adaptive tuning. Keep the Adaptive Renderer enabled.
- Ignoring profiles: Custom profiles are powerful but can be inconsistent. Start with built-in profiles.
- Mixing Sodium settings: Sodium has its own culling and entity settings. Let FPSFlow manage entity culling; let Sodium manage chunk/block culling.
"entityCulling": { "maxDistance": 96 },
"entityLOD": { "farLODDistance": 128 },
"nameplateCulling": { "maxDistance": 48 },
"blockEntityCulling": { "maxDistance": 64 }"entityCulling": { "maxDistance": 64 },
"entityLOD": { "farLODDistance": 96 },
"nameplateCulling": { "maxDistance": 32 },
"blockEntityCulling": { "maxDistance": 48 }"entityCulling": { "maxDistance": 48, "occlusionCulling": false },
"entityLOD": { "farLODDistance": 64 },
"nameplateCulling": { "maxDistance": 16, "enabled": false },
"blockEntityCulling": { "maxDistance": 32 },
"particleOptimization": { "maxParticles": 2048, "maxDistance": 32 }If you cannot resolve your issue:
- Check the Features page
- Review the Configuration reference
- Search existing issues on GitHub
- Create a new issue with:
- Minecraft version and mod loader
- List of all installed mods
- FPSFlow config (
config/fpsflow.json) - Game log (
latest.log)