Report, edit, etc...Posted by Gold_Member on 2006-11-14 at 23:54:30
Wow I have no idea if i did something bad but whenever i start up this game im making and try to build an scv from a command center starcraft crashes. help plz 
Report, edit, etc...Posted by ReCoN on 2006-11-15 at 00:48:35
Wow thats really weird, did u place the wrong unit?
Any triggers that have to do with it?
Any triggers that have to do with it?
Report, edit, etc...Posted by DT_Battlekruser on 2006-11-15 at 01:37:05
900 to 1 gets that you set its build time to zero.
Any unit with zero build time will crash instantly upon creating; you must set its build time to a very small number like 1 (use Starforge or SCMDraft and '1' will be the equivalent of 1/15 in Staredit), not 0.
Any unit with zero build time will crash instantly upon creating; you must set its build time to a very small number like 1 (use Starforge or SCMDraft and '1' will be the equivalent of 1/15 in Staredit), not 0.
Report, edit, etc...Posted by Lord-Omega on 2006-11-15 at 10:54:42
QUOTE(DT_Battlekruser @ Nov 15 2006, 01:37 AM)
900 to 1 gets that you set its build time to zero.
Any unit with zero build time will crash instantly upon creating; you must set its build time to a very small number like 1 (use Starforge or SCMDraft and '1' will be the equivalent of 1/15 in Staredit), not 0.
[right][snapback]589520[/snapback][/right]
Any unit with zero build time will crash instantly upon creating; you must set its build time to a very small number like 1 (use Starforge or SCMDraft and '1' will be the equivalent of 1/15 in Staredit), not 0.
[right][snapback]589520[/snapback][/right]
if u want zero for timing put 8765 and it will be interperted as zero
Report, edit, etc...Posted by Wing-of-no-Wing on 2006-11-15 at 15:21:33
Using a build time of zero will cause PC users (but not Mac users) to crash when they build such a unit. In order for PC starcraft to build a unit without crashing, it has to show the progress bar at empty and the progress bar at full. This takes it 1/15th of a second to do. Mac starcraft only has to show the progress bar at empty, and can thus build a unit in about 1/30th of a second, taking 0 time to go from when building starts to when the unit is built, as opposed to the one frame necessary for a PC.
I sometimes start work on a map on my Mac before emailing it to my other computer for further progress; in order to test gameplay where building-based control systems are concerned, I'll temporarily set unit build times to 0, allowing me to test the map at full speed (actually, slightly faster than the final speed, but only by 1/15th of a second), though if anyone else tries to use the building system in the test version, they'll crash.
I sometimes start work on a map on my Mac before emailing it to my other computer for further progress; in order to test gameplay where building-based control systems are concerned, I'll temporarily set unit build times to 0, allowing me to test the map at full speed (actually, slightly faster than the final speed, but only by 1/15th of a second), though if anyone else tries to use the building system in the test version, they'll crash.
Report, edit, etc...Posted by mugen on 2006-11-15 at 16:14:39
QUOTE(Lord-Omega @ Nov 15 2006, 10:54 AM)
if u want zero for timing put 8765 and it will be interperted as zero
[right][snapback]589578[/snapback][/right]
[right][snapback]589578[/snapback][/right]
Doesn't work 8765.
Report, edit, etc...Posted by Heimdal on 2006-11-15 at 16:18:36
If you managed to acutally set it to 0 then you're using an editor that doesn't multiply by 15 for you (SF, for example). To fix this just use 1 instead of 0.
Report, edit, etc...Posted by Ultramilkman on 2006-11-15 at 16:25:31
QUOTE(DT_Battlekruser @ Nov 15 2006, 01:37 AM)
900 to 1 gets that you set its build time to zero.
Any unit with zero build time will crash instantly upon creating; you must set its build time to a very small number like 1 (use Starforge or SCMDraft and '1' will be the equivalent of 1/15 in Staredit), not 0.
[right][snapback]589520[/snapback][/right]
Any unit with zero build time will crash instantly upon creating; you must set its build time to a very small number like 1 (use Starforge or SCMDraft and '1' will be the equivalent of 1/15 in Staredit), not 0.
[right][snapback]589520[/snapback][/right]
Mods work with 0
but then the unit hp gets cut [ex] 200 hp turns to 167
Report, edit, etc...Posted by Heimdal on 2006-11-15 at 20:37:27
I really doubt that. This is a divide-by-zero crash in the starcraft engine. I don't see how a mod could change this.
Note that units that can be built without you seeing the progress bar won't crash - usually this only means buildings. But even then, if you click on the building as it's being built you will still crash.
Note that units that can be built without you seeing the progress bar won't crash - usually this only means buildings. But even then, if you click on the building as it's being built you will still crash.
Report, edit, etc...Posted by DT_Battlekruser on 2006-11-15 at 20:41:22
This is not true. (to ultramilkman) Any created unit with zero build time will crash. When you see diminished HP, it is true of units that are built at extreme speed (less than 1 second).
They spawn with fewer than full HP, or shields, or whatever else.
They spawn with fewer than full HP, or shields, or whatever else.
Report, edit, etc...Posted by Nintendo_Confed on 2006-11-19 at 08:26:43
QUOTE(Lord-Omega @ Nov 15 2006, 12:54 PM)
if u want zero for timing put 8765 and it will be interperted as zero
[right][snapback]589578[/snapback][/right]
[right][snapback]589578[/snapback][/right]
That only works for Upgrades. You cant set any unit to 0, it has to be 1. Any unit with 0 build time will crash the game.
Report, edit, etc...Posted by Heimdal on 2006-11-19 at 13:56:22
QUOTE(Nintendo_Confed @ Nov 19 2006, 08:26 AM)
That only works for Upgrades. You cant set any unit to 0, it has to be 1. Any unit with 0 build time will crash the game.
[right][snapback]591410[/snapback][/right]
No, no, no.[right][snapback]591410[/snapback][/right]
A little lesson on build times:
The build time that gets stored in the map is actually stored in fifteenths of a second. Staredit divides this number by 15 before displaying it to you, and it multiplies the number you type in by 15 before saving it into the map. Starforge, on the other hand, allows you to set the number directly including setting it to 0.
So what happens when you type 8739 into staredit? It multiplies it by 15 (so you get 131085). Now the build time is stored as a 2-byte short integer, which has a max value of 65535. The higher order bits will get truncated (this has the same effect of taking the modulus by 65536), and you're left with 13. So, next time you view this value in SE, it will divide 13 by 15 and display 0 (but the build time isn't actually 0). This process is the exact same as if you had just typed 13 into starforge.
Long story short: If you use Starforge, never type 0 into a build time for a unit. Use 1 instead. If you use Staredit, type 8739 and you will get a slightly longer build time.
Report, edit, etc...Posted by Ultramilkman on 2006-11-19 at 22:24:11
QUOTE(DT_Battlekruser @ Nov 15 2006, 08:41 PM)
This is not true. (to ultramilkman) Any created unit with zero build time will crash. When you see diminished HP, it is true of units that are built at extreme speed (less than 1 second).
They spawn with fewer than full HP, or shields, or whatever else.
[right][snapback]589823[/snapback][/right]
They spawn with fewer than full HP, or shields, or whatever else.
[right][snapback]589823[/snapback][/right]
Thanks for clearing that up.