[Nemesis6]

I've seen quite a bit of this, for example the Shivans 0.2 campaign is totally broken by the new exe files, I'm wondering what exactly is happening behind the scenes that produce these showstoppers.

[Fury]

I'm not familiar with most mods out there, but giving a proper description of problems encountered along with contents of fs2_open.log after running said mod with debug build would go long way in determining what the problem is.

However, my guess is that the problem is not in 3.6.11 exes, but in the mod itself. 3.6.11 is far stricter and comprehensive in its error checking routines and is far more likely to spew out errors, warnings and asserts when there is bad mod data. And this is a good thing as it helps making mods far more stable and bug-free. Of course, it also breaks older mods like you've said. But in the long run, it's definitely worth it.

[General Battuta]

Broken how? Giving warnings, or actually crashing and preventing you from proceeding?

There are no new instabilities. The new .exes simply warn and yell about major problems that previous versions tried to stumble past.

[Nemesis6]

Broken how? Giving warnings, or actually crashing and preventing you from proceeding?

There are no new instabilities. The new .exes simply warn and yell about major problems that previous versions tried to stumble past.

Drawing again on the Shivans 0.21 campaign, what seems to happen is after the very first mission, I am stuck. I see the hud, when I speed up or stop, I can hear it, but it's as if my viewpoint hasn't adapted to my fighter and yet the enemies don't seem to engage me. No error message or anything. Then again, that is a very, very old campaign as far as I understand.

[Fury]

Run d-build, aka the exe in where there is d after version number (fs2_open_3_6_11d). After you're stuck again, post contents of FreeSpace2\data\fs2_open.log. Preferably as an attachment. Also, does this mod work with 3.6.10 or 3.6.9 build?