The objective is to increase the Texture Streaming Pool and force a more efficient Async Loading priority, preventing the game from “hanging” while you cross map boundaries.
File Path & Access
File Path (Standard): %LOCALAPPDATA%\Hotta\Saved\Config\WindowsNoEditor\ File Path (Steam): %LOCALAPPDATA%\Hotta\Saved_Steam\Config\WindowsNoEditor\
Step-by-Step Instructions:
- Press
Win + R, paste the appropriate path above, and press Enter. - Locate
Engine.ini. (Crucial: Backup asEngine_Backup.inibefore editing). - Right-click and open with Notepad.
- Paste the technical block provided below at the very end of the file.
- Save and set the file to Read-only to prevent Hotta’s launcher from overwriting your tweaks.
Optimized “Map-Speed” Configuration Block
[SystemSettings]
r.GTSyncType=1
r.FinishCurrentFrame=0
r.Streaming.PoolSize=4096
r.Streaming.FullyLoadUsedTextures=1
r.Streaming.MaxNumTexturesToStreamPerFrame=10
r.Streaming.FramesForFullUpdate=1
r.Shaders.Optimize=1
[ConsoleVariables]
s.AsyncLoadingThreadEnabled=True
s.PriorityAsyncLoadingExtraTime=5.0
s.LevelStreamingActorsUpdateTimeLimit=5.0
s.IoDispatcherCacheSizeMB=1024
gc.TimeBetweenPurgingPendingKillObjects=60
Parameter Details & Technical Purpose
| Parameter | Recommended Value | Technical Purpose |
s.AsyncLoadingThreadEnabled | True | The Loading Fix. Moves map loading to a background CPU thread to prevent the “5-second freeze.” |
r.Streaming.PoolSize | 4096 | Sets the VRAM budget (4GB). Adjust this to 50% of your total VRAM for optimal texture stability. |
s.IoDispatcherCacheSizeMB | 1024 | Increases the I/O cache for asset streaming, critical for fast travel and high-speed mounts. |
gc.TimeBetweenPurging | 60 | Extends the time between Garbage Collection cycles, reducing the frequency of random “hiccups.” |
r.Streaming.FramesForFullUpdate | 1 | Forces the engine to check for texture updates every frame, reducing “blurry textures” after fast travel. |
Best Practices for 2026 ToF Map Performance
To ensure a smooth experience in the latest 2026 Warp Server expansions, follow these additional GameEngineer.net technical steps:
- DLSS Memory Leak Fix: ToF is known for a memory leak tied to older DLSS versions. In 2026, we recommend manually updating the
nvngx_dlss.dllin yourEngine\Plugins\Runtime\Nvidia\DLSS\Binaries\ThirdParty\Win64folder to the latest version available on TechPowerUp. - NVMe Speed Reliance: Map speed in ToF is directly bottlenecked by your storage. If the game is on a SATA SSD or HDD,
s.AsyncLoadingThreadEnabledwill help, but you will still see “Low Poly” models. An NVMe Gen 4 drive is highly recommended for the 4.0+ maps. - Particle Overload: Large-scale boss fights in the global map can tank FPS due to “Mimi electric effects” or similar high-particle attacks. If your FPS drops in combat, add
fx.MaxCPUParticlesPerEmitter=4to your[SystemSettings]to reduce visual clutter without losing gameplay clarity. - Disable Fullscreen Optimizations: Right-click the game executable > Properties > Compatibility > Disable Fullscreen Optimizations. This fixes the “Camera Judder” many players experience when moving the mouse quickly across the horizon.