Alan

Is anything logged in stderr.log when you do that? Maybe you have the wrong architecture of Allegro?

To clarify, the question about stderr.log was only for the person who manually replaced their allegro libraries. It's very unlikely that anything useful would be logged there otherwise.

Weird, https://github.com/DFHack/dfhack/commit/00d39e270ca17d13520080a1bcf86dc555e9370f should have fixed that. Did you have a libfreetype.6.dylib directly in the `hack` or `libs` folder (_not_ `hack/libs`)?

Ok, moving it shouldn't have changed anything, then, because DFHack would look in hack/libs after looking in hack. Can you check what DFHack version you're using? It'll be logged in...

I suppose it's possible that Stonesense is picking up an incompatible freetype from inside SDL_ttf (which is in libs, which is searched first). @cvandermeer can you run `devel/lsmem` in the...

Edit: wait, you said *after* the fix? That makes even less sense - moving libfreetype didn't even do anything, as far as I can tell! Yeah, it is loading SDL_ttf's...

Oh, you did that too? That wasn't what fixed https://github.com/DFHack/dfhack/issues/649 so I assumed you had only replaced freetype. It was more likely allegro, then - what allegro version were you...

Unfortunately no, the algorithm does not store the necessary information for flying creatures. This is what `pathable` uses, and there is no related field for pathing through the air: https://github.com/DFHack/df-structures/blob/fc098e53fce4fdd112a52690188a23b1e177a013/df.map.xml#L292-L297...

Anything in stderr.log?

How in-progress is this?