Not really a limit to pathnodes, but if you deleted them and it still crashes then i'm not sure. Maybe a bug?

Crash log from editor.log ?

I even sent a long time ago Smirf such a (test)map where exactly this happened. A path node or reachspecs limit is unknown. At least the engine source does not tell anything about this, regarding his words. In fact he was unable to debug it (afaik a microsoft software he was using failed to debug this stuff there, I don`t know what he was using anymore), so he could never figure that out. Not sure if it changed through time. Such bugs got even reported to occur in ut2004 (ed).
BTW: For such logs you are actually supposed to use uhm a site called pastebin or something like that.

GreatEmerald wrote on 02/18/12 at 14:35:02:

Nope, I already tried both, also tried "to last".

For the records, I've had the map cause a "crash on save" multiple occasions before, always only after rebuilding new brushes I recently added that the editor, for whatever reason, did not like. A building with multiple vertical rooms caused that a lot and I had to remove 1 or 2 rooms.

And there it in pastebin, I forgot about that website completely.

http://pastebin.com/1VGXDuGa

So far, I'm not reassured at all :/

Is there any way to massively select things -excluding brushes-? And I don't mean select all actors (EDIT: Which selects brushes anyway -_-). I wanted to, say, clean up a portion of the actors in a map at a time (half/half) and find out if a specific bunch of path nodes are causing the issue.

EDIT: Nevermind that: I tried moving all the path nodes elsewhere then cutting them in half, then place them back, rebuild, save, and either half I cut, it saved properly.

There are lots of streets, but if an area is very open, I don't just put nodes everywhere, there's just one line in the middle or to the sides.

I'm looking at my map after a rebuild before I save with Show Paths, and most are pretty separated. There's a few spots with -lots- of stacking lines however. I guess I could try reworking that?

I fixed most of what I could, but there's tons of InventorySpot called in Editor.log that don't exist in the map at all.

Also tried deleting all inventory actors (there's -lots- of them) but that doesn't stop it from crashing. That however removed all the remaining warnings.

I tried exporting/importing in a new map right before your post and it did not work (the results are exactly the same).

Removing a quarter of the path nodes exactly doesn't seem to cut it. I need to remove a bit more. So far, I could save with 1239 path nodes, but not with 1390.


Now there is something weirder here: I have many earlier backups of the map. Some of them weren't fully pathed or finished at all, and saved properly after a rebuild, even if they have 1600+ path nodes. However, when I try -now-, it does NOT work.

I -could- be wrong and my memory is fuzzy, but I don't understand how I have so many backups before it if I didn't have this issue earlier with the path nodes. I do know that in those maps, all path nodes are linked, so it -was- properly rebuilt then saved.

Thanks but I'm not sure how thats useful? It might clear the spots if I could save but since I can't...

You're just gonna have to keep deleting pathnodes untill it works. I read another problem like this on an unreal tounrmanet forum and they said it could be just one pathnode or a whole bunch causing the problem. Just delete the "inbetween" pathnodes that aren't really needed

Buster wrote on 02/20/12 at 15:30:09:


With 227, you can simply use restricted paths for that (although it still leaves the view rather cluttered).