JeffreyC

2.7.9 still has the same problem with not ending missions. The fix on here from BuzzLine is still the only fix for the problem. Had the problem until putting this fix back in and have not had the issue again since. When it shows up is hit and miss usually, but this issue occurs every time with the USAF Weapons School campaign. Reproducing is simply flying the mission, ending, and clicking End Mission with nothing happening in the results screen as always.

Just an FYI for those who may wonder, the bug is still there and this fix still works. Another thanks to BuzzLine

The End Mission not advancing is a DCS bug that shows up at times. There is a user made fix I'm including link to the thread for you.

Well at least I was slightly on the right track Sounds like a lot more updated too, amazing! Very much still enjoying it! I run through this campaign with all my aircraft Fantastic is an understatement for how good it is.

Noticed the instructor isn't taking off since the new DCS update. It also seems he isn't spawning. This might be related to an internal name change for the Nevada map and saw MOOSE has an update to address this.

Love your splash damage! Thank you so much for making this!!

I've only used them with the new GUI. The only problem I have had it when restarting a campaign when I had the problem you described. In that case I removed the campaign completely and made sure it was gone in DCS, reinstalled and set up the first mission, then loaded DCS and selected the campaign. If you haven't already tried it might be worth a shot.

well that was pretty stupid of me! Thanks a million! It generates without error now.

You got it. There is no "title" line in conf_mod.lua. I did edit the camp_init.lua you stated in your other message. I attached both. conf_mod.lua camp_init.lua

Thanks that fixed a large number of errors but now it's getting the error: E:\SteamLibrary\SteamApps\common\DCSWorld\bin\luae.exe: ../../../ScriptsMod.NG/MAIN_NextMission.lua:231: attempt to index local 'loadoutFile' (a nil value) stack traceback: ../../../ScriptsMod.NG/MAIN_NextMission.lua:231: in main chunk [C]: in function 'dofile' ..\..\..\ScriptsMod.NG\BAT_FirstMission.lua:403: in main chunk [C]: ?

I can't seem to find if this is known anywhere. I'm having an error with "Harrier Over Caucasus-LHA" Every time trying to start the first mission in the DCE Manager it has an error: "E:\SteamLibrary\SteamApps\common\DCSWorld\bin\luae.exe: ../../../ScriptsMod.NG/ATO_Generator.lua:26: module 'Debug/db_loadouts_archive' not found: no field package.preload['Debug/db_loadouts_archive'] no file '.\Debug/db_loadouts_archive.lua' no file 'E:\SteamLibrary\SteamApps\common\DCSWorld\bin\lua\Debug/db_loadouts_archive.lua' no file 'E:\SteamLibrary\SteamApps\common\DCSWorld\bin\lua\Debug/db_loadouts_archive\init.lua' no file 'E:\SteamLibrary\SteamApps\common\DCSWorld\bin\Debug/db_loadouts_archive.lua' no file 'E:\SteamLibrary\SteamApps\common\DCSWorld\bin\Debug/db_loadouts_archive\init.lua' no file '.\lua-Debug/db_loadouts_archive.dll' no file '.\Debug/db_loadouts_archive.dll' no file 'E:\SteamLibrary\SteamApps\common\DCSWorld\bin\lua-Debug/db_loadouts_archive.dll' no file 'E:\SteamLibrary\SteamApps\common\DCSWorld\bin\Debug/db_loadouts_archive.dll' stack traceback: [C]: in function 'require' ../../../ScriptsMod.NG/ATO_Generator.lua:26: in main chunk [C]: in function 'dofile' ../../../ScriptsMod.NG/MAIN_NextMission.lua:361: in main chunk [C]: in function 'dofile' ..\..\..\ScriptsMod.NG\BAT_FirstMission.lua:403: in main chunk [C]: ?" I have no problems with "Falcon Over Caucasus", "Hornet over Caucasus-CVN", "Tomcat Over Caucasus-CVN", or "Harrier over PG-LHA" so at a loss why this one is having a problem when the other 4 don't. Have tried re-downloading and reinstalling the campaign with no change. Anyone have any idea what is going wrong with this one campaign?

