Alright so I went to change the boundary settings on my map from being inside the map to displaying the full map, and now when I go to test it the minimap isn't even displaying terrain anymore in game. WTF. Does anyone know how to fix this? I have no triggers doing anything with the mini-map or anything, this is the only thing I changed.
Is it like a bug with the editor or something? Because if worst comes to worse I guess I could just copy my terrain into a new map of the same size, and triggers, then work from that (I'm assuming this would probably fix it)
That's what it looks like right now. I fixed it to an extent by increasing the map size on each side, but it seems the islands on the left are still out of camera view ingame, and the width of the map is at 256 so I cannot do that again... I even set a trigger to set the camera bounds & playable map area to the 'entire map' preset. Does absolutely nothing. :(
It's like the boundaries function is calculating at a different value than it should be or something, and I have no idea as to why it would do that...
Just gonna toss this out there, but while editing the bounds of the map, there are 2 things you can change, camera bounds, and map bounds. Make sure your changing camera bounds.
As for the trigger controls, it can't expand, it can only limit an area.
Just gonna toss this out there, but while editing the bounds of the map, there are 2 things you can change, camera bounds, and map bounds. Make sure your changing camera bounds.
As for the trigger controls, it can't expand, it can only limit an area.
No... I was editing the camera bounds, I think I can differentiate between camera bounds and map size... This is still a super annoying issue :(
I've had the same problem. My mini-map terrain disappears when I add campaign dependency.
But I fixed it.
My map began during beta. Adding in the campaign dependency just wreaks havoc on an older beta map. When a map is using the campaign dependency, it cannot see any custom tilesets you made with the beta version (in the minimap of course).
The solution (be sure you make a back up in case something goes wrong) is to change the tileset of the terrain to a default version of Starcraft 2: Wings of Liberty. Once that is done, you should see the minimap terrain display again. And then, you should alter your tileset as you did before.
I've had the same problem. My mini-map terrain disappears when I add campaign dependency.
But I fixed it.
My map began during beta. Adding in the campaign dependency just wreaks havoc on an older beta map. When a map is using the campaign dependency, it cannot see any custom tilesets you made with the beta version (in the minimap of course).
The solution (be sure you make a back up in case something goes wrong) is to change the tileset of the terrain to a default version of Starcraft 2: Wings of Liberty. Once that is done, you should see the minimap terrain display again. And then, you should alter your tileset as you did before.
Yeah I figured this out earlier. My map was created after release tho. Setting the campaign dependency after you begin working on the map really does screw with some settings it seems.
So I had the same thing happen to me with my minimap and never did find anywhere that actually explained what had gone wrong.
Bottom Line: When a map is saved, the minimap is generated according to the map bounds. It doesn't always generate correctly, it seems. My fix was to set the camera AND map bounds to what screwed them up initially, save and test, then re-expand them to full size.
Here's the long story, as it may contain more useful information for others:
I was playing around with creating instances - areas that are not on the minimap and unviewable until a unit gets transported there, by trigger, and then that region is the ONLY thing on the minimap and you can't view anything else until you leave. I tried setting the camera bounds to what I wanted the default bounds to be, planning to use a trigger to get to the hidden portions of playable map area - this is impossible, however, as the overall camera bounds (set by going to Map -> Map Bounds) cannot be changed once in-game. Basically, this has to be done with a map initialization trigger. Alright, so I figured that out, no problem; I changed the overall camera bounds back to max and set up triggers to do all this for me. When I tested it, however, the minimap looked a little funny...all the terrain on the minimap had somehow shifted to the left and the units were placed in impossible areas (only according to the minimap, the actual placement was normal). When I ordered my unit to go to a location via the minimap, he'd go far to the left of where I ordered him. After about 5 hours of searching, experimenting, and pulling out what little hair I have, I finally fixed it. Turns out, when you change the camera bounds and save it, the minimap gets generated. Unfortunately, it doesn't always regenerate correctly when you change the camera bounds again. To fix it, I went to Map -> Map Bounds, made sure both boxes had a check in them, and shifted the camera and map bounds until the map bounds lined up exactly with where I had changed them to when it got screwed up. Saved it, tested it (minimap was fixed, in-game), then re-expanded the camera and map bounds to full size - saved and tested again and minimap was working again.
I finally got it (I had the same problem)! I made a new map and i simply transfer 3 files via the MPQEditor, MapInfo, Mapinfo.version and the Minimap.tga.
And for my terrain texture, I needed to reload it in the map info in the editor. If you have already do some terrain job, it's sure that it will be deleted (I don't have that problem because my terrain is randomly generated).
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Alright so I went to change the boundary settings on my map from being inside the map to displaying the full map, and now when I go to test it the minimap isn't even displaying terrain anymore in game. WTF. Does anyone know how to fix this? I have no triggers doing anything with the mini-map or anything, this is the only thing I changed.
Is it like a bug with the editor or something? Because if worst comes to worse I guess I could just copy my terrain into a new map of the same size, and triggers, then work from that (I'm assuming this would probably fix it)
-
View User Profile
-
View Posts
-
Send Message
ModeratorsTry going to the Console (Window > Console). Type "browse", and find "Minimap.tga". Export that and take a look at it, see if it looks correct.
http://i861.photobucket.com/albums/ab180/l3lackjax/Minimap.png
That's what it looks like right now. I fixed it to an extent by increasing the map size on each side, but it seems the islands on the left are still out of camera view ingame, and the width of the map is at 256 so I cannot do that again... I even set a trigger to set the camera bounds & playable map area to the 'entire map' preset. Does absolutely nothing. :(
It's like the boundaries function is calculating at a different value than it should be or something, and I have no idea as to why it would do that...
@ST4RKiLL3R: Go
Just gonna toss this out there, but while editing the bounds of the map, there are 2 things you can change, camera bounds, and map bounds. Make sure your changing camera bounds.
As for the trigger controls, it can't expand, it can only limit an area.
No... I was editing the camera bounds, I think I can differentiate between camera bounds and map size... This is still a super annoying issue :(
OH MY FUCK IT JUST HAPPENED AGAIN. This time when I added both of the campaign dependencies to my map. WTF.
I've had the same problem. My mini-map terrain disappears when I add campaign dependency.
But I fixed it.
My map began during beta. Adding in the campaign dependency just wreaks havoc on an older beta map. When a map is using the campaign dependency, it cannot see any custom tilesets you made with the beta version (in the minimap of course).
The solution (be sure you make a back up in case something goes wrong) is to change the tileset of the terrain to a default version of Starcraft 2: Wings of Liberty. Once that is done, you should see the minimap terrain display again. And then, you should alter your tileset as you did before.
This bug (or a similar one) can be caused when the minimap area is not a multiple of a certain number (I believe 8.)
Yeah I figured this out earlier. My map was created after release tho. Setting the campaign dependency after you begin working on the map really does screw with some settings it seems.
Necro!
So I had the same thing happen to me with my minimap and never did find anywhere that actually explained what had gone wrong.
Bottom Line: When a map is saved, the minimap is generated according to the map bounds. It doesn't always generate correctly, it seems. My fix was to set the camera AND map bounds to what screwed them up initially, save and test, then re-expand them to full size.
Here's the long story, as it may contain more useful information for others:
I was playing around with creating instances - areas that are not on the minimap and unviewable until a unit gets transported there, by trigger, and then that region is the ONLY thing on the minimap and you can't view anything else until you leave. I tried setting the camera bounds to what I wanted the default bounds to be, planning to use a trigger to get to the hidden portions of playable map area - this is impossible, however, as the overall camera bounds (set by going to Map -> Map Bounds) cannot be changed once in-game. Basically, this has to be done with a map initialization trigger. Alright, so I figured that out, no problem; I changed the overall camera bounds back to max and set up triggers to do all this for me. When I tested it, however, the minimap looked a little funny...all the terrain on the minimap had somehow shifted to the left and the units were placed in impossible areas (only according to the minimap, the actual placement was normal). When I ordered my unit to go to a location via the minimap, he'd go far to the left of where I ordered him. After about 5 hours of searching, experimenting, and pulling out what little hair I have, I finally fixed it. Turns out, when you change the camera bounds and save it, the minimap gets generated. Unfortunately, it doesn't always regenerate correctly when you change the camera bounds again. To fix it, I went to Map -> Map Bounds, made sure both boxes had a check in them, and shifted the camera and map bounds until the map bounds lined up exactly with where I had changed them to when it got screwed up. Saved it, tested it (minimap was fixed, in-game), then re-expanded the camera and map bounds to full size - saved and tested again and minimap was working again.
I finally got it (I had the same problem)! I made a new map and i simply transfer 3 files via the MPQEditor, MapInfo, Mapinfo.version and the Minimap.tga.
And for my terrain texture, I needed to reload it in the map info in the editor. If you have already do some terrain job, it's sure that it will be deleted (I don't have that problem because my terrain is randomly generated).