VeeSPIKE

No, it does not.

Another thing that works, if you have the ability, is toe-braking to nudge the nose one way or the other. Sometimes NWS over-steers, particularly once you get up to speed. One or two light, quick taps on the appropriate brake is enough to work the nose back in to line.

That faint roaring noise you hear, sounds a little like your gear are down just not as loud? Yeah, that.

A little more thinking on my part, because I know I have used my method before. Forgot a part. One of the things that Lib does when you run it is it replaces the default MissionScripting.lua in your DCS\Scripts folder with one of its own. And then it switches them back when it closes. I had forgotten that part. You can force the issue on your own, either manually or with a batch file. Make a copy of your [DCS]\Scripts\MissionScripting.lua. Save it is a different folder. Replace the original DCS file with the MissionScripting.lua file found in [Liberation]\resources\scripts Run DCS and run your mission. You should not see any more errors (from this issue anyway. You can leave it as-is afterwards or, once you are finished switch back the original file that you saved in the first step. You could write a batch file to do this for you, or just handle it manually whenever you want to replay liberation missions. I just tested this process this evening. I got no script errors after changing the lua.

Open the "liberation.nextturn.miz" in the ME, Save As [cool filename here], and close the ME. Run the mission you just saved over and over and over. Then, when you are ready to move on, run Liberation normally and save your results.

Campaigns from version 5 or 5.1 should still be compatible with 5.2. Campaigns from earlier versions are not.

There is a centerline option for 5 Mk82/SE's

Yep - from the Patriots Jet Team - https://patriotsjetteam.com/

Are you using any mods? When you last updated, did you Clean and Repair?

If this was in multiplayer, server desync causes some really weird stuff sometimes.

The Updater generates a log file in your Saved Games folder. Check that to see if there is anything specific going on. The Updater has run fine for me since the last DCS update.

Use the in-game module manager. It has a section for terrains. YOu can deactivate and delete installed modules from there.

You do that either with a launch command, or with a dcs_variant.txt file in the dcs root - assuming that your "pure" and "default" are based in separate installs. https://www.reddit.com/r/hoggit/comments/mgnvgb/cant_run_dedicated_server_and_dcs_on_same_machine/ "1st is if its actually a separate install of the dedicated server. Go to its install folder and create a "dcs_variant.txt" file. In this file just type whatever you want. When you launch DCS it will create and use a folder in saved games as DCS.whateverYouTyped." Note that this was written applying to running a server alongside a client. But it should work just as well for what you are trying to do.

You could also try messaging the mod author and ask if they are still active and working on it.

Adding to Cfrag's answer, you can also set script flags to spawn units on events. So if you wanted to have a SAM unit go active if a boundary is crossed, it can be done that way.