|
On January 03 2017 16:01 alexpnd wrote:
Sweet, thank you!
When is audio coming?
Can't say exactly. It's scheduled after adding protoss.
On January 03 2017 19:30 heluq wrote:
I dont know why after this upgrade, my replay is very lag :/
On January 04 2017 01:05 toriak wrote:Show nested quote +[B]On January 03 2017 19:30 heluq wrote:
I dont know why after this upgrade, my replay is very lag :/ For me lag started with previous update - units/buildings selection
Thanks you two for your feedback on bugs and functionality. Please keep it coming! 
We have made some changes to the JavaScript, such that it hopefully plays smoother again.
|
Wow! This looks interesting! Thank you!
|
Doesn't it sound weird that SB is "clearly not interested" ? If you combine both, you get an HD broodwar with all modern features for playing and watching so maybe im missing some point...
|
On January 04 2017 23:32 imp42 wrote:
We have made some changes to the JavaScript, such that it hopefully plays smoother again.
Definitely smoother now. Many thanks for your work.
|
On January 05 2017 03:13 Guojing12 wrote:
Doesn't it sound weird that SB is "clearly not interested" ? If you combine both, you get an HD broodwar with all modern features for playing and watching so maybe im missing some point...
Indeed, this could possibly even attract some new players to the scene but blizzard would propably send their lawyer army if it turned out successful.
|
Russian Federation3339 Posts
|
On January 05 2017 03:13 Guojing12 wrote:
Doesn't it sound weird that SB is "clearly not interested" ? If you combine both, you get an HD broodwar with all modern features for playing and watching so maybe im missing some point...
Yeah I'm actually disappointed about this. Maybe SB doesn't want the possibility of subtle differences in the game engine?
|
On January 05 2017 12:25 xboi209 wrote:Show nested quote +On January 05 2017 03:13 Guojing12 wrote:
Doesn't it sound weird that SB is "clearly not interested" ? If you combine both, you get an HD broodwar with all modern features for playing and watching so maybe im missing some point... Yeah I'm actually disappointed about this. Maybe SB doesn't want the possibility of subtle differences in the game engine?
All I can say is we're being completely ignored and don't know the reason. Personally I would like to let the matter rest for a while. At the same time I understand people will ask over and over about an integration. But I can only speculate and public speculation is hardly going to improve the situation, so I will refrain from doing so.
regarding the subtle differences in the game engine:
replays actually re-play the game by executing commands stored in the replay file in exactly the same way it was originally played. This is the reason why you can't move back or insta-jump forward in the original Brood War when watching a replay.
As a consequence of this mechanism replays will desync at the slightest difference between original BW and OpenBW.
Imagine for example if we didn't include the bug where units get stuck at a ramp. Then they would manage to get up the ramp and reach their originally intended target, leading to a very different game state and subsequently to a complete desync.
There are two advantages to this:
a) whether we should stay true to the original behavior is not a question, but a MUST
b) we can easily test the OpenBW engine by running replays in original BW and OpenBW simultaneously and compare the game state.
|
On January 05 2017 14:52 imp42 wrote:Show nested quote +On January 05 2017 12:25 xboi209 wrote:On January 05 2017 03:13 Guojing12 wrote:
Doesn't it sound weird that SB is "clearly not interested" ? If you combine both, you get an HD broodwar with all modern features for playing and watching so maybe im missing some point... Yeah I'm actually disappointed about this. Maybe SB doesn't want the possibility of subtle differences in the game engine? All I can say is we're being completely ignored and don't know the reason. Personally I would like to let the matter rest for a while. At the same time I understand people will ask over and over about an integration. But I can only speculate and public speculation is hardly going to improve the situation, so I will refrain from doing so. regarding the subtle differences in the game engine: replays actually re-play the game by executing commands stored in the replay file in exactly the same way it was originally played. This is the reason why you can't move back or insta-jump forward in the original Brood War when watching a replay. As a consequence of this mechanism replays will desync at the slightest difference between original BW and OpenBW. Imagine for example if we didn't include the bug where units get stuck at a ramp. Then they would manage to get up the ramp and reach their originally intended target, leading to a very different game state and subsequently to a complete desync. There are two advantages to this: a) whether we should stay true to the original behavior is not a question, but a MUST b) we can easily test the OpenBW engine by running replays in original BW and OpenBW simultaneously and compare the game state.
But how do you account for the super rare bugs? I recall someone was able to un-infest a command center one time, it's barely even documented or mentioned anywhere.
|
On January 05 2017 14:58 xboi209 wrote:Show nested quote +On January 05 2017 14:52 imp42 wrote:On January 05 2017 12:25 xboi209 wrote:On January 05 2017 03:13 Guojing12 wrote:
Doesn't it sound weird that SB is "clearly not interested" ? If you combine both, you get an HD broodwar with all modern features for playing and watching so maybe im missing some point... Yeah I'm actually disappointed about this. Maybe SB doesn't want the possibility of subtle differences in the game engine? All I can say is we're being completely ignored and don't know the reason. Personally I would like to let the matter rest for a while. At the same time I understand people will ask over and over about an integration. But I can only speculate and public speculation is hardly going to improve the situation, so I will refrain from doing so. regarding the subtle differences in the game engine: replays actually re-play the game by executing commands stored in the replay file in exactly the same way it was originally played. This is the reason why you can't move back or insta-jump forward in the original Brood War when watching a replay. As a consequence of this mechanism replays will desync at the slightest difference between original BW and OpenBW. Imagine for example if we didn't include the bug where units get stuck at a ramp. Then they would manage to get up the ramp and reach their originally intended target, leading to a very different game state and subsequently to a complete desync. There are two advantages to this: a) whether we should stay true to the original behavior is not a question, but a MUST b) we can easily test the OpenBW engine by running replays in original BW and OpenBW simultaneously and compare the game state. But how do you account for the super rare bugs? I recall someone was able to un-infest a command center one time, it's barely even documented or mentioned anywhere.
Of course there's always a chance that something is missed. It's software development after all. It comes with bugs. But thanks to bwreplays.com we have about 250'000 potential test cases 
tscmoo actually found that some gameplay bugs are introduced by corrupt maps. It seems like "protected" maps are just maps that have been corrupted in a way such that the game is still able to load them while the editor isn't. This is quite a hack and has potential side effects.
IIRC specifically one bug causing units to get stuck at a ramp occurs only in the upper half of a protected map. Theoretically this could lead to unintended unfair advantage for a player spawning at the top.
|
Do you have an automated setup where you (a computer) are constantly running replays and checking for problems / desync issues?
|
On January 05 2017 14:58 xboi209 wrote:
But how do you account for the super rare bugs? I recall someone was able to un-infest a command center one time, it's barely even documented or mentioned anywhere.
That's the kind of bug that I'd imagine most people wouldn't be against fixing since it's not something that affects the gameplay anymore if it's super rarely encountered and not reliably reproducible.
|
On January 05 2017 19:09 BossPurple wrote:
Do you have an automated setup where you (a computer) are constantly running replays and checking for problems / desync issues?
Not yet, but IMO that would be the correct setup for integration tests. Possibly in conjunction with a nightly build or weekly build. I would like to get this done once we have a "version 1.0" including Protoss.
On January 05 2017 20:12 nighcol wrote:Show nested quote +On January 05 2017 14:58 xboi209 wrote:
But how do you account for the super rare bugs? I recall someone was able to un-infest a command center one time, it's barely even documented or mentioned anywhere. That's the kind of bug that I'd imagine most people wouldn't be against fixing since it's not something that affects the gameplay anymore if it's super rarely encountered and not reliably reproducible.
Once we fix even one single tiny bug we need an elaborated versioning system in place. Personally I'm not against bug-fixing. We should just be very cautious about it and make sure users are able to choose their preferred version. Sometimes the line between "bug" and "feature" is blurry.
|
Are there any videos available from openbw testing?
|
On January 07 2017 01:55 Piste wrote:
Are there any videos available from openbw testing?
We don't have any videos, no. What exactly did you have in mind?
And: if anyone wants to cast a game using OpenBW or do a short introduction of how to use the controls we'd be happy to upload the video to our youtube channel.
Edit: thanks Xloctis for contributing a Short OpenBW Replay Viewer Tutorial
|
ANNOUNCEMENTS
Protoss arrived
You can now watch 1v1 melee games of all three races, brought to you by tscmoo.
http://www.openbw.com/protoss-too/
quuad takes BW HD lead
quuad is taking over the lead for the BW HD module. We are very excited to have quuad in charge of BW HD. Not only is he immensely talented, but he also brought his own supply:
+ Show Spoiler +
Social Media
We're now present on Twitter, Youtube, Reddit.
Of course you can always visit our forum to discuss anything related to OpenBW.
|
Awesome news about Protoss.
But I just went to openbw.com to do a TvP replay and got a 500 error. What's up with that?
Cheers
|
May I suggest that instead of creating an entirely new subreddit, merge with /r/broodwar?
|
On January 10 2017 12:30 prOxi.swAMi wrote:
Awesome news about Protoss.
But I just went to openbw.com to do a TvP replay and got a 500 error. What's up with that?
Cheers
Sorry, you caught me in the middle of an update. It normally goes unnoticed, but this time I messed up a dependency.
On January 10 2017 12:33 xboi209 wrote:
May I suggest that instead of creating an entirely new subreddit, merge with /r/broodwar?
I just posted a simple link to the replay viewer in /r/broodwar and it got downvoted immediately. I figured it's better if other people post about OpenBW in /r/broodwar if they're interested, so I deleted the link again. Anyways, now the mod linked our tweet instead.
|
On January 10 2017 13:02 imp42 wrote:Show nested quote +On January 10 2017 12:33 xboi209 wrote:
May I suggest that instead of creating an entirely new subreddit, merge with /r/broodwar? I just posted a simple link to the replay viewer in /r/broodwar and it got downvoted immediately. I figured it's better if other people post about OpenBW in /r/broodwar if they're interested, so I deleted the link again. Anyways, now the mod linked our tweet instead.
I believe it has something to do with how Reddit works, I don't think anyone actually downvoted your post. Anyways, I am the mod at /r/broodwar :p
|
|
|
|
|
|
EPT![[image loading]](http://www.openbw.com/wp-content/uploads/2017/01/SupplyDepot_WIP.png)
