Rutger wrote:Small update: the crash happens in an obscure part of the engine... which just so happened to have broken crash reporting. So I've just put a new build of the game live on Steam (I can't update the GOG build myself, so that'll have to wait a little longer), which includes better crash reporting for that particular area. If you run into this issue again, please give a shout in this topic, and I can look up the crash report. Thanks for your patience! I'd hoped to have this fixed a lot sooner. :(

Hello. Just to clarify, are you saying the problem is in theory solved but that you fixed the crash reporting just in case or that you could only fix the crash reporter and that we should try to reproduce the crash again so we can send the report with the new tool ASAP?

Nope, only fixed the crash reporter, although I have been getting reports that it might have resolved the issue itself. Since I've put up the fix on Steam I have not gotten anymore crash reports for that bug, which seems a little too convenient.

In the off chance this might be helpful here's a fix someone posted in the GOG forums, after trying this fix and doing a run it seems to have fixed it for me also:

chlee0725: I had the same issue, and I fixed it today.

Uninstall the game, start Galaxy "Run as Administrator," and reinstall the game. After that, go to the game folder (in my case, it's located in C:\Program Files (x86)\GalaxyClient\Games\Renowned Explorers) to start the game "Run as Administrator." Exit the game, and start the game on Galaxy.

I had this same problem back in June and it was fixed by an update back then. However, I started playing again recently and it started happening again, under identical circumstances. I have the up to date gog version of the game.

Sorry you're running into this! Could you send your abbeycore.txt log file (which you can find after the game crashes in the game's installation folder) to support@abbeygames.com, so I can take a look at the exact crash? :)