I am making a 256x256 map. As I added more and more doodads, units, triggers, etc, the drop in framerate during the initial 10 seconds became more severe, though it returned to normal afterward.
I have tried my best to switch off all the triggers that are not needed in the beginning. Any other ways to reduce this initial framerate drop? Thanks!
Starting lag exists on many maps, it's not very consistent either. Melee maps, the campaign, custom maps. They don't even have to be big, sometimes it lags. Power computer, or not. Maybe you could distract the players with something at the beginning if it's really bad.
Your best bet is to not putting the unit down, put the point /region reference and then use trigger to create them. Actually that's how blizz put more unit in brutal campaign (default unit on map is for normal i think)
I am making a 256x256 map. As I added more and more doodads, units, triggers, etc, the drop in framerate during the initial 10 seconds became more severe, though it returned to normal afterward.
I have tried my best to switch off all the triggers that are not needed in the beginning. Any other ways to reduce this initial framerate drop? Thanks!
Triggers don't impact much, if any, at all.
Starting lag exists on many maps, it's not very consistent either. Melee maps, the campaign, custom maps. They don't even have to be big, sometimes it lags. Power computer, or not. Maybe you could distract the players with something at the beginning if it's really bad.
Would it be useful if I uncheck the Initial Active box for units I don't needed at the beginning and use trigger to show them afterward?
Your best bet is to not putting the unit down, put the point /region reference and then use trigger to create them. Actually that's how blizz put more unit in brutal campaign (default unit on map is for normal i think)
Creating an intro of sorts ( Depending on if your map even needs one ) that has the terrain and such hidden for like ten seconds might help.
Thanks again