SCFusion - WoL, HotS & LotV Build Order Optimizer - Page 4

CwEyeGonE

Iceland14 Posts

November 12 2010 16:10 GMT

#61

I like some of the suggestions here, and I doubt not that you had some of them in mind yourself, but I have one suggestion, I think it would also be great to be able to see the resources available at the Time that the goal is achieved.

Anyways, this seems like a great program, keep up the good work

Lejving

Sweden82 Posts

November 12 2010 16:15 GMT

#62

This is very good, a whole lot faster then evolution chamber too :O

Obviously needs some addition but still very good

For example I would really like Gateways: 3, Robotics Facility: 1 and so on, but you probably already on your way to add that.

Thanks!

Wire

United States494 Posts

November 12 2010 16:23 GMT

#63

I worry that soon computers will just play SC2 and we will all be spectators

They are thinkingz much too fasters than we has can

Deleted User 101379

4849 Posts

November 12 2010 16:58 GMT

#64

I put in 10 High Templars and got a buffer overflow after letting it run for a while (Game Count 347 946 810, Evolution 62 955). I tried to debug it with visual studio, but since there are no debug symbols i couldn't get the exact position.

I wonder if i could code this in C# myself and how fast it would be (definatly faster than java from my experience with both languages), time to read into the theory.

Champi

1422 Posts

November 12 2010 17:08 GMT

#65

quite an articulate post, had to read it a few times to completely understand

pxds

Brazil72 Posts

November 12 2010 22:22 GMT

#66

what exactly does the save function does? i made a build yesterday, saved it into a xml file and today, when i went to see the build, the xml file had nothing in it.

CarbonTwelve

Australia525 Posts

November 12 2010 23:01 GMT

#67

On November 13 2010 00:17 Nolari wrote:
CarbonTwelve, I'm wondering, why do you store the events in a sorted linked list rather than in a heap?

A sorted linked list gives O(1)-time removal of the first event, but O(n)-time insertion of a new event and updating the time of an event. A heap would give O(log n) time for all three operations.

Have you found that removals are so much more frequent and n so small that the linked list is superior?

To be honest, I haven't thought about it much. I suspect that the events queue rarely gets long enough to suffer too much for O(n) insertion. My primary goal was to ensure there's no dynamic allocation, and a linked list with a memory pool is simplest for that. I might look into the internal structures a bit more once I've got the other key features sorted out.

On November 13 2010 01:58 Morfildur wrote:
I put in 10 High Templars and got a buffer overflow after letting it run for a while (Game Count 347 946 810, Evolution 62 955). I tried to debug it with visual studio, but since there are no debug symbols i couldn't get the exact position.

I suspect that's the crash I've found and fixed already. Will do an upload later today with a new version.

[/quote]I wonder if i could code this in C# myself and how fast it would be (definatly faster than java from my experience with both languages), time to read into the theory.[/QUOTE]

Obviously you're welcome to try, and it's always good having someone redesign something as you might find reasons for doing things in a different way that I can then incorporate into my code. Honestly though, I doubt you'll get anywhere near the speed that my app achieves, basically because of the lack of control over memory allocations in C# and garbage collection just getting in the way.

CarbonTwelve

Australia525 Posts

November 12 2010 23:02 GMT

#68

On November 13 2010 07:22 pxds wrote:
what exactly does the save function does? i made a build yesterday, saved it into a xml file and today, when i went to see the build, the xml file had nothing in it.

Yeah, nothing at all atm, sorry. The GUI was just tacked together at the last second before I uploaded that version, and it was created using the MFC wizard which added all those controls that I haven't implemented yet. I do plan to allow saving of queries & build orders though.

TyPsi5

United States204 Posts

November 12 2010 23:08 GMT

#69

<3 you for releasing the code

Ronald_McD

Canada807 Posts

November 12 2010 23:23 GMT

#70

Any plans of adding building count options instead of just units?
Like, if I want for example 4 stargates in a given amount of time

Polatrite

United States135 Posts

November 12 2010 23:47 GMT

#71

Here are some build orders created with this tool. Note that some of these build orders aren't really feasible because they do things like Gateway on 17, but nonetheless:

5:10 - 6 zealot, 2 stalker, 1 sentry, 16 probes
+ Show Spoiler +

6:08 - 8 zealot, 2 sentry, 1 void ray, 18 probes
+ Show Spoiler +

7:48 - 1 mothership, 12 zealots, 30 probes, 2 bases (3 minute expand)
+ Show Spoiler +

0.00: 50M 0G 0E 6/ 10S - Build Probe
17.00: 73M 0G 10E 7/ 10S - Build Probe
34.00: 107M 0G 19E 8/ 10S - Build Probe
41.63: 100M 0G 23E 9/ 10S - Build Pylon
51.65: 50M 0G 29E 9/ 10S - Build Probe
68.65: 95M 0G 39E 10/ 18S - Build Probe
68.65: 45M 0G 39E 11/ 18S - Chrono Nexus
79.98: 126M 0G 20E 11/ 18S - Build Probe
88.89: 146M 0G 25E 12/ 18S - Chrono Nexus
91.40: 165M 0G 1E 12/ 18S - Build Probe
102.73: 213M 0G 8E 13/ 18S - Build Probe
116.65: 291M 0G 16E 14/ 18S - Build Probe
133.33: 407M 0G 25E 15/ 18S - Chrono Nexus
133.54: 409M 0G 0E 15/ 18S - Build Probe
137.45: 400M 0G 2E 16/ 18S - Build Nexus
144.88: 73M 0G 6E 16/ 18S - Build Probe
152.13: 100M 0G 11E 17/ 18S - Build Pylon
157.65: 55M 0G 14E 17/ 18S - Build Probe
171.43: 150M 0G 21E 18/ 18S - Build Gateway
177.13: 65M 0G 25E 18/ 26S - Build Probe
177.78: 22M 0G 25E 19/ 26S - Chrono Nexus
182.31: 75M 0G 3E 19/ 26S - Build Assimilator
188.68: 74M 0G 6E 19/ 26S - Build Probe
201.13: 178M 0G 13E 20/ 26S - Build Probe
202.83: 150M 0G 14E 21/ 26S - Build Gateway
212.31: 118M 0G 19E 21/ 26S - Move Probe To Gas
212.31: 118M 0G 19E 21/ 26S - Build Assimilator
212.31: 43M 0G 19E 21/ 26S - Move Probe To Gas
218.13: 108M 8G 23E 21/ 26S - Build Probe
235.13: 269M 32G 32E 22/ 26S - Build Probe
237.45: 248M 35G 34E 23/ 36S - Build Probe
237.45: 198M 35G 34E 24/ 36S - Build Cybernetics Core
237.45: 48M 35G 34E 24/ 36S - Chrono Nexus
241.30: 100M 41G 11E 24/ 36S - Build Zealot
241.30: 0M 41G 11E 26/ 36S - Move Probe To Gas
248.79: 95M 56G 15E 26/ 36S - Build Probe
248.79: 45M 56G 15E 27/ 36S - Move Probe To Gas
252.13: 90M 65G 17E 27/ 36S - Build Probe
261.45: 172M 92G 22E 28/ 36S - Build Probe
261.45: 122M 92G 22E 29/ 36S - Build Assimilator
267.83: 138M 109G 26E 29/ 36S - Build Zealot
269.13: 56M 113G 26E 31/ 36S - Build Probe
275.09: 100M 130G 30E 32/ 36S - Build Pylon
287.45: 194M 164G 37E 32/ 36S - Build Stargate
290.88: 100M 24G 39E 32/ 36S - Build Zealot
290.88: 0M 24G 39E 34/ 36S - Move Probe To Gas
290.88: 0M 24G 39E 34/ 36S - Move Probe To Gas
294.23: 50M 37G 41E 34/ 36S - Build Probe
297.57: 50M 50G 42E 35/ 36S - Build Probe
297.57: 0M 50G 42E 36/ 36S - Move Probe To Gas
305.83: 123M 87G 47E 36/ 44S - Build Zealot
305.83: 23M 87G 47E 38/ 44S - Chrono Gateway
311.23: 104M 111G 25E 38/ 44S - Build Probe
314.57: 107M 126G 27E 39/ 44S - Build Probe
314.57: 57M 126G 27E 40/ 44S - Move Probe To Gas
317.33: 100M 140G 28E 40/ 44S - Build Pylon
328.88: 174M 198G 35E 40/ 44S - Build Zealot
333.83: 157M 222G 38E 42/ 44S - Build Zealot
333.83: 57M 222G 38E 44/ 44S - Chrono Gateway
347.97: 300M 293G 46E 44/ 52S - Build Fleet Beacon
361.83: 228M 162G 54E 44/ 52S - Build Zealot
361.83: 128M 162G 54E 46/ 52S - Build Pylon
366.88: 111M 187G 56E 46/ 52S - Build Zealot
372.29: 100M 214G 59E 48/ 52S - Build Pylon
399.83: 453M 351G 75E 48/ 68S - Build Zealot
399.83: 353M 351G 75E 50/ 68S - Move Probe To Gas
404.88: 436M 379G 78E 50/ 68S - Build Zealot
404.88: 336M 379G 78E 52/ 68S - Chrono Gateway
404.88: 336M 379G 53E 52/ 68S - Chrono Gateway
408.76: 400M 400G 55E 52/ 68S - Build Mothership
408.76: 0M 0G 55E 60/ 68S - Chrono Nexus
411.80: 50M 17G 32E 60/ 68S - Build Probe
424.88: 215M 89G 39E 61/ 68S - Chrono Gateway
424.88: 215M 89G 39E 61/ 68S - Chrono Nexus
427.50: 258M 103G 15E 61/ 68S - Build Probe
427.83: 214M 105G 16E 62/ 68S - Build Zealot
430.22: 155M 118G 17E 64/ 68S - Build Zealot
430.22: 55M 118G 17E 66/ 68S - Chrono Gateway
444.44: 300M 196G 25E 66/ 68S - Chrono Nexus
458.76: 556M 274G 8E 66/ 68S - Satisfied.

5:38 - 8 stalkers, 18 probes
+ Show Spoiler +

Third3ye

United States3 Posts

November 13 2010 00:56 GMT

#72

The 8 stalker build is interesting. You can actually have 7 stalkers and it boosts the gateways just to get out that last stalker so I bet if you run it at 7 stalkers it cuts down the time quite a bit. Having 7 stalkers right around 5 minutes seems pretty fast to me.

If I recall correctly, a three rax MM push should arrive at around 6 minutes if it's really tight so it seems about right. Feels as if with this sort of build order you could overrun a three rax.

When's the terran version coming out? :D

DragonDefonce

United States790 Posts

November 13 2010 01:03 GMT

#73

This is awesome. However, I think it would be much, much more useful if you added in the ability to add buildings and upgrades? Such as how to get 5 stalkers with blink fastest or something like that. Great work though

Barook

Germany143 Posts

November 13 2010 01:05 GMT

#74

I get a mfc100u.dll error when trying to run the exe, despite having both the file and VC++ 2010 Redistributables x64 installed (Windows 7 64 Bit).

What's a way to fix the problem? Installing the the x86 version?

CarbonTwelve

Australia525 Posts

November 13 2010 01:24 GMT

#75

On November 13 2010 10:05 Barook wrote:
I get a mfc100u.dll error when trying to run the exe, despite having both the file and VC++ 2010 Redistributables x64 installed (Windows 7 64 Bit).

What's a way to fix the problem? Installing the the x86 version?

Yes, you need the x86 redistributables.

Barook

Germany143 Posts

November 13 2010 02:45 GMT

#76

On November 13 2010 10:24 CarbonTwelve wrote:

Show nested quote +

Yes, you need the x86 redistributables.

Thanks, that worked.

Pretty nifty programm, although it certainly could need some additions like buildings, research and warpgates.

I also noticed the probe count isn't exactly optimized. If you don't put in a number, you may end up with a probe count below the optimal, possible amount in that build. Maybe you should include some option that you continuously build probes while doing the build whenever possible?

gotlucky

United States60 Posts

November 13 2010 07:02 GMT

#77

I hope this doesn't come off as a stupid question, but just so I'm clear: I can go through 30 million games in about a minute...are those 30 million games equivalent to 30 million games of Lolimar's program? In other words...what would take me hours to do with his program, this can do in 1 or 2 minutes?

It seems like that is what you were saying, but I just want to make sure I understand.

Thanks and keep up the good work!

dcemuser

United States3248 Posts

November 13 2010 07:13 GMT

#78

On November 13 2010 16:02 gotlucky wrote:
I hope this doesn't come off as a stupid question, but just so I'm clear: I can go through 30 million games in about a minute...are those 30 million games equivalent to 30 million games of Lolimar's program? In other words...what would take me hours to do with his program, this can do in 1 or 2 minutes?

It seems like that is what you were saying, but I just want to make sure I understand.

Thanks and keep up the good work!

I believe that Lolimar's program only counts in games that achieve the result. This program counts all games, I think.

Nevertheless, this is still much, much faster, just not by a factor of a million.

Stromming

Sweden64 Posts

November 13 2010 09:51 GMT

#79

Thanks a ton, this will sure be useful, especially if you add upgrades support!

Razzers

United States24 Posts

November 13 2010 10:19 GMT

#80

thank you so much! works nicely, i will for surely put it to use