Hi folks
I've plentiful experience in using the Terrain editor, but run into a problem I am unsure how to fix. I began work on a new map and set the starting Height Map to 50, which was way too high considering the height-limit for any water is 48. Now, in the toolbar at the top, I found the option to reset the Height Map to a more reasonable level, such as 8.
However, since this drops the map a significant 'distance', even though my cliffs and terrain is still fully intact - the camera seems to still believe the map is at a height of 50. Both in the Editor and in-game, even zoomed in as much as possible the camera is still about 30 height units above the ground. This makes any further work on the map almost impossible and actual in-game playing downright impossible.
How do I fix this so that the camera, both in the Editor and in-game, is aware that the Height Map is no longer 50?
Just going to ask too. I thought increasing the base Height Map (to 50 for example) meant the final dropoff cliffs would be much higher. As in, the cliff-falloff to the unpathable layer, when often used around the edges of maps. What does increasing the Height Map actually do? Raising or lowering a cliff level adjusts the height by +2 or -2 respectively, or -8 for the final 'edge' cliff, so I dont see what the point is.
Let me come straight to the point and tell you that there isn't really much of an easy fix for your problem save from starting your map from scratch. Luckily you should be able to copy over practically anything to a new map (data, triggers and even terrain) so the hassle won't be as big. That said, you might also want to take a look at post #6 in the FAQ; your issue is likely the same as the one mentioned before-last in that post.
As for what the Height Map does; I'm unsure about the specifics, but I believe it changes some integral map data used specifically for the things that are bugging out for you now; in-game placement markers, camera height, that kind of jazz. It's a function generally left untouched anyway: it is easier to simply manually adjust specific settings such as camera height depending on what your map needs rather than to adjust the height map itself and then proceeding to wiggle out the bugs. Usually it doesn't bug out if the numbers are somewhat reasonable (between -8 and 12 or such), but for all intents and purposes I'd advice against ever changing it if you don't know exactly what you're doing.
I should note here that with its incredible size and all the options the Galaxy Editor offers it is quite possible that all the fields adjusted by setting the height map can also be independently re-adjusted within the data editor. This would allow for a data editor-based fix of your issue without having to copy over all your things to a new map (you simply change the data fields back to their regular values and your issues should be gone), but since I'm not very familiar with the data editor and also have my doubts over whether the map changes made by altering the height map can actually all be found in the data editor my recommendation is still to simply start a new map and copy over the relevant stuff - it'll very likely be faster and easier to do. That said, if you do wish to pursue trying to fix your map through the data editor, try making a post on our data board.
StarCraft II: Annihilation Campaign - A 24 mission single-player campaign featuring unique heroes, custom tracks, boss battles, a varied set of mission scenarios and three intersecting storylines.
Hi folks I've plentiful experience in using the Terrain editor, but run into a problem I am unsure how to fix. I began work on a new map and set the starting Height Map to 50, which was way too high considering the height-limit for any water is 48. Now, in the toolbar at the top, I found the option to reset the Height Map to a more reasonable level, such as 8.
However, since this drops the map a significant 'distance', even though my cliffs and terrain is still fully intact - the camera seems to still believe the map is at a height of 50. Both in the Editor and in-game, even zoomed in as much as possible the camera is still about 30 height units above the ground. This makes any further work on the map almost impossible and actual in-game playing downright impossible.
How do I fix this so that the camera, both in the Editor and in-game, is aware that the Height Map is no longer 50?
Just going to ask too. I thought increasing the base Height Map (to 50 for example) meant the final dropoff cliffs would be much higher. As in, the cliff-falloff to the unpathable layer, when often used around the edges of maps. What does increasing the Height Map actually do? Raising or lowering a cliff level adjusts the height by +2 or -2 respectively, or -8 for the final 'edge' cliff, so I dont see what the point is.
Hey there Venrez,
Let me come straight to the point and tell you that there isn't really much of an easy fix for your problem save from starting your map from scratch. Luckily you should be able to copy over practically anything to a new map (data, triggers and even terrain) so the hassle won't be as big. That said, you might also want to take a look at post #6 in the FAQ; your issue is likely the same as the one mentioned before-last in that post.
As for what the Height Map does; I'm unsure about the specifics, but I believe it changes some integral map data used specifically for the things that are bugging out for you now; in-game placement markers, camera height, that kind of jazz. It's a function generally left untouched anyway: it is easier to simply manually adjust specific settings such as camera height depending on what your map needs rather than to adjust the height map itself and then proceeding to wiggle out the bugs. Usually it doesn't bug out if the numbers are somewhat reasonable (between -8 and 12 or such), but for all intents and purposes I'd advice against ever changing it if you don't know exactly what you're doing.
I should note here that with its incredible size and all the options the Galaxy Editor offers it is quite possible that all the fields adjusted by setting the height map can also be independently re-adjusted within the data editor. This would allow for a data editor-based fix of your issue without having to copy over all your things to a new map (you simply change the data fields back to their regular values and your issues should be gone), but since I'm not very familiar with the data editor and also have my doubts over whether the map changes made by altering the height map can actually all be found in the data editor my recommendation is still to simply start a new map and copy over the relevant stuff - it'll very likely be faster and easier to do. That said, if you do wish to pursue trying to fix your map through the data editor, try making a post on our data board.
Good luck with the issue either way!
<sub>,,</sub>
StarCraft II: Annihilation Campaign - A 24 mission single-player campaign featuring unique heroes, custom tracks, boss battles, a varied set of mission scenarios and three intersecting storylines.
Starcraft II: A War Story Campaign - A multi-act campaign with custom factions. Follow my discord for updates: https://discord.gg/Ztu44gZ
If you want to see a list of other awesome campaigns, go to: Custom Campaign Initiative