Staredit Network > Forums > SC1 UMS Mapmaking Assistance > Topic: Known causes of EUD crashes
Known causes of EUD crashes
Mar 25 2018, 1:46 am
By: Lanthanide  

Mar 25 2018, 1:46 am Lanthanide Post #1

With SCR supporting EUD editing, we have new abilities that has not been widely used before, so there is limited knowledge about the things that will cause crashes in SCR. So this thread aims to consolidate any discoveries made about EUD changes that will cause SCR to crash or freeze.

Setting unit vision to 12 or greater
The maximum vision distance for any unit is 11. Setting it to 12 or greater will result in a crash.

Changing unit size for units already in the map
This occurs for pre-placed units, and perhaps also units that you create, then subsequently change the size of (untested). This, along with the crash below, was one of the infamous freeze/crash bugs in the map I was working on, that I bored many people in Discord with. I spent about 45 hours testing to get to the bottom of this problem.

The actual crashes/freezes seem to be with the Unit Finder code, which is what is used to determine if units are at a particular location, for any of the unit-location based trigger actions and conditions (move unit from location to location, kill unit at location, bring unit to location etc). There are two algorithms used for the unit finder depending on the size of the location being referenced. Small locations (8x4 tiles or smaller) are vulnerable to a variety of freeze/crash issues, eg if you pre-place a unit X on the map and change the size of that unit via EUDs, then bring that unit to a small location that is being used for other trigger purposes (moving unit Y to that location), the presence of unit X at that location can cause SC to freeze.

Units that are newly created after the unit size is changed are not affected. It also seems that if you create a new unit of the same type after changing the size, that the original units of that type will no longer cause freezes. This needs to be confirmed with more testing though.

Setting any unit dimension to 0
Similar to the above, a unit which has a dimension of 0 can interfere with the unit finder algorithm and result in a crash or freeze in Starcraft. I don't have a 100% clear understanding of what is required for this to cause freezes, but it was definitely happening in my map.

I have a test map that demonstrates the freezes you get with small size locations when a pre-placed unit has its size changed. The map also demonstrates a freeze that seems to be related to a unit having a dimension of 0, but the mechanics behind this freeze are a little weird.

Download link for 0-dimension freeze example map:

See the map description for how to reproduce the freezes and how to edit the map to see some more weird behaviour.

Post has been edited 5 time(s), last time on Mar 26 2018, 4:23 am by Lanthanide.


  Back to forum
Please log in to reply to this topic or to report it.
Members in this topic: None.
[10:44 pm]
Ultraviolet -- 1337 ejaculator
[10:29 pm]
ejac1337 -- derp
[07:08 pm]
Slyence -- Well shucks ..
[2021-11-26. : 4:02 am]
O)FaRTy1billion[MM] -- Slyence
Slyence shouted: I could've swore I used to have a colored username.
probably, they did get reset at some point
[2021-11-26. : 4:02 am]
Apos -- :wob:
[2021-11-26. : 12:01 am]
UndeadStar -- 🦃 Just saw a new news 🦃
[2021-11-25. : 6:04 pm]
Slyence -- Meme x2
[2021-11-25. : 12:39 pm]
Moose -- meme
[2021-11-25. : 12:25 pm]
Slyence -- I could've swore I used to have a colored username.
[2021-11-24. : 10:56 pm]
RdeRenato -- xd
Please log in to shout.

Members Online: Roy, Oh_Man, MetalGear