Closed GoogleCodeExporter closed 9 years ago
Only happens when running auto-menu on the clients that join a game.
Original comment by AHeinerm
on 8 Jul 2012 at 1:42
Original comment by AHeinerm
on 12 Jul 2012 at 6:43
Issue 439 has been merged into this issue.
Original comment by AHeinerm
on 12 Jul 2012 at 6:44
Another bug related to this:
When openning two instances one after another with a small (several seconds)
delay, the second client will show the message: "The scenario map file is still
being distributed".
The first client will crash shortly after that...
I guess this is because of the first client tries to start the game before the
map was fully "downloaded" in the "delayed" client...
Another workaround to this will be simply by adding a single button to
Chaoslauncher that will launch several clients at once.
Original comment by Leonid.T...@gmail.com
on 26 Oct 2012 at 10:31
Original comment by AHeinerm
on 7 Jan 2013 at 3:53
For the "The scenario map file is still being distributed" message, please see
http://code.google.com/p/bwapi/issues/detail?id=373#c19
The "Second client downloads maps it already has" problem is still happening
though.
Original comment by chris.c...@gmail.com
on 17 Aug 2013 at 8:28
Fixed the "Second client downloads maps it already has" in r4441.
The "auto-menu instability" part of this issue is still occurring in some
cases, e.g. crashes in some cases if you quickly open multiple multiplayer
instances of BWAPI and there are more of them than the wait_for_max_players
setting.
Another problem is that multiple games may be created (rather than having a
single BWAPI instance as the game host and the rest of the BWAPI instances
joining it), due to a race condition.
Original comment by chris.c...@gmail.com
on 23 Aug 2013 at 2:18
Original comment by AHeinerm
on 23 Aug 2013 at 6:27
The BWAPI project is slowly undergoing the migration to GitHub. All issues have
been migrated to the GitHub issue tracker located here:
https://github.com/bwapi/bwapi/issues
In order to receive updates on your issue, please head over to the GitHub issue
tracker and subscribe to your issue.
Original comment by AHeinerm
on 15 Apr 2014 at 7:46
Original issue reported on code.google.com by
AHeinerm
on 4 Jul 2012 at 3:21