BuzzLine

I had the same issue, I'm not sure how the mission is supposed to unfold there. Happy to hear some hints !

Just to balance things a bit, I'm one of those who play DCS campaigns for the roleplaying aspects as well as the flying, rather than for the action proper. I've thoroughly enjoyed this campaign, as I did The Crew pt 1 (will there ever be a part 2?) and even Oilfield that has zero combat.

I also got bitten by this issue and it took me half of forever to understand the cause. (yes call me lazy, I used to skip setting the ALT value before alignment). Did the default altitude change from zero to 99999 at some point ? Or maybe in the past the radar used to read the altitude from the altimeter ? Anyways, that seems a bit strange to use the INS to feed the altitude to the radar, is that the same on other airplanes ? I always thought they used data from the altimeter...

You need to "transfer licenses" (sync would be a better term) after each Steam purchase. Go into your DCS account, edit profile, section "steam account", click "get licenses" (new items show up in green) then click "transfer licences". And now you should own PG also on standalone as well as Steam.

Hear, hear ! Sharing this classic : https://m.xkcd.com/1053/ Sorry for the off-topic comment but it'd be nice if more people shared in this philosophy.

I just finished the Huey variant, I'll try the Gazelle later on. Flying and mission design : excellent. Short missions with good atmosphere and many things happening in the background. Never too hard but no piece of cake either. I liked that the copilot would set up the radios, etc. That's a really nice touch. Briefings, inflight discussions, etc : would be excellent too, but I found it a bit hard to follow at times. I guess the translation could be improved as some sentences don't feel quite right sometimes. Nothing major but since there's a big backstory, it would make it even more valuable. Nitpicking: I would have loved to fly an Mi-8 again ! (my fav helo ) Now I may have to buy the Jeff to get the next part of the story Keep up the good work.

My fix doesn't affect your stats, those are stored in your "Saved Games" folder. The file to replace is ED's code inside the main DCS folder (hence the need for me to re-update it regularly when they update the file but still don't pick up my fixes).

Error in the manual : "This example will use the altitude of Nellis Air Force Base: 4867 ft" (page 240, section 19-4, setting up the INS) No it's not. The real altitude of Nellis is 1869ft. See https://en.wikipedia.org/wiki/Nellis_Air_Force_Base , and (more importantly, perhaps) it's what is used in the game. I wonder if, for this French plane, someone has used the French version of wikipedia that also gives this erroneous number, or if it's a coincidence ? Cheers !

The two (and a half) campaigns by BD really do it justice. I love the sounds of the switches ! They feel heavy and authentic. The Mirage 2000C: an elegant weapon, for a more civilized age.

BTW: update for 2.7.11.21408 (with the double fix) me_logbook.lua

Hey @Flappie , I saw a change in the code that may be related to this issue but I'm not sure it actually fixes the issue. Can you still reproduce on your side ? Thanks, Buzz.

@rge75 Feel free to pick my fix for the End Mission bug (see above). I update it at every patch release (it covers the train fix and some other ellusive bug).

Most of those airframes are 40-50 years old. Remember the computers of that time ! (for those who can ) We have the benefits of hindsight and decades of UI/UX research and testing.

Sorry, obligatory reference. Thanks Terry Dactil for the comprehensive information, most interesting.

I had no idea ! Many thanks, I love history What an extraordinary place. Now I want to go and visit... @MiG21bisFishbedLyou should do a mission/campaign where people would fly to all those places in Syria and you would provide all the historical context and references. Maybe using the T-51, so everyone could fly around ?

Nice ! Where is that one ? Also take a look around Palmyra, some good places for chopper sightseeing ! BTW, is there a list of all the sights, ruins, monuments to visit ?

Side note : I think that ED only does prepurchases and rebates for their *own* modules' launches. Third party modules are only sold when they are ready, and at full price. Later on, there are the usual sales, of course. But pre-launch: only ED, as far as I know. (That does not change the logic of what Baco and Get_lo said. One may still need to carefully plan their investments. Just pointing out some minor detail that may make the decisions easier. Or not. )

Super amazing, @Reflected ! All the thought and attention to detail shows in the final product so keep up the good work. I'd love to hear more about Mission Editor techniques from wizards such as yourself or Baltic Dragon. I like to dabble a bit to build missions for own enjoyment but my skills are not in the same league as yours. Looking forward to your future work.

Thanks ! Happy to help. On a parallel matter, I've been trying for months to reproduce in a "lab environment" the other EndMission one (the old one from last year) and it's still eluding me so far... If I ever corner that SOB I'll send it over.

Also see this one : Doubly fixed file provided in this thread too, as a convenience. me_logbook.lua

@Cael: I've started the campaign (lots of fun so far, good job !) and had the same issue as @xmegasuro on the Patrol mission, despite flying with my own fix for the End Mission bug. Apparently, this may be caused by killing locomotives ? Anyhow, fix available here (both issues) :

New bug causing "End Mission" button not to work. (note this is not the same root cause for the other End Mission bug) Description : fly a campaign mission, kill a locomotive, watch the "End Mission" button not working when quitting. This error found in the dcs.log : ALERT LUACOMMON: Error: GUI Error: [string "./MissionEditor/modules/me_logbook.lua"]:1147: attempt to perform arithmetic on field 'Rate' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./MissionEditor/modules/me_logbook.lua"]:1147: in function 'updateUserStatistics' [string "./MissionEditor/modules/me_debriefing.lua"]:361: in function 'updateStatistic' [string "./MissionEditor/modules/me_debriefing.lua"]:385: in function 'endMission' [string "./MissionEditor/modules/me_debriefing.lua"]:351: in function 'onChange' [string "./dxgui/bind/Button.lua"]:22: in function 'callback' [string "./dxgui/bind/Widget.lua"]:368: in function <[string "./dxgui/bind/Widget.lua"]:363> Cause : locomotive objects lack a score value (called "rate" in the code) and this causes a null ref error. Solution : add a score value to locomotives (and other objects I guess) and/or fix the code in the stats updater (see attached) Attachments: - micromission to duplicate the bug (for your convenience, I used the Su-25T so no need for special modules). Lower the nose and shoot the train. - track of me flying - dcs log of the error (it's not quite the same mission but the stacktrace should be the same) - a patched lua file with both my fixes for the two causes of End Mission bug that I'm aware of. debug_endmission_bug2_train.miz BUG_endmission_locomotive.trk dcs_BUG_Mi24_Patrol.log me_logbook.lua

I'm with you. I flew most ingress/egress legs with the Fighter Pilot Podcast playing in the background, so honestly, I didn't mind the long flight times.

You probably know that it's the same in the corporate world. Everytime we have a new head of Marketing, we start a poll to guess the date when we have a new logo. Closest wins the pot.