Ok, this bug has stalled my entire game because it is such a large flaw. I am currently working on a major Starcraft map. Whenever I click "start" at the mission briefing to begin the game, Starcraft crashes. I thought something was wrong with that map so I brought up an older version of the same map, which worked when I pressed "start" to begin the game.

HOWEVER, once I edited the map and added new stuff to it (JUST TERRAIN, no doodads or triggers or unit fixes) and saved a new file, yet again the bug which crashed my previous game returned.

This is major because it doesn't allow me to play my game whatsoever. I put about 8 days into this project, so I'm really worried about if anyone could play my game at all.

I have no idea what could cause this, does anyone know what I can do?!

It appears I can only make a certain amount of terrain changes? I think this is retarded so I don't even want to consider it, but to be honest that's what I see. Everytime now that I add structures(badlands terrain) it fails, when I delete some (add dirt) it works. Keep in mind I'm like halfway into my project so my map is like halfway full.

I decided, since I have no other real choice, to show you guys my map and try to figure out wtf is wrong. I worked real hard on it and it sucks that it's failing halfway through. The file size might be moderete for a sc map (2.5 mb), but I was gonna reduce it once I got more done. Plus I added a few songs, one I'm not even using atm.


Keep in mind I didn't add any enemies yet (except some scourge) so I could test the game triggers and stuff without interruption. Feel free to look around my map in game and in editor.

If you need me to tell you any information about the map just ask and I'll post it here.
Also, keep in mind this map is in it's alpha stages, just made the name beta cause it's shorter .
For checking, try adding a bunch of terrain improvements on the map, then saving, then trying to begin it. The map I attached is the LATEST WORKING version, but I'm sure any more terrain improvements will cause it to crash.

Any help would be appreciated, and if we get through this I'll add your name in the credits for good measure .




Post has been edited 1 time(s), last time on Sep 7 2009, 2:12 am by EzTerix.

Null is bad. If you have Null on your map, there is a slight chance that it will drop you.
Nobody say this isint true. Sometimes generated null crashed the game. This is experience talking
Maybe you added a doodad that went off the map boundary. Im not sure if this will crash you, but it would still be safe to double check if one went off the boundary.
Heres what I suggest.
Save a copy of your map.
Open up your map.
Select "Doodads"
Once you can select doodads, hit CTRL+A
Hit delete.
All your doodads are deleted. Now, save the map as a different file, then host it.
If your map doesn't crash, then you know its the doodads fault. Do this same thing again except with units. Im not completely sure if this will solve your case, but at least you will be able to get an idea who the perpetrator is.

http://www.staredit.net/wiki/Crashlist
Or post the error log so Heinermann can tell you what's wrong.

How do I post an error log?

Anyway, I'm still circling around this issue. Checked the crash lists, are these like the only known crashers or are there more?
I'm not telling people to do the problem for me, just to point so I can know wtf I'm suppose to do.
The error still exists, I checked the edges of my entire map and I don't see any loose doodads. I have no idea what could be causing this. All I know is that I was working on terrain one day and then boom this crap came up.

Any others tips for me? @_@

EDIT:How do I post an error log?

Anyway, I'm still circling around this issue. Checked the crash lists, are these like the only known crashers or are there more?
I'm not telling people to do the problem for me, just to point so I can know wtf I'm suppose to do.
The error still exists, I checked the edges of my entire map and I don't see any loose doodads. I have no idea what could be causing this. All I know is that I was working on terrain one day and then boom this crap came up.

Any others tips for me? @_@


EDIT2:
Ok I narrowed it down, apparently there is some doodad at the west side of the map causing all this trouble. I don't know how, I don't know why, I just know I need to find and delete it. If this works I'll give fire1337 credit in my credits. Ultimo thanks but you lead me into a vicious circle, but your help is appreciated anyway .

Now to find that doodad...

Post has been edited 1 time(s), last time on Sep 10 2009, 8:50 am by NudeRaider. Reason: merged posts

when starcraft crashes, it will tell you why it crashed, usually in the form of nonsensical (to you) numbers. Revert to an older version is the best way. I recall a map where the terrain was corrupted.

Well when my game "crashes" I mean that when I press the "start" button on the mission briefing, I see nothing but blackness and then I am returned to my desktop. No numbers or anything unfortunately, I did have numbers before but that was for a misplaced tank or car or whatever.

There is an error folder in your Starcraft directory, but I'm not sure how that works really.

I deleted a few triggers (like 57) at a small portion of the town and the game worked. I'm thinking I should just delete those 57 doodads and then redo that area?

btw is there a maximum doodad limit, I have about 400ish doodads @_@

Uh, I got your map working. All I did was delete stuff really close to the edges of the map, like there are two sets of beacons on the left side along with three shield batteries on the right. I deleted those and started up the map and it worked.

Keep in mind I attached the last WORKING version to this thread. Make like a bunch of structures(terrain) all over the bottom right and then try the game again.

EDIT:
I MAY have figured this out. I deleted all the hospital doodads (the outside of hospital, not inside) and the game worked. I have no idea how this could have effected me to this extent but I will redo the hospital outside and further edit my map and see what happens. If it fails, I'll return. If it works, your all in my credits .

EDIT2:
OK, no the game does not work, and apparently I was like in a wild goose chase with the doodads because apparently the area I thought the evil doodad was, is like non existent.

Anyway I am tired, I have no idea what can be causing this, and I have doubts about the future of my map. A toxic concoction for any map maker.

Things I need to knowish
-how many doodads can be on the map
-what in the world can be causing something so wierd.
If you want just dl my map, add a bunch of terrain structures at bottom right, then try the game. It will not start I swear.

Help, I'm like dieing here >_<

Post has been edited 1 time(s), last time on Sep 7 2009, 6:20 pm by NudeRaider. Reason: merged posts

You've obviously done something else wrong, I have never heard a case where Null has dropped the game, it's just like any other tile, unless you're using some weird extended Null.

Are these all just doodads, or sprites? to narrow it down further, in the Doodad layer, select all the doodads in the area you say is bad, and right click and do "Convert to Terrain", then go to the Sprites layer and select all in that area and delete everything you select, this will narrow it down to just the sprites, leaving about half your doodads.

Doodads are sort of a virtual thing, it's just terrain sometimes attached to a sprite, I had an image a little while back with around 65,000 doodads on a single map, so a limit isn't the problem, the real limit you gotta worry about is the Sprite limit, which is 499. I'm guessing you've managed to pass the 499 limit by placing enough doodads with attached sprites, try removing a bunch of sprited doodads and see if it runs.

You should attach the map that is crashing then, what is the point of giving us the map where it doesn't crash? We can't really solve your problem then.

K put a non working version at first post.

EDIT:Well it says my total limit is amount of sprites is 190(I even checked by deleting all doodads, then sprites as you said). So since the limit is below 499 I don't see a problem with sprites.

Post has been edited 1 time(s), last time on Sep 7 2009, 6:21 pm by NudeRaider. Reason: merged posts

Yeah, I tried it out, didn't see a problem with your sprites at all, or the units. It's the doodads

Oddly enough, I simply converted all the doodads to terrain, and then tried running the map, and got the nooks and crannies error, seems to me you're going to have to do something to change your terrain, because nothing is really certain on how to fix that glitch.

Oh my. Just have a couple questions.
What is the "nooks and crannies error"?
Second question, by changing terrain do you mean a complete overhaul of the entire terrain on the map? Or do I just start a new map? I worked on a TON of triggers on this map already because I was slowly connecting the story with the triggers with the terrain.

Well, it's an error that just seems to randomly come up with maps, it seems to happen more often when they're heavily doodaded, but lots of maps get away with it(Crescent Dyne, for example), so I would just try changing some of your terrain around, you don't need to make a new map, just try doing some major terrain overhauls and see if it fixes the problem.

Ok does this effect units? Also is it necessary for me to change the entire terrain (structures, asphalt, water, high dirt, etc) of the map or do I just have to delete a bunch of doodads and replace them differently?

If you delete a lot of the doodads this may fix the problem, units have nothing to do with it.

K, I deleted all the doodads except a couple bridges that I didn't really feel the need to remove and then replant at the same spot.
I think I noticed before that when I removed a ton of triggers the problem sorta went away, but I was way too confused and unwilling to delete a days work and then take another day to redo it.
Hopefully this stops the problem once and for all, I would HATE to see it return .

I am far too tired to work on it today, I actually spent most of today and some of late yesterday trying to fix this. Also I'm behind my personal schedule on when to finish this >_<.
It's ok though, I'll just pretend this is room for improvement and making the game better.
Thanks for the help, you'll be in the credits for sure =).

Would right-clicking and converting the doodads to terrain fix this, or no?