|
Hi
I'm korean user
(sorry for my english..)
since 2003 i used bwchart very useful
and when patch 1.18, bwchart 1.0x series didn't work
but then jca2 updated bwchart 2.00B, so used it very well
but blizzard patched 1.21, now bwchart doesn't work again
i sent pm to jca2 for request for remaking bwchart
but i don't know when jca2 would read it
can someone find out why doesn't bwchart work to 1.21?
bwchart 2.00B working 1.18~1.20.11's replays but 1.21's
if you need 1.20.11, 1.21 replays is here.
1.21's replay(doesn't work bwchart)
1.20.11's replay(bwchart work well)
and bwchart 2.00B's link is here Bwchart 2.00B
|
Hey, I wish BW Chart was still working, I'm not sure if it is still being used to be honest, ummm didn't DakotaFanning make it? not sure. I hope it gets updated soon, it's an awesome tool.
|
No jca made it. Dakota made the sc2 version I believe. We will just have to wait and see if he updates it.
|
i hope too but still not respond from jca2...
|
I check bwchart after almost all of my games, I hope it'll be patched soon
|
jca2
France51 Posts
Thanks for the replays. I have started looking into them and I will release a new bwchart as soon as I can. jca
|
On December 10 2017 00:16 jca2 wrote:Thanks for the replays. I have started looking into them and I will release a new bwchart as soon as I can. jca Thank you for your dedication to the StarCraft community!
|
thank you jca2
if you need other replays, i will upload it
|
jca2
France51 Posts
https://www.dropbox.com/s/9s14suslvn0wtbq/bwchart200C.exe?dl=0
Here you go. If you had previously added 1.21 replays to your database, you will have to rebuild it to see the correct engine version.
The work is still in progress as there are new actions in the replay. I need more time to understand what they are and learn how to decode them. For example, you will see the new "select121" action, that is nothing more than a usual select except that the unit IDs are stored on 4 bytes instead of 2. I assume the other new actions are also variants of existing ones. We'll see.
|
oh.. i can't believe it
i opened once some replay of 1.21
very thankful, and if there is something i can help i will help your work
for example, 0x61 thing is set rally i guess, not sure,
but thanks, anyway
|
i misunderstood for set rally is 0x61 attack, attack move, move(click M key of keyboard) patrol, gather, set rally, clear rally, repair, comsat scan, load, unload, lay mine, any other energy skill and nuke launch in 0x61 too
shift deselect in 0x65 shift select in 0x64 lost vision on selected unit in 'Deselect' Bunker's all unload in 'Unload all' One click unload from Bunker, Dropship in 0x62 Land in Build Cancel Research in 0x31 Cancel Upgrade in 0x33
|
My BWChart crashes as soon as I want to add my replay library Help?
|
On December 15 2017 20:30 chrisolo wrote:My BWChart crashes as soon as I want to add my replay library Help?
For me, I need to open BWChart a couple of times before it will tell me which replay is causing the crash.
So, try 1: opens 1/2 way, crashes Try 2: opens 1/2 way, says "replay #### is corrupt, please remove" Before clicking OK I just use the search function to find the ### and delete it Press ok afterwards, BWChart opens. Upon opening it will likely pop up with a list of corrupt replays that it wants to move to another folder. This notification never goes away for me, even if I've already said "yes move to another folder." For whatever reason there are replays that prevent BWChart from opening entirely (crash on startup) and replays that just cause the pop-up but otherwise let you open BWChart.
If there is more than one corrupt replay preventing BWChart from opening you have to do the above process for each one. So if you have 4 corrupt replays that need to be manually deleted, you will do the above, delete replay #1, then hit OK and BWChart will just crash again. Then you open it again, it crashes again. Then you open it again, it will say "replay #2 is corrupt, please delete it" etc.
|
Ye deleting all the replays that were corrupt by hand did actually help. Why doesn't have the programm a feature to auto delete (or auto move them into a "corrupt replays" directory) them though? I deleted one and still encountered the "same" mistake (didnt really take a look on the replay name since the autosave naming of replays is quite bad in SC:R) but it was just another replay that was corrupt. After deleting them all one by one it works normally. Thank you very much Chrysanthemum.
|
Just curious, is APM broken in this version? Or is apm broken inside of starcraft? I just played a game, bwchart said my apm was 165 my opponent was 266, after the game though it says my apm is 193, opponent is 275. SC seems to be counting some actions bwchart does not.
|
On December 16 2017 06:20 jimminy_kriket wrote: Just curious, is APM broken in this version? Or is apm broken inside of starcraft? I just played a game, bwchart said my apm was 165 my opponent was 266, after the game though it says my apm is 193, opponent is 275. SC seems to be counting some actions bwchart does not. I believe classic bwchart doesn't count the camera hotkeys. Don't know if it is updated in the latest versions.
|
That was the first thing that came to mind, i do use the camera keys quite a bit.
|
bwchart 2.00c reads improperly some action. so it is not perfect version yet jca2 is in the process of fixing errors in bwchart.
|
and as far as i known, camera key(f2~f4) is can't count in any programs. it was
|
It seems to be more than camera hotkeys not being counted. I noticed some small discrepancies prior to the latest patch between blizzard's apm and bwchart's apm--from 10 to 40 apm generally. I average between 300 and 400 apm but most of my recent games bwchart is saying I'm at about 150 apm. I just played a game where I had 380 apm according to the blizz end-game counter, but 180 apm according to bwchart. What's curious is that my opponent also had 350 end-game counter apm, which bwchart came much closer to--323 apm.
Looking at the hotkeys recorded it seems that bwchart is counting my hotkey presses fairly accurately. It looks like maybe my mouse use is not being counted.
|
|
|
|