Stuck on loading screen

For some unknown reason this issue has just started happening to me today.

Haven't done anything different between yesterday 03/27/2025 and today 03/28/2025. turned on my computer and booted up PoE 2 on steam. loaded up a T15 waystone and got stuck on the loading screen for the map.

Seen someone else talk about de-activating multi threading to fix the issue, attempted this and it solved nothing.

I've also attempted to load up and play through the separate PoE2 launcher and still run in to the same issue.

Extremely upsetting and confusing as i haven't touched or modified anything in my files and I'm now unable to play. Really really hoping this issue is resolved before the major update coming on the 4th of April.

My problem started the same. 28th started getting stuck on loading screen when trtying to run a map. Tried the vulkan/directx11 and still getting stuck. Removed multithreading and still getting stuck on the loading screen. Even deleted my config file and still nothing. I am not using steam to run the game, only thing i can think of now is to uninstall the game and reinstall see if that works.

Seems like this is only an issue when attempting to play solo.

When i was able to load in to my hideout, i joined a party with one of my friends and teleported to them in their hideout. No issues loading in and joining them.
They then loaded up some throwaway T13 maps to test if i would get stuck on the loading screen again but was able to join in and play no problem.

We continued to play through multiple T15 and T16 maps for over 5 hours and i never once experienced an issue when loading in to their maps or returning to their hideout.

Only once my friend logged off to go play another game, I attempted to run my own maps again as i felt it would be safe, i was greeted with the infinite loading screen once again.

I was having the same issue, however just as a side note, i am not having this in maps rather than in the campaign itself.

What i found useful is adding this to poe2 launch parameters.


--waitforpreload --noasync --garbagegeneration 1



I am not sure if this is what helped or something was done on the server\game side of it, but for now it is working properly on my side.