I haven't played FS2 for years, but today I decided to go back through War in Heaven, and it's been... a little unstable. I updated Knossus, updated all my mods, and everything went well for a while...
My first time through Delenda Est, in the middle of a dense furball, the framerate dropped to single digits for a few seconds, and then it crashed to desktop, producing a mdmp file containing an access violation. I'd tell you more, but I couldn't reproduce the crash, and I can't figure out where to get symbol files. I could upload the mdmp file somewhere if you want it.
I then used Knossus to enable fast debug. This resulted in a ton of warning popups that seem to indicate Blue Planet's models and tables need to be updated to modern standards. Clicking through them every time a mission or cutscene loaded was a real drag.
My first time through Nothing is True, I got right up to the part at the end where I ordered my wingmen to attack the federation fighters, and then an assert triggered: "total_ammo" at aicode.cpp:5740
From skimming the code, I think this means that somehow an AI ship with only ballistic weapons (probably my wingman... maybe the Custos?) somehow ended up with its maximum ammo set to 0. Couldn't reproduce on second runthrough, not sure how I would, though of course I could run through the mission a dozen times if you want me to be thorough.
I got through Everthing is Permitted withough errors, but then when I went to the dreamscape afterwards, I experienced another access violation with mdmp during the Custos training sequence. No idea what triggered it, but there was no framerate drop this time.
My log is here: https://fsnebula.org/log/60b73bc1d6a16939c439130d
I am running Windows 10 on some seriously old hardware (~2013), and I haven't tried a ton of troubleshooting, but I'm not really sure where to start, with nothing clearly reproducible. I just figured I should log my experience.