archive by month
Skip to content

BWAPI 4.2.0 and CIG 2017

I heard back from the CIG 2017 organizers. They wrote that the contest will support BWAPI 4.2.0 “if there’s no special issue,” and that details will be announced later.

So: They haven’t decided for sure. I expect that there will be no issues and they’ll adopt it, but the decision is not set in stone.

In my experience, most academics are extremely busy, which is not ideal since good scholarship calls for time and concentration. I think the CIG organizers are no different.

Trackbacks

No Trackbacks

Comments

Ailien on :

As I said in my other comment. The problem for all Uab Derivates is the dependency on bwta. If someone has a clue what to do about it other than wait for an update, I'm basically done.

Jay Scott on :

I think it should work if you compile BWTA2 yourself with vs2017. It probably doesn’t need many changes for that? I hope?

Jay Scott on :

Another choice would be to follow UAlbertaBot (in the sparcraft_update branch) and remove BWTA as a dependency. Dave Churchill added a BaseLocation class to replace BWTA’s and updated the distance map stuff. It depends on what you’ve done, but to me it doesn’t look hard to retrofit.

Joseph Huang on :

BWTA2 is not easy to compile because of CGAL dependency which depends on a lot of other libraries.

Joseph Huang on :

I looked into it more, looks like Boost dependency is the only requirement, others are optional. However the license is GPL2.

krasi0 on :

Source?
I thought it is LGPL (https://bitbucket.org/auriarte/bwta2/src/4222ab0d9b5d49362e4893ffb5fbcdcbeff359ec/COPYING?at=master&fileviewer=file-view-default)

Joseph Huang on :

BWTA2 is in violation of the GPL.

CGAL 2D Segment Delaunay Graphs is licensed under GPL. http://doc.cgal.org/latest/Manual/packages.html

All BWTA2 bots and derivatives should be GPL licensed.

MicroDK on :

I finally found a solution to my latency related problem. Apparently BWAPI 4.1.2 occatinally reports a wrong amount of minerals which can be negative and much higher what you see in-game. This only occurs when using UDP or Local PC with latency frame 6 or higher (its 6 for me) and turning latcomp off makes it worse. The result is that UAB/SH based bots will start producing units from larvas and skip it since there are not enough minerals. You also hear/read the warning. My solution is to only call the ProductionManager::manageBuildOrderQueue() every latency frame. It is easily tested by setting speed to 420 (very slow). At game start the mineral count will go up to 50. This takes some frames, in my tests 3 frames. But BWAPI reports to have 50 in the first frame so the first unit will be set to be produced and then skipped.
If BWAPI 4.2.0 has better latency handling it could be worth to upgrade.

MicroDK on :

Forgot to mention that I can only detect this error when playing as Zerg...

krasi0 on :

That's very curious and really smells like a lat compensation bug...

Add Comment

E-Mail addresses will not be displayed and will only be used for E-Mail notifications.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA

Form options

Submitted comments will be subject to moderation before being displayed.