A quick update: I've now finished most of the work on the vehicle data (land and air) and emplaced/armament weapons, and am now making a start on infantry weapons. I should hopefully have the 2.26-compatible minimod more or less complete within a week, but I'll still have to do a lot of testing before release just to check there's nothing "broken".

One thing I have noticed about 2.26 is that the aibehaviours.ai file (in mods\fh2\ai) is a HUGE step backwards from 2.25 - it looks like all Legion's improvements have been abandoned. I'd highly recommend you replace it with either the original 2.25 file, or the one from my minimod v1.2 (which should be compatible with 2.26)

I was going to start a thread like this myself, but no need now! Here's what I've noticed so far, from playing or looking through the files - probably not a complete list, though. I wrote this before seeing your post, so it repeats a few things you've already mentioned.

- SP support for Gazala! (no Alam Halfa, though) - plus PHL is now available in the SP menu (previously co-op only)
- Bombers now work properly (and the Stuka strafes targets as well)
- Bots can aim AT guns (the ones I saw - 2pdr, 6pdr and Flak 88 - at least)
- Bots use mortars! - at least when they can see their targets; the German mortar was shelling the British lines on Siege of Tobruk.
- The Sherman .50 cal bug (which caused the Luttich loading CTD) is fixed.
- Satchel TKing has been fixed ("c4" behaviour is set to 0.0 in the AI behaviour file - which seems to have had quite a few other tweaks since 2.25)
- The train locomotive has an AI profile (still no SP maps with it in, though)

On a less positive note, the static Pak40 CTD is still there (at least this is an easy fix). Some other things haven't been fixed, such as the messed-up min/max ranges for tank weapons, and the kamikaze AT mine attacks; playing 2.26 has reminded me how bad the unmodded AI is, bots are much less aggressive and there's a lot of clueless/"headless chicken" behaviour, with opposing bots and vehicles running around or facing each other apparently trying to work out how to fire their weapons...

Still, it's good that most of the serious bugs and CTD causes have been addressed. AI modding should now mostly just be a case of tweaking + improving rather than fixing (hopefully).

Since the next version of my minimod will be 100% re-done using the 2.26 files, it should incorporate all of the 2.26 improvements such as Nebelwerfer use (haven't seen this yet) and plane behaviour. (Really not sure how the latter got "broken" in my mod, but since planes need much less modification now, it shouldn't happen again)

I was just about to post the same thing!
With the various SP fixes + addons, there are several playable maps with the Tiger - Goodwood 64 is now (nearly) CTD-free, and Op. Cobra and Totalise are now playable. (No King Tiger yet, though)

It may be a while (2-3 weeks) after the 2.26 patch before fully compatible SP files are ready, though. I suspect Remick04's new maps will work, but my AI fix minimod won't (and if it does, you'll miss out on most of the additions + fixes in 2.26)

Great idea - should be very useful having all the SP-related files available in one obvious thread, some of them like Winterhilf's Falaise + Goodwood are very hard to find otherwise.

It'd probably be a good idea to host my AI minimod on the mediafire site as you've done with the other files, I'm not sure what the bandwidth capacity of my webspace is. There shouldn't be a problem with keeping the file updated, as when I update the minimod I'll upload a new file (and post a link here) rather than updating the existing one.

Definitely sounds like the problem is due to the archives from a previous version being in the FH2 folder. If you've installed the minimod by extracting the files + putting them into the FH2 archives, you don't need the mod archives or serverarchives.con.

I set up my minimod with seperate archives to make it easier to revert to unmodded FH2 for playing online - it's also easier (probably) to install for those who don't have much experience with altering archive files.

This is very odd... With the aircraft disabled, the map runs fine - but with any aircraft (I've tried every possible combination) it will inevitably CTD sooner or later (usually sooner). But it looks like I'm the only one experiencing this issue.
I've tried reverting to the 1.2 AI minimod files (after disabling the train) and have tried removing my modified AI strategy files for the map, but still get a CTD every time.
What's even weirder is that none of the aircraft cause any CTD problems on other maps. I tried disabling all the AA guns instead of the aircraft, in case one of these was the actual cause of the crash, but no luck.

Looks like I'll just have to wait and see if the updated Mount Olympus works OK for me!

I also spotted the stuck bots in the Monastery ladder room, and there appears to be another upstairs spawn point, in a room accessed by stairs, where bots get stuck; this may just be a pathfinding/navmesh issue, as they should be able to use the stairs. 

BTW, please don't take all these error reports as criticism - you've done some amazing work in getting these maps working so well in SP. (Many of the "official" maps have just as many bugs and/or CTD issues)

Had a CTD as soon as I shot the Pak at Flak battery. Maybe I forgot to update something.

Have you installed the latest version of my AI minimod? That fixes the Pak40 destruction CTD.

To add to Djinn's post - if any of the FH2 devs are reading this, I'd be happy for any of the fixes/changes/ideas in my AI minimod to be "stolen" for a future patch, if you don't want to use my modifications directly. I don't mind not being credited, I just don't want to have to start again from square one when 2.26 is released 

The AT gun and bomber fix, and the various CTD fixes (Sherman top MG, Pak40, Compo B, Jeep) ought to be in at least, as they're straightforward bug fixes rather than tweaks or additions. The PIAT CTD fix needs more work though, as my temporary fix allows you to equip the weapon when out of ammo. (I'd be interested to know why the "switch when out of ammo" line causes CTDs when bots use it...)

The raised artillery viewpoint is definitely NOT suitable as an "official" addition though, as there's no way to make it only appear in SP/co-op games, and it will probably make artillery overpowered in MP, as it allows you to see further without using a spotter.