Trying to figure out what I did wrong here. My map plays perfectly fine solo, but as soon as I hit it up in Battle.net with multiplay it has really bad stutter which affect movement/camera speed. The UI stays perfectly fine though.
Well, because if you enable Debug mode and switch to the Activity tab, you'll see that the game is generating a lot of Events (the Unit Enters Point events specifically) and that might be too much for Battle.net to handle.
While I agree that the activity does spike a little, but battle.net should handle that no problem. All it is it's my unit pathing from point to point. And the activity isn't showing in the beggining because there is not a wave , and it will still stuter.
@Bibendus:
I tried doing just a Melee load screen with Wait For Key, but as soon as I get in it says You've Been dropped... So I can't even test if that fixes it, seems like it just wont let me play...I'll do a couple more tests...this is really bothering me.
Despite everyone's suggestions (which certainly may help reduce the lag and likelihood of dropping) this issue is a battle.net issue that affects custom and ladder maps, for which there is no current fix. You should report what is happening on the battle.net bug report forum. Check the bug report forum for posts on dropping. There are at least 2 posts where blues have requested information about the dropping events so that they can find out what happened, and the reports are split about half and half with custom and ladder matches.
My map had this problem, and I tried the "wait for key" fix, and now the dropping happens to 1 player every 10th game instead of every player every game.
Hey guys,
Trying to figure out what I did wrong here. My map plays perfectly fine solo, but as soon as I hit it up in Battle.net with multiplay it has really bad stutter which affect movement/camera speed. The UI stays perfectly fine though.
If anyone can try it and maybe has seen this problem before, I've uploaded it publicly and unlocked through Battle.net, Hero Team Survival, or you can download here : http://www.sc2mapster.com/maps/enfos/files/22-hero-team-survival/
Any help would be greatly appreciated.
EDIT : Actually, if I play it solo over battle.net it also has horrible stutter. It only works fine when I play localy from the editor .
/cry
I didn't test your map but I think your problem is caued by the loading screen image that desyncs users from battle.net
You have 2 solutions to solve this:
1) Remove the custom loading screen
2) Check "wait for key" in the map loading screen options
So does your map lag at the beginning only or even while playing it?
@Klishu:
It lags while playing as well. I'll try to enable the Wait for Key see if that makes a difference.
Well, because if you enable Debug mode and switch to the Activity tab, you'll see that the game is generating a lot of Events (the Unit Enters Point events specifically) and that might be too much for Battle.net to handle.
@senatorsfc: Go
Guys its the loading screen problem, believe me.
I fixed my map in this way too...
@Klishu
While I agree that the activity does spike a little, but battle.net should handle that no problem. All it is it's my unit pathing from point to point. And the activity isn't showing in the beggining because there is not a wave , and it will still stuter.
@Bibendus:
I tried doing just a Melee load screen with Wait For Key, but as soon as I get in it says You've Been dropped... So I can't even test if that fixes it, seems like it just wont let me play...I'll do a couple more tests...this is really bothering me.
@senatorsfc: Go
Despite everyone's suggestions (which certainly may help reduce the lag and likelihood of dropping) this issue is a battle.net issue that affects custom and ladder maps, for which there is no current fix. You should report what is happening on the battle.net bug report forum. Check the bug report forum for posts on dropping. There are at least 2 posts where blues have requested information about the dropping events so that they can find out what happened, and the reports are split about half and half with custom and ladder matches.
My map had this problem, and I tried the "wait for key" fix, and now the dropping happens to 1 player every 10th game instead of every player every game.
Good luck, and remember to report.