In-Game map / "Fog of War"

So, i have the same issue and i've been battling this since Beastiary. The story goes back after i got myself a new SSD and a freshly installed WIN10 Pro. My issue was so bad that even settings i changed were reset on a client relaunch and at one point, ALT-TABBING or changing my screen resolution reset my fog-of-war on the map.

Very frustrating when you come to town to sell stuff, and zone back in and forget where the hell youre going and basically need to follow the body trail. Anyhow, i tried a multitude of things which i will list below:

1) Ensuring STEAM wasnt being stupid, did multiple steam reinstalls & did a stand alone installation.
2) UAC manipulation, making sure i had ownership of all files. Also adding control of all files
to Everyone from drive C:
3) Compatibility modes, ensuring admin, trying WIN8 compatability.
4) Direct X 9, for some reason the client acts much differently with your folders in DX9 vs 11
5) Moving folders around, deleting folders, moving the client installation folder/root from
Program Filesx86 to Desktop or My Documents
6) Ensuring Anti-Virus wasnt a problem
7) Ensuring Firewalls werent getting in the way


It was not until i hit #7 is when i finally had some success here. Allowing the Client.exe, PathOfExile_64 and PathOfExile past the firewall (windows) allowed some of these folders to repopulate. They do not repopulate immediately on launch, but will start to pop up some minutes afterward. The Fog of war issue is gone, but the game always starts in Windowed Fullscreen, regardless of the setting i choose. Also, the Minimap folder stays devoid of any files, despite the issue being gone.

Basically, it comes down to a severe lack of understanding of how the minimap system in this game really works. It would be nice to have some freedom as far as where the game is targeting file locations or how it works. If we had the ability to ensure the program is looking in the right place, it would be easier to pin point whats going on here.

In case it helps anyone, I fixed this problem by checking the production_Config.ini file - in the section under [GENERAL], the cache_directory was on a drive that had since been removed.

Changing it to e.g. C:/PoECache/ fixed the problem for me. This might have been something I'd monkeyed around with, so maybe I deserved it~