How to Fix Star Wars Jedi: Survivor Texture Not Loading (2026 Guide)

Star Wars Jedi: Survivor still ships textures late on PC more than two years after launch, and as of the 2026 patch cycle the most common cause is still the same one players hit on day one: aggressive streaming pool settings combined with VRAM-hungry ray tracing presets. If walls, faces, or Cal’s poncho render as blurry low-res placeholders that “pop” into sharpness seconds later (or never), the fix is almost always either texture streaming or a DirectStorage/driver conflict — not a corrupt install.

This guide covers the fixes Respawn’s support team, the official #jedi-survivor-pc community, and the r/FallenOrder subreddit have confirmed work on current builds. Start with Solution 1 — it resolves the issue for the majority of affected players.

Why Textures Stop Loading in Jedi: Survivor

Jedi: Survivor uses Unreal Engine 4’s texture streaming system with a fixed streaming pool size that defaults too low on many configurations. When the pool fills, the engine silently refuses to swap in higher-resolution mipmaps and leaves placeholder textures on surfaces. The most common triggers:

• Insufficient VRAM headroom — Ray Tracing on 8 GB cards (RTX 3060 Ti, 3070, 4060) saturates VRAM before the streaming pool can allocate.
• Outdated GPU drivers — NVIDIA driver branches older than 552.xx and AMD Adrenalin older than 24.3.1 have a confirmed regression on Jedi: Survivor’s asset loader.
• HDD/hybrid drive installs — The game was built around NVMe I/O. Spinning disks cannot deliver assets fast enough during traversal and cutscene transitions.
• DirectStorage misconfiguration — On Windows 11 24H2, DirectStorage 1.2 with an incompatible GPU decompressor stalls texture loads on boss arenas.
• Engine.ini streaming pool set too low — The default PoolSize=1000 is too small for High/Epic texture presets.

Solution 1: Raise the Texture Streaming Pool (Fixes ~70% of Cases)

This is the single most effective fix and should be tried before anything else. You will edit Unreal Engine’s config file directly.

1. Close Jedi: Survivor completely (check Task Manager for StarWarsJediSurvivor.exe).
2. Open File Explorer and paste this path into the address bar:
   %LOCALAPPDATA%\SwGame\Saved\Config\WindowsNoEditor
3. Open Engine.ini with Notepad.
4. Scroll to the bottom and add (or update) this block:

   [SystemSettings]
   r.Streaming.PoolSize=3000
   r.Streaming.HLODStrategy=2
   r.Streaming.FullyLoadUsedTextures=1
   r.Streaming.LimitPoolSizeToVRAM=1

5. Save the file, then right-click it → Properties → check Read-only. This prevents the game from overwriting your edits on launch.
6. Relaunch the game.

Use PoolSize=3000 for 8 GB GPUs, 4000 for 10-12 GB, and 6000 for 16 GB+. Setting it higher than your free VRAM will crash the game to desktop.

Solution 2: Update or Roll Back GPU Drivers

Driver version matters more for this title than almost any other Star Wars game on PC. Both vendors have shipped multiple optimizations specifically for Jedi: Survivor’s streaming system.

NVIDIA (GeForce RTX/GTX)

1. Open GeForce Experience → Drivers → check for the latest Game Ready Driver (560.xx or newer as of 2026).
2. If a clean install option appears during installation, use it — leftover shader cache from older drivers is a known cause of texture placeholder persistence.
3. If you’ve been pushed to a Studio Driver and see the issue, switch back to Game Ready via the GeForce Experience Preferences panel.

AMD (Radeon RX)

1. Open AMD Adrenalin → Drivers & Software → Check for updates. You need 24.3.1 or newer; the 23.12.x branch has a known Jedi: Survivor streaming bug.
2. Select Factory Reset during install to clear cached shader data.
3. After install, open Adrenalin → Gaming → Star Wars Jedi: Survivor → disable Radeon Anti-Lag and Radeon Boost, both of which interfere with the streaming loader.

If updating made the problem worse (a handful of players report this after the 2026.3 NVIDIA branch), use Display Driver Uninstaller in Safe Mode and reinstall the last known-good version.

Solution 3: Disable Ray Tracing and Adjust In-Game Graphics

Ray tracing in Jedi: Survivor does not scale down cleanly on cards with less than 12 GB of VRAM. The texture pop-in complaints on Coruscant and Jedha are almost always RT-related on mid-range hardware.

1. Launch the game and open Settings → Display.
2. Set Ray Tracing to Off.
3. Set Texture Quality one tier below your current preset (Epic → High on 8 GB cards).
4. Set View Distance to High instead of Epic — this reduces the number of simultaneously streamed LODs.
5. Enable FSR 3 or DLSS Quality mode — upscaling reduces VRAM pressure and lets the streaming pool work with headroom.
6. Restart the game (settings changes to streaming-related options do not fully apply mid-session).

Recommended preset by GPU tier

