Sadly I keep running into the same crash with KeeperFX
"Error: triangle_find8: Infinite loop detected" basically
it does not seem stable, tried unofficial and then 0.46, same crash, too frequent :(

That's the pathfinding bug. It was already there in the original game, but seems to come up more in keeperfx. It appears on maps with many different routes from point A to point B, especially if the road there goes from land to water/lava and back.

It's not an easy fix, since the bug takes place in the code from the original game that still isn't rewritten.

Damn. Kind of kills it for me I think :[ I'm not sure I want to tweak my playstyle and try many times until it stops crashing, expecting it to crash. I think I'm going to try DK 2. DK has made strong impression on me since long time it was nice to play it again, I was gonna play it more and make maps but it seems it needs fixing, won't be fixed, idk what to say i think i'll drop it :[ Bullfrog made lot of impressive games too bad this is flawed!! >.<
thx for your replies

It doesn't have that much to do with playstyle. There are a few maps that would only crash if you for example give the AI forever to make massive dungeons, but those are very rare. Most maps don't really crash at all unless you specifically try to, or always crash.

If you want to play without risk of crashes, look here, where maps are reviewed and it is mentioned if they crash or not.
Maps made recently also don't really crash as mapmakers who still make maps know about the limitations of the game.

If this is too buggy for you, I'm afraid DK2 isn't going to be much help here. DK1 is pristine compared to DK2 in the bugs department. The gog version of DK in particular has the broken AI, where it never defends with more than 1 unit. And that's besides the crashes, compatibility issues and weird stuff like units attacking from the north doing more damage than units attacking from the south.

I ran into this crash multiple times playing the campaign first 12 missions or so :/
I like to make large dungeons with many paths and in some cases take time before I attack enemies. So I run into this crash 30minutes into the game or so.

so GoG's DK2 is bad too... I asked for refund for DK1, bought them together, hope they'll refund DK2. Its pretty sad, man in particular I love DK1, I think it's quite captivating, but it's hard to keep playing it in these conditions. Basically I understand it's gonna happen more if dungeon is large with more paths, and if you stay longer on a map and if you attack or finish off your ennemies later. So I could tend to avoid it by making smaller and simpler dungeons with less paths, stay a shorter time on maps and attack opponents earlier and try to win earlier. That's a lot to put up with imo :/ for a game like this! And I read that as a important limiter of playstyle. Besides I understand (and remember) it did NOT crash that often back in the day!

Could you do me one favor, that might help solving the pathfinding bug. Reinstall KeeperFX, but an old version instead, try it with 0.4.2, play like you usually do and tell me if you also have the pathfinding crash in that version (you might not, and that will solve your issue). If not, update to 0.4.3 and later 0.4.4 so we can see if indeed this issue has become more common now than it has been in the past and when this has started.

I'm willing to do that,
however the download mirrors at http://keeperfx.keeperklan.com/ fail to complete downloads. Tried multiple times and also ran into this earlier for 4.6 where I used Mega mirror to complete download. The other links for older versions at http://keeper.lubiki.pl/html/dk_keeperfx_older.php just point the Keeperklan downloads so they also fail. Is there any other place for getting that, or somebody still have them and upload them again or fix the keeperklan downloads?

I can download the files just fine. I believe it's an issue for people with a slower download speed.
So I downloaded 0.4.2 and uploaded it to MEGA for you:

https://mega.nz/#!tcAmwa4D!CxNu8Eg8uhfRX2qlmf_tojHaMjfGhMJG879IRTfHMec

Thanks, I just replayed the campaign map that I ran into crash each time with 0.4.6, this time with 0.4.2 I was able to complete it without crashing playing the same/similar way. I'll keep playing and see if I run into crash again let you know.

Thanks.

Here's 0.4.3:
https://mega.nz/#!lIxnQICA!gGvpFdLfqi783lMDdKhZ0jIvDEdRMtytlynZbM75vXY
And here 0.4.4:
https://mega.nz/#!NV5BVaAa!Iv371VNDQ6t-k0DIQsrZ7NnMxcXR2AV_F0yv5fUUJ4A

Other mega links can be found on lubiki.

This bug is really hard to pin down. There's the suspicion it happens more frequently in new versions than that it does on old versions, but no way to consistently do it. We have plenty of testmaps that show the bug soon and reliably, but they also hang/crash in the original/gog versions of the game.
But there could very well be a change that makes the game run into the crash sooner, which sucks for people/maps who used to get by and now not anymore. And that might not be a bug in itself, could be a simple as a change that causes the AI to be a bit more active.

hey loobinex i reached the final map of the campaign and never ran into the pathfinding freeze again with 0.42 playing from about the middle of the campaign, so despite running larger dungeons for longer times
i did run into 1 crash once but it wasn't the same bug and it just shut down the game instead of freezing (also didn't crash again upon redoing same thing from loading before it occured, its probably rather rare bug and no big deal(?) happen when wizard stand on 1 square surrounded by lava and tries to target attacker who is over lava then over his square or something like that)
so as opposed to latest version of keeperFX which got pathfinding freeze multiple times doing the first half of the campaign, no pathfinding freeze at all on 0.4.2 on the second half
[the main thing that 0.42 version is missing is game music playing from game if you put music files in folder]

next i will try running a few times one campaign map that was repeatedly running into pathfinding freeze with 0.43

That's easy, just use the -level command line option.