The scale is working fine for me. It was only broken in one alpha and fixed shortly after.
For the MiniMap, well Mapster doesnt do anything with it, go look somewhere else :)
FYI, there are some changes in the 3.3.3 patch that require changes to Mapster to work right. I just patched it up (though not sure what I did is right) on the PTR, so if 3.3.3 goes live tomorrow, I will test it further, and update here (and open a ticket)..
Blizzard does the coloring itself now on the mainmap, as a consequence the feature was removed from Mapster, as the battle map is just "spill over" from the main map feature.
What, you mean like it's server-side? I'm pretty sure all the maps are on the client. Did you have the same problem and fix it that way?
I'm not 100% sure on this as I don't care enough for the feature one way or the other.
But I seem to recall that initial investigation on Beta showed that some textures are only cached locally after any of your toons has actually "discovered" the area.
You'll notice the streaming icon show up in that case.
So it's not exactly server side or client side.
Take this with a grain of salt, like I said I'm not 100% but I believe that's how it works.
I can't seem to get the fogclear to work on 4.0.3a. Any idea what's up?
Its not working out of the box right now because Mapster does not have the map data for the new maps in 4.0.3a. I'll be adding that as soon as the EU realms get back up.
Fogclear is still broken in 1.3.11-3-g83dc93b. The overlay shows, but the fog underneath is not cleared. I tested this on a new gnome character, and uncovering jigsaw pieces of the map did not make the rest of it appear.
Yes the overlay part works fine. But the fog is never cleared in the first place.
The way I remember it working before was that the fogclear module removed ALL the fog from the entire map, revealing it entirely, then the overlay sat on top of the fully cleared map, showing the player where they hadn't yet explored.
I have 2 screenshots. The first shows the map with the overlay set to 100% transparent. All the parchment colored areas should be fully uncovered, showing Ironforge, the lake to the east side of the zone, etc. The second shows it with the overlay set to 20% opaque. That pink mask should be covering a the map with no fog visible.
Edit: After creating a new profile, I think I understand how it works now. The fogclear opacity controls not just the fog overlay but the "clear" map portions themselves. Since I had it at low opacity, I couldn't see the map beneath it. The new profile with the color set to pure white and 100% opaque made that obvious. The trick is not to use the opacity function at all, and treat the darkness of the color as "opacity", since it only impacts the fogclear.
Someone already posted a ticket about this issue (ticket 74), just wanted to attach a couple pictures detailing the problem.
One shows the regular full sized map, note where the "track quest" check box is located. Another shows the (Mini) version, again note where the "track quest" check box is still located.
Thanks for the updates to Mapster to keep it current.
I'm getting this error now, since patch 4.1, that prevents placing the raid markers on the ground. This can be tested by going into a raid, pulling out the pop-out from the right of the screen, and trying to place a raid marker.
Date: 2011-04-28 21:14:12
Error occured in: AddOn: Mapster
Message: Error: AddOn Mapster attempted to call a forbidden function (PlaceRaidMarker()) from a tainted execution path.
Debug:
[C]: PlaceRaidMarker()
...mpactRaidFrames\Blizzard_CompactRaidFrameManager.lua:146: func()
..\FrameXML\UIDropDownMenu.lua:638: UIDropDownMenuButton_OnClick()
[string "*:OnClick"]:1:
[string "*:OnClick"]:1
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Using 1.3.2
Reinstalled this morning to verify, still happening.
For the MiniMap, well Mapster doesnt do anything with it, go look somewhere else :)
on 1.3.11
1.3.10 still does but it has a couple other issues
That's my understanding anyway.
thats the best feature about your addon
i use it in bgs all the time
also the combat coloring
and dead coloring
I'm not 100% sure on this as I don't care enough for the feature one way or the other.
But I seem to recall that initial investigation on Beta showed that some textures are only cached locally after any of your toons has actually "discovered" the area.
You'll notice the streaming icon show up in that case.
So it's not exactly server side or client side.
Take this with a grain of salt, like I said I'm not 100% but I believe that's how it works.
Its not working out of the box right now because Mapster does not have the map data for the new maps in 4.0.3a. I'll be adding that as soon as the EU realms get back up.
The way I remember it working before was that the fogclear module removed ALL the fog from the entire map, revealing it entirely, then the overlay sat on top of the fully cleared map, showing the player where they hadn't yet explored.
I have 2 screenshots. The first shows the map with the overlay set to 100% transparent. All the parchment colored areas should be fully uncovered, showing Ironforge, the lake to the east side of the zone, etc. The second shows it with the overlay set to 20% opaque. That pink mask should be covering a the map with no fog visible.
http://img121.imageshack.us/img121/9024/wowscrnshot112610204416.jpg
http://img220.imageshack.us/img220/4642/wowscrnshot112610204430.jpg
Edit: After creating a new profile, I think I understand how it works now. The fogclear opacity controls not just the fog overlay but the "clear" map portions themselves. Since I had it at low opacity, I couldn't see the map beneath it. The new profile with the color set to pure white and 100% opaque made that obvious. The trick is not to use the opacity function at all, and treat the darkness of the color as "opacity", since it only impacts the fogclear.
One shows the regular full sized map, note where the "track quest" check box is located. Another shows the (Mini) version, again note where the "track quest" check box is still located.
I'm getting this error now, since patch 4.1, that prevents placing the raid markers on the ground. This can be tested by going into a raid, pulling out the pop-out from the right of the screen, and trying to place a raid marker.