Well, if this:

Is true, then that seems unlikely, since most protectors delete the Isom section.

Ah, well I also agree with this. In my much earlier post I explained that the terrain in my map (somehow) was all corrupted and transformed into rec tiling. I probably put it into some crappy compression or map unprotector, or something stupid. For some reason certain spots of the map would crash the editor if I tried to modify them. The point is, the entire map was converted from isom to rec tiling, and then I received the nooks and crannies error. I've also helped a couple people, one or two, with this error by re-making certain parts of terrain with the isom brushes to try to correct any parts of the terrain that might be causing problems, and it worked.

How about we ask blizzard why this error comes up...

I think it's been mentioned that the pathfinding AI tries to plan out paths while loading the map... Perhaps it's optimized by checking the ISOM data instead of the rectangular tiles? (That is, perhaps it plans paths isometrically -- it works with a larger grid, so it covers more terrain at once. With normal terrain, there wouldn't be any lost detail -- it wouldn't skip over any walls. It can just say, "Is this ISOM tile walkable or not?" and in doing so, cover a good 8 or so terrain tiles.) If that's the case, then anything that (severely) complicates, removes, invalidates, or renders inaccurate the ISOM data would cause this error.

I had this error in my RPG, but found that I was cramming too many tree doodads in one place. After I removed them, the error went away. I think it's doodads causing the problem.

Honestly it seems to me that it happens when you have too much of one thing. Or close to that.

The only thing I added to my map is about 40x40 tiles of that neat qPK's blend.
I was wondering if Heimdal or Farty could crack out the answer from some SC source code or something? D:

I've updated the first post, is there anything I have missed?

I had a nook and crannies error like this in two maps I made in the past, were instalations made with ye' old staredit. It was ''labyrinth'' like maps... The errors were caused by too much narrow path, it was isom-made paths that were just big enough for a goliath/dragoon to walk in. I know it was caused by this because when I removed the longest parts, it worked again.

Doodle sent me a map that was just dirt with a small spot of water copied and pasted as many times as would fit... It gives the error.

Following the MTXM function I found a little call that leads to a huge pile of functions. ;o
Including...


Post has been edited 2 time(s), last time on Jan 22 2010, 12:17 am by FaRTy1billion.

And that means...?

The point is the text. ;o I found the function that contains the error.

I don't even think that StarCraft uses the Isom section though, I think it's only used by editors, since it seems kinda odd that the map would still be playable with it deleted if it was used at all. I think perhaps the SC Pathing AI is created with the intention of being used in isometric terrain, and all the extended terrain we do messes this up. Although that still doesn't explain why using a protector changes anything.

Starcraft\SWAR\lang\sai_PathCreate.cpp is referenced, followed by Starcraft\SWAR\lang\sai_ContoursCreate.cpp

I don't think blizzard anticipated people using "extended terrain," and if this is so, the error message they made was intended for use in isometric terrain.

The map I use to induce it is purely isometrical.



Post has been edited 1 time(s), last time on Jan 22 2010, 3:12 am by FaRTy1billion.

There's a limit of 5000 paths. If the "path limit"(that is what I'm calling it) is exceeded, you will get the error.

Could you define path for us? Because it seems like there's more than 5000 paths easily pickable in most maps

I have no idea. All I know is that if there is more than 5000 of "something", the error will pop.
Paths probably refer to the AI paths(unit paths are done real time).

how the hell did they avoid it in CD then, absolutely everything is connected.