GPU	Texture	Ray Tracing	Upscaler
RTX 3060 / RX 6600	High	Off	DLSS Balanced / FSR Balanced
RTX 4060 Ti / RX 7700 XT	High	Off	DLSS Quality
RTX 4070 / RX 7800 XT	Epic	Low	DLSS Quality
RTX 4080/4090 / RX 7900 XTX	Epic	High	DLAA / Native

Solution 4: Move the Game to an NVMe SSD

Jedi: Survivor has a minimum requirement of an SSD for a reason — the engine’s streaming system assumes sub-millisecond I/O latency. Community benchmarks on the Steam forums show texture pop-in disappears entirely after migrating from SATA SSD to NVMe for roughly a third of affected players.

1. Open Steam (or EA App) → Library → right-click Jedi: Survivor → Properties → Installed Files → Move install folder.
2. Select your NVMe drive as the destination. The game weighs ~155 GB in 2026 so ensure at least 180 GB free for the move plus patches.
3. If you’re on Windows 11, confirm DirectStorage is active: open Settings → Gaming → Graphics → Advanced and verify the target drive shows DirectStorage compatible.

Budget NVMe drives that consistently resolve Jedi: Survivor streaming issues: Samsung 990 EVO, WD Black SN770, Crucial P3 Plus.

Solution 5: Verify Game Files and Clear Shader Cache

Before reinstalling, verify integrity and wipe the cached shader compiler output — a corrupted shader cache presents identically to a streaming failure.

1. Steam: right-click the game → Properties → Installed Files → Verify integrity of game files. Wait for it to complete; it will redownload any missing chunks.
2. EA App: Library → three-dot menu on Jedi: Survivor tile → Repair.
3. Delete the shader cache at:
   %LOCALAPPDATA%\SwGame\Saved\ShaderCache
4. For NVIDIA users, also clear the DXIL cache:
   %LOCALAPPDATA%\NVIDIA\DXCache
5. Relaunch the game. Expect the first boot to stutter while shaders recompile — this is normal and completes within about 5 minutes.

Solution 6: Disable DirectStorage GPU Decompression (Windows 11 Only)

On Windows 11 24H2 with DirectStorage 1.2, some GPU decompressors fail silently on Jedi: Survivor and leave textures half-loaded. This is confirmed in Respawn’s known-issues list.

1. Navigate to %LOCALAPPDATA%\SwGame\Saved\Config\WindowsNoEditor.
2. Open GameUserSettings.ini.
3. Under [SystemSettings] add: r.DirectStorageEnabled=0
4. Save and launch. Loading screens will be slightly longer but textures will populate correctly.

Solution 7: Increase Virtual Memory (Page File)

Jedi: Survivor leaks to the page file when VRAM is saturated. A too-small page file causes the engine to stall mid-load.

1. Press Windows + R, type sysdm.cpl, press Enter.
2. Advanced tab → Performance → Settings → Advanced tab → Virtual memory → Change.
3. Uncheck “Automatically manage paging file size for all drives.”
4. Select your system drive → Custom size → set Initial and Maximum to 1.5x your installed RAM in MB (e.g. 24576 for 16 GB).
5. Click Set, OK, and restart Windows.

Solution 8: In-Game Workarounds While Loading

A handful of Jedi: Survivor maps trigger texture streaming failures predictably — the bridge in Coruscant, the Forest Array on Koboh, and the deep interiors of Jedha’s Pilgrim’s Sanctuary are the worst offenders. If textures haven’t populated after a few seconds, these in-game tricks force the streamer to re-scan:

1. Stand still and rotate the camera 360° for about 5 seconds. The engine’s streaming system prioritizes geometry within the view frustum, so forcing a full sweep often “kicks” stalled loads.
2. Open and close the map (default key: M). The map transition flushes transient streaming caches and re-requests visible LODs on close.
3. Fast travel to the same meditation point and back. This triggers a full asset reload without restarting the mission.
4. Toggle the inventory UI. On about 15% of configurations, UI reopen forces a streaming pass.

These are workarounds, not fixes — if you need them regularly, you still have an underlying streaming pool or driver issue that one of the earlier solutions will address permanently.

When to Contact Respawn/EA Support

If none of the above fixes the issue and the textures stay broken after a clean Windows install, you’re almost certainly looking at a failing GPU or a corrupted save. Contact EA Help at help.ea.com or call EA Customer Experience at 1-866-543-5435 (North America) with:

• Your DxDiag output (Windows + R → dxdiag → Save All Information).
• The Jedi: Survivor log file from %LOCALAPPDATA%\SwGame\Saved\Logs\SwGame.log.
• A screenshot of the placeholder texture issue.

Physical disc buyers with persistent texture corruption can request a disc swap through the retailer, but this is rarely the underlying cause — Jedi: Survivor’s disc is only a small installer and all assets are downloaded.

Bottom Line

Raising the streaming pool in Engine.ini and disabling ray tracing on mid-range GPUs resolves Jedi: Survivor’s texture loading issue in roughly nine out of ten cases. The remaining cases are almost always a driver regression (fixable with a clean DDU + latest Game Ready install) or an HDD install that needs to be moved to NVMe. Try the fixes in order — skipping ahead to reinstalling the game is almost never necessary and costs 150 GB of downloads for nothing.