Anyone had that map that, after you worked hard on it and you try testing it, it freezes on the loading screen without any reason, at all? I'm having this issue right now, and I don't know what is it. It must've been a fruit of the 2.1.6 patch that literally screwed everyone over. I did the terrain, very hard work, and even checking again and again for something wrong, the map won't load. It stucks on 90% and that's it. Sometimes at 50%, but that's after the 'streaming data' thing is done doing it's job.
I've been looking at it a bit more closer and realized it's not an internal coding issue, but rather one of the doodads, or a lot of them, responsible for the freezing. I'll be taking a closer look and try to get to the root of it as I progress piece by piece.
Hook the SC2 process to a debugger and check if it is still doing anything. It is possible that the loading will take an excessively long time (dozens of minutes). This often happens with complex maps on systems with low memory as the SC2 editor + the actual game process can cause page faults to occur.
Hanging is usually the result of an infinite loop, an infinitely blocking operation or a deadlock.
I just discovered what it is - It's the Pathing Cliff Fill tools (Under Dynamic Pathing Fill) used to prevent any ground unit getting into that particular cliff level, even if it's large and clean. This just occurred as I added them just minutes ago and then I had ordered a test.
Anyone had that map that, after you worked hard on it and you try testing it, it freezes on the loading screen without any reason, at all? I'm having this issue right now, and I don't know what is it. It must've been a fruit of the 2.1.6 patch that literally screwed everyone over. I did the terrain, very hard work, and even checking again and again for something wrong, the map won't load. It stucks on 90% and that's it. Sometimes at 50%, but that's after the 'streaming data' thing is done doing it's job.
I've been looking at it a bit more closer and realized it's not an internal coding issue, but rather one of the doodads, or a lot of them, responsible for the freezing. I'll be taking a closer look and try to get to the root of it as I progress piece by piece.
Hook the SC2 process to a debugger and check if it is still doing anything. It is possible that the loading will take an excessively long time (dozens of minutes). This often happens with complex maps on systems with low memory as the SC2 editor + the actual game process can cause page faults to occur.
Hanging is usually the result of an infinite loop, an infinitely blocking operation or a deadlock.
I just discovered what it is - It's the Pathing Cliff Fill tools (Under Dynamic Pathing Fill) used to prevent any ground unit getting into that particular cliff level, even if it's large and clean. This just occurred as I added them just minutes ago and then I had ordered a test.
Sounds like something for Blizzard to fix.