Path file issue: ~.path failed to load

[AdrianD]

Thanks for the responses.

The specific path file from gukbottom was kindly given to me by Mr. provocating. It was the first zone I utilized this tool in a couple days ago.

It looks like the maxnodeid is being set at nodecount - 1 like your code quote says but, that is not the real maxnodeid. I don't know how it is supposed to work but, setting the maxnodeid = nodecount -1 is obviously incorrect if a functional #path remove option exists. Maybe resetting the nodeids is an easier solution than correcting the counting function. I don't know.

Corrupted .path files have been around a while I imagine. As long as I have been around here. I know this much.

I can't say using #path remove is the only thing that could corrupt a .path file but, it seems apparent it does. I haven't heard of this issue in the few threads I've searched. I think it's possible people have just accepted this as "working as intended" to not stir any pots.

I was watching the memory/cpu usage as various zones were being loaded and #showpathnode -ed. I understand some zones are more complex than others. Point being, the potential efficiency gain is present and may be worth looking into.

Thanks