SOLVED Infinite loading screen / shaders loading bug
|
edit: SOLVED, just deleting the config files of the game worked, here is the video on how to do it: https://www.youtube.com/watch?v=chP8qzfGTaY
(run the game with the config file deleted) Almost every time I try to load a new area the loading screen has no end. I tried everything I thought could work (I will list then below) and nothing helped, really need support. After some tries I was able to barely load the game but just the area my character was in the moment before this bug started, trying to load a new area or dying starts a new infinte loading screen and I said barely because most of the times the game "worked" enemys where either partially or completely invisible. Specs: CPU: I5-10400fr GPU: RX 7600 AMD RAM: 32GB BOARD: B560 DS3H AC-Y1 WINDOWS 11 25H2 I tried to solve my problem by: Changing the Steam shader pre-loading settings, deleting the shader cache in the game folder (%appdata%path of exile 2), optimizing the game for a Windows 8/7 system, running the game as administrator, removing fullscreen optimizations, reducing the game's graphics quality (in all aspects) and the number of audio channels, enabling ReBar in the BIOS, enabling and disabling dynamic culling and multi-threading, verifying the integrity of the game files multiple times, uninstalling and reinstalling the game, reverting Windows updates to previous versions and reinstalling the current ones, undervolting the GPU, changing the video card drivers, adjusting the number of active CPU cores dedicated to the game, enabling and disabling XMP, and enabling and disabling secure boot. I feel like it's a problem related to the game's shader loading taking too long. When I reset the shaders, the game manages to load the area I'm in, and I can play. I played the game for 1300h and this is the first time I have this problem. Última edição por Moranguinha#2898 em 16 de nov. de 2025 22:48:32 Último bump em 16 de nov. de 2025 20:54:03
|
|
|
Forgot to mention that I also tried changing from Vulkan to DX12 and DX11, and also tried changing the type frame generation.
|
|








