"This map could not be loaded because it had too many obstructions. Try widening cooridors and reducing the number of small nooks and crannies to correct the problem."
Why is the editor so picky? I think it's a pathfinding issue, but why the error?
(I fixed it on my map by the way; I was just wondering.)
-EE
I have never heard or seen that error. You sure someone wasn't messing with you while you were on some bad acid trip?

what does this have to do with terrain?
lol I have no idea but this problem has occured with Killer2001 before I think...
This happens when you a hugh amount of edges and small openings within your isometric terrain.
Basicly just simplify things and widen small paths.
I have never seen that error, isn't that when the map is in Illigal dimensions?
I remember DK showing me a map he made to test the speed of units ect...
It kept crashing and gave us that Error
It was because he had an island 3 spaces wide wiht a 1 space gap inbetween the islands for ALL units in the game... It crashed for that reason lol...
Why would Blizzard do that then? They never really had square tiles like we had now so this can't be the issue. It was meant for something else that we don't know but it seems like it has to do with what we thought but not necesarilly.
That happend to one of my maps. Had to restart the terrain.
I've seen this error one or two times before. It happens when you have passages that are mainly intraversible. As it says, widen corridors and such. It happens in maze-type atmospheres.
woah, how can an editor know problems like that in a map?
ya, there has been like 4 threads on this. somebody should test it on square terrain because im pretty sure that it did it for that also.
It occurs when the pathfinding engine fails to init.
Very, very weird, never happened to me before.
Can someone Move this now? It has nothing to do with terrain.
And this Error can also occur when stacking buildings in a messy form. The Buildings will take up the exact same cordinate Point and cause the map to show you this error. I don't think anyone else posted this problem on SEN before(or at least before i was here).
What the hell? This has everything to do with terrain, and has NOTHING to do with units or triggers. This can also happen using classic Staredit by the way.
This happen to me too many times I've been annoyed by this! But finaly someone posts a topic about it!
Hmm..Never had this happen to me before. I dont experiment with terrain so much that it crashes. Odd that it would.
wait so this only happens with square terrain yet it can happen on original staredit? i dont understand what the base of this problem is
It doesn't have to be square terrain, it can be regular isometric terrain.
QUOTE(Suicidal Insanity @ Feb 18 2005, 05:45 PM)
It occurs when the pathfinding engine fails to init.
[right][snapback]148236[/snapback][/right]
Whats init mean? Just it fails to start up or something?
I understand what your saying but your not saying much. Do you know much more specifics about it?
What is the Pathfinder engine?
I reproduced this effect using every terrain peice (in the jungle set) , so I think that might have something to do with it; but it could have seen this as an unclear path. This is one effect that has plagued me for a while on rpgs. Someone should find out what the limit is for this, and what sort of limit it is.