TEXTURES NOT LOADING PoE 2 0.4
|
I'm using `--waitforpreload` as well, but it doesn't help with the textures; they're still gone. Sometimes right away, sometimes after 10 minutes of playing.
Tried Vulkan and DirectX 12 modes, the behaviour is the same. The only difference is that in DirectX 12 mode, the game loads around 3 times slower than with Vulkan. ``` OS: Ubuntu 25.10 x86_64 Host: XPS 17 9700 Kernel: Linux 6.17.0-7-generic DE: GNOME 49.0 WM: Mutter (Wayland) CPU: Intel(R) Core(TM) i7-10750H (12) @ 5.00 GHz GPU 1: NVIDIA GeForce GTX 1650 Ti Mobile [Discrete] Nvidia drivers: 580.95.05 GPU 2: Intel UHD Graphics @ 1.15 GHz [Integrated] Memory: 13.27 GiB / 30.59 GiB (43%) Battery (DELL 01RR3YM): 93% [AC Connected] Running with GE-Proton 10-25 gamemoderun %command% --nologo --waitforpreload ``` |
|
|
Same here with 1660ti. Seems like it's a vram issue but it's new because this never happened in earlier leagues. And it's way woprse in act3. Happens every 15-20 mins then have to restart.
|
|
|
same problem
|
|
" ![]() on vulkan MSI GE62VR 7RF Laptop 16gb RAM Intel i7-7700HQ @ 2.8 GHz GTX 1060M 3GB Windows 10 Nvidia driver 32.0.15.8180 Disk: 1TB HDD dxdiag:https://pastebin.com/9tHGp7qM Dernière édition par Eruoso#0266, le 14 déc. 2025 à 09:40:35
|
|
|
GGG please fix this before your staff gp to long holiday for Chriszmas and New year.
|
|
|
Same here in both d12 or Vulkan. This has come with 0.4 path! It wasnt in 0.3.
This issue is something that comes from poe1. It was there in that one before as well. I dont know maybe it could be related to AMD environment. RX AMD 6400 4gb. R5 1600af 16gb ram. |
|
|
same her
|
|
|
ROG ALLY X
AMD Ryzen™ Z1 Extreme Processor ("Zen4" architecture with 4nm process, 8-core /16-threads, 24MB total cache, up to 5.10 Ghz boost) AMD Radeon™ Graphics (AMD RDNA™ 3, 12 CUs, up to 2.7 GHz, up to 8.6 Teraflops) RAM : 12GB*2 LPDDR5 on board --- I have tried a ton of potential fixes and only found an impractical workaround that will hopefully work for all of you and gives GGG some ideas on the root cause. /!\ Works for DX12 only, I'll discuss Vulcan lower. FYI, I have not found a workaround/fix for Vulkan issues yet. Requires two screens /!\ 1 - Delete Documents\My Games\Path of Exile 2 folder (potentially not mandatory). In short, this will basically reset your settings (resolution, keybinds, volume, etc.) 2 - Open game and update to your desired parameters in graphics options menu (keep DX12 or it will break again) 3 - When you see this issue change screens to your second monitor, save changes. 4 - Change back to your primary monitor 5 - Whenever textures stop loading again, repeat steps 3. As you can clearly see, this is extremely impractical and can potentially get your char killed so proceed with caution if using this method outside of a town. --- I'd like to just quickly mention issues of Vulkan users here as this is not the main topic and I didn't find a workaround for it yet. In case you experience long (or even non-ending) loading screens, switch to DX12 if possible and use the above workaround. --- Finally, I'd like to say a huge THX for GGG team as with this workaround I can see that optimization work you did help a ton, whenever I have all textures loaded, FPS increase, fluidity and responsiveness is as clear as day. Have a good one! |
|
|
I didn't try this method, but it does make sense, as I said before, this looks like a refresh problem. u can mimic this method by changing some graphic configurations (nothing very specific) and pressing "agree" The new configuration does a "refresh", but when we change zones, for example, u will see the problem again.
|
|
|
Same problem. Have to restart the game all the time and problem comes very quickly, sometimes almost immediately, sometimes can play a zone or two the most before it happens. I play in windowed mode, as expected, i use the lowest possible settings and Vulkan because Vulkan has had best performance up to this point.
System: Ryzen 5 2600 16 GB RAM RX 570 (4GB) M.2 500GB win 11 Tried downgrading AMD Adrenaline to older version but that didn't have any noticeable effects. ![]() |
|
















