Argh
I installed and updated EQ2Map version 1.0.16. Same problem reoccurs. As far as I can find, there's no newer version or anything so I'm assuming it's a recent update/map(s) itself? If so, there's not a whole lot one can do except stop using EQ2Maps until the issue is resolved with a new update.
|