fog of war in maps resets after visiting hideout - (pics)
|
When I return to a map after leaving to sell an item, the fog of war has returned on the entire map.
This is upon entering a map and unlocking the first checkpoint:  From there, return to hideout and re-enter the map. The checkpoint is still discovered, but the fog of war has returned:  This happened to me seemingly every map until a specific patch (.1d?) and it hasn't happened again until today after this happened: I was in a map and received a trade request. I invited the requestor, and after they accepted I went to my hideout and retrieved the item. The person seemingly ignored my trade request and eventually disconnected, so I went back to the map. The fog of war was gone. I ran around a little bit and that person came back. After returning to the hideout, successfully trading and going back into the map, the fog of war was gone again. I have since entered multiple maps (including the one pictured) and left again just to test and sure enough the fog of war always returns. FWIW, dying does not reset the fog of war for me. Only leaving and returning. Please do not ask me how I know this. :( qq EDIT for details: PS5 player. California region. Changing regions, restarting the client, and rebooting do not help. Last edited by splunty#9517 on Apr 15, 2025, 12:58:53 PM Last bumped on May 10, 2025, 2:01:43 PM
|
|
|
Has anyone found a fix for this yet?
I've seen other similar threads but no responses from mods Its gotten where I don't leave a map to sell anything for less than a divine because it's not worth retracing the whole map again. |
|
|
Enter map lost.
Before portal back to hideout:  After returning through the portal:  |
|
|
Possible workaround:
1) Exit to Character Selection 2) Log out 3) Kill the game (On PS5 "Close Game") 4) Start POE1 5) Log into a character on POE1 6) Spin in a circle and marvel at the old graphics 7) Log out of POE1 8) Restart POE2 This has worked twice now. Killing POE2 and running a different game did not help. No idea why this worked and it might just be false causation due to small sample size. |
|
|
The workaround above does work every time.
|
|