4.1.1 is really good. 5.0 preview is . Don't even plan on using that when it comes out, sticking with 4.1.1. Hoping 6.0 might be better or ED will move forward with the real dynamic campaign.

After seeing the changes done in the latest preview release of Liberation, I'm even more hopeful for the ED Dynamic Campaign to come out to replace it.

Sad to hear DiCE (DCS Integrated Countermeasure Editor) has replaced this. I tried it before and went back to this as I have liked it a lot more. Might end up for each update to install DiCE, make the changes, the remove it again. Still appreciate the work put into making it easier than having to edit files manually.

I noticed him on my wing specifically on the F-16C 4v2 ACM. He didn't fire since he made no Fox-2 calls in the 2v2 ACM but that could have just been chance, I didn't think to check on what he was doing. I did find that on Fox3 the instructor does fire for sure.

Is there a way to clear a hung start without restarting the mission? Just had it hang for the first time. I thought it was stable at 20% but not absolutely certain. In any event, the fault needs to be able to be cleared for doing another start and aborting the mission doesn't seem right. Scratch that, Full shut down of the plane and sitting for a bit clears it. Had it sitting which checking the forum

Not sure if I'm doing something wrong, but the instructor doesn't seem to be engaging the enemy in 2v2 and 2v4 missions. I tried a couple different planes and notice this last time after he calls that he is engaging he remains in formation on my wing. I remember way back he would break and attack but that was several versions ago so things might have changed and I missed a new instructions.

For the most part yes especially for flying issues. But the popups don't tell you everything listed there. It gets to increase RPM to 100% and even with throttle all the way it keeps flashing the same thing. Something with the RPM/Throttle registering for the popups is not detecting the engines being revved up.

Regarding notifications, there seems to be an issue with them detecting throttle. It keeps repeatedly showing the notice to increase to 100% even with throttle at 100%. Still repeats even with lowering then pushing the throttle back up again (have assigned to an axis on my HOTAS with the traditional throttle axis as the collective).

Looks great and did a few flights yesterday it in. Great work! Any chance a future release might have the troops spawn for use after deployment like the paratroopers do in the Anubis C-130 mod?

You give better support than many professional developers! With so many aircraft supported and complexity some things creeping is in not at all unreasonable to expect. Thank you for your ongoing great work on this campaign!

I have some weirdness on the AV-8B 2v2 ACM mission. The instructor followed me to the runway, took off after I did, but then turned around and landed instead of forming up. Turned off the map restrictions to get a better picture of what was going on after the first time it happened. Your triggers are WAY over my head so afraid I can't really offer anything on what could possibly be the cause so a track file is about the best I can do showing what is going on. AV8B 2v2 Instructor lands.trk

Tried the newest version (2.1) with the present update for DCS (2.7.5) with the AV-8B and when mission is completed it does not respond to End Mission. Clicking but button after exiting the mission just sits there. If I fail the mission by exiting it without doing anything End Mission does respond. Interestingly, in the General Debrief Data the Mission Name and Pilot are both blank. I do not know if this problems happens with other aircraft as I have not tried with other aircraft at this time.

Only found this happening in the Persian Gulf map so far, two others worked correctly. The HUD view point for the TPOD is far above where the TPOD actually looks. Tried with F-16C Litening pod and F/A-18C ATFLIR. Got track for F16C. hud target for tpod way off.trk

Latest updates targeting pods are not locking to designated target way-points/steer-points. Have reproduced in F/A-18C and F-16C in both cases pod will stabilize if slewed to a target and set to track, but entered points drift and do not lock on to the target. This may or may not be a reason pod does not now slew to a target that coordinates were programmed in. This I have only found an issue in the latest 2 open beta releases including the one today. pod does not lock on designated waypoint 2.trk pod does not lock on designated waypoint.trk