PoE2 Town FPS Fix — Stop Lag in Hideouts & Queues (0.5.0)

If your Path of Exile 2 runs smoothly in maps but drops to 20-40 FPS in town or your hideout, you are not alone. Town FPS has been a persistent issue since Early Access launch, and the 0.5.0 update's player surge has made it worse — towns are more crowded than ever. The problem is not your GPU being too slow; it is specific game systems (MTX rendering, audio processing, and player count handling) that scale poorly with large numbers of players in a single instance. Here is exactly how to fix it.

Fix #1: Hide Player MTX

This is the #1 cause of town FPS drops. PoE2 renders every cosmetic MTX effect for every player in your instance — wings, weapon effects, character effects, portal effects, pet MTX, and skill MTX from their equipped gems. In a full town instance with 20+ players, this can mean hundreds of additional particle and mesh draws per frame, each with transparency and overdraw costs.

• Go to Settings > UI > Hide Other Players' MTX Effects and set it to Enabled (or use /hideout_mtx off in chat).
• Alternatively, set show_party_mtx=false and show_other_player_mtx=false in production_Config.ini under the [DISPLAY] section.
• New in 0.5.0: There is also a "Hide MTX in Towns" checkbox under Game > Display. Enable it.

Players report 30-50% FPS recovery in towns after disabling MTX rendering. The effect is most dramatic in high-population instances like the League NPC area or hideout queues.

Fix #2: Reduce Sound Channels

PoE2's FMOD audio engine processes every sound source independently. In towns, every nearby player generates sounds: footsteps, ability effects, portal sounds, MTX ambient audio, and NPC dialogue. With 512 concurrent voice channels (the default), the audio mixer becomes a significant CPU bottleneck.

• Drop max_concurrent_voices to 64 in production_Config.ini for towns. This is aggressive but necessary for crowded areas.
• In the in-game Audio settings, set Channel Count to Low (64 channels).
• Reduce Ambience Volume to 20 or lower — ambient audio layers in towns consume CPU cycles with no gameplay benefit.
• Set Music Volume to 0 if you have not already.

Reducing sound channels from 512 to 64 can recover 5-15% CPU headroom in towns, which directly translates to higher FPS when your GPU is waiting on draw calls that are CPU-bound.

Fix #3: Disable Dynamic Culling

Dynamic Culling is designed to reduce rendering load by hiding distant or less important objects when FPS drops. However, the culling process itself introduces frame-time spikes because it recalculates visibility every frame. In towns where the culling system is constantly evaluating dozens of characters and their MTX, the overhead can actually reduce performance.

• Go to Settings > Graphics > Dynamic Culling > Off.
• Alternatively, set dynamic_culling=false in production_Config.ini under [RENDER].

Disabling dynamic culling paradoxically improves frame-time consistency because the rendering pipeline no longer spends CPU time deciding what to hide.

Fix #4: Instance Restart (The Nuclear Option)

Town instances accumulate memory fragmentation and script processing overhead the longer they are alive. If your town FPS has been getting progressively worse over a play session, the instance itself may be the problem:

• Press Ctrl + Left Click on the town waypoint and select "Create New Instance" to generate a fresh town.
• For hideouts, leave and re-enter your hideout, or right-click the hideout waypoint and select "Create New Instance."
• If you are in a queue for a league mechanic (like the Runes of Aldur NPC area), Ctrl + Click to enter a new instance with fewer players.

Instance restart is particularly effective after the 0.5.0 update because the new endgame systems create more objects per instance. A fresh instance can recover 20-40% FPS compared to one that has been running for hours.

Fix #5: General Graphics Settings for Towns

These settings help specifically in high-population areas without affecting your map performance (you can toggle them per-zone if you want):

• Global Illumination: Off. GI computes light bounce contributions from every player and MTX effect. In towns, this is wasted computation. Disable it.
• Shadow Quality: Low. Each player casts dynamic shadows. With 20 players, that is 20x shadow cascades. Low shadows reduce per-player shadow cost significantly.
• Water Detail: Low. Town water effects in areas like Lioneye's Watch or Bridge Encampment are expensive for their visual impact.
• Disable Depth of Field. Blur effects in the background are wasted GPU time in towns where you need maximum clarity to navigate your stash and NPCs.

0.5.0-Specific Town Performance Notes

The Return of the Ancients update added new NPCs, visual effects, and environmental details to town hubs. The Runes of Aldur league NPC in town generates additional particle effects that compound the MTX problem. Combined with higher player counts due to the update's popularity, towns in 0.5.0 are the most demanding they have ever been. GGG has acknowledged town performance as a known issue and is working on engine-level optimizations for a future patch, but the fixes above are your best options right now. For extreme cases, consider using /hideout and doing all your trading and crafting there instead of in town instances.

For more performance fixes, see our 0.5.0 Performance Guide or use the Config Generator for a full production_Config.ini.