BuzzLine

experience

I'm working my way through the campaign and had this same issue at M2. I switched the condition (>12m AGL and >11kts) to a simple "unit outside zone" and it flowed perfectly well.

And ... all done. Amazing campaign ! No issue to report aside from the usual AI misbehaviors, like wingmen not taking off for several minutes sometimes. Also, the Spitfire air cover in M7 (the v1 site) did not really engage the enemy: one pass then they hauled a... Maybe they ran out of fuel and went home ? I had lost an engine due to flak and got downed by the 190s but I probably would have outrun them on two engines. But everything that matters worked. Superb work, again.

To whoever is interested: Netflix has a movie called "The Bombardment" about Operation Carthage with surprisingly good-looking Mosquito scenes. A great companion to a great mission, my favorite of all the daytime ones. An excerpt : https://www.youtube.com/watch?v=tYNlewIxAvg "Watch for seagulls"

@Flappie I think the Spitfire has the same issue. I can recheck if needed. MT+2D.

M4: what a blast ! It helped to have seen your Youtube video, I'll admit. Those searchlights are terrifying down low, I got blinded several times. Minor detail : Tacview-20230312-221035-DCS-VV - 04.zip.acmi

Hey Reflected, I've been waiting for that campaign ever since you talked about it and so far (2 missions done, crashed in a tree during 3rd) I'm absolutely loving it, it's everything I hoped it would be. I was flying so low I picked up a few nits for when you have a second: Unless they are jokes that I missed (am still flying so low, lots of things can pass over my head ), I think there's a few typos in the english subtitles: all (?): "This is Air Sea Rescue, recieving you loud and clear."=> receiving intro : "capatin" , "arthery" , "appauling" There's a few minor issues with cosmetic triggers: M1 : as I was flying back from the convoy, pilot said "roger" out of nowhere. Could be his answer to the "This is Dungeness, we're almost home" call that was missing. M2 : I took off late for oboe and the call "it's time, heading 087, altitude 25k ft" happened while I was still taxiing. Thanks again, congrats, and looking forward to flying the rest of the missions ! EDIT: pressed <enter> before I could actually type my message

Well what do you know. Official fixes seem to be in today's patch. From reading the code, I can see: The very first "End Mission" bug from way back when : fixed The one caused by trains : fixed The custom campaigns : probably fixed (They wrote a different fix than mine so I don't know, but let's assume it works too) Note : this is for todays openbeta. If someone reads this and is still on stable, either wait, upgrade, or use the two files I fixed (a few messages up). Even better : use the official me_logbook.lua and me_campaign.lua files from today's patch, the only differences with the stable branch are the fixes for those bugs.

An elegant weapon display system, for a more civilized age. I love learning how stuff works. Thank you for sharing !

They might be 737s flying for JANET airline. Old timers who flew FSX back in the days might remember that there was a mission flying one of those shuttle flights between Las Vegas and Area 51.

+1 on the UH60, especially since it is free Mi24 FM is interesting too, "feels" right too but it's a tricky beast to fly, being both heavy and powerful. But Huey remains my favorite to learn helicoptering.

Yes, you have to re-apply the fix after updates. I usually post my updated version whenever they change the file. Good news is that all should be fixed in the next official patch. If not, then I'll post a new file in this thread.

Those delays are measured in milliseconds (or dozens of) in order to allow the bomb to penetrate a bit before exploding. Not sure how much of that is implemented in DCS but here's some light (?) reading on the question of bomb fusing : https://www.fighterpilotpodcast.com/musing/understanding-the-fmu-139-and-its-employment-options/ And some less light reading in this master's thesis : https://trace.tennessee.edu/cgi/viewcontent.cgi?article=2979&context=utk_gradthes

The further on the edge The hotter the intensity it's also true for openbeta...

@Wiggo: Grab those two files with my fixes and give it a try. Your logbook should not have been damaged. The good news is @Flappie told me ED had fixes for all those issues, I hope they will be in the next patch. me_logbook.lua me_campaign.lua

Try adding an air defense unit (like a manpads). Set its ROE to weapons hold if you don't want them to react to enemy aircraft. That should do the trick.

@FalcoGer those red units are capturing/challenging your FARP maybe ? What if you spawn them more than 2km away (I think the capture radius is 2km) ?

Probably with the use of multiple missions per stage and some clever use of scoring to fall on the right one.

@bertog Right. I'm not seeing any error I recognize in your dcs.log so I'm not sure why the mission did not register ! At any rate, you can edit the logbook to fill in results for the 1st mission and point to the next mission : [8] = { ["created"] = "Sat Jan 28 20:13:32 2023", ["player"] = "Guy Mc Birtolz", ["campaign"] = "C:/Users/Ursula2/Saved Games/DCS/Missions/Campaigns/en//FA-18C - Bold Cheetah/FA-18C - Bold Cheetah.cmp", ["status"] = "Active", ["history"] = { [1] = { -- ///// THIS IS A FLOWN MISSION, ALL FIELDS ARE FILLED ["stage"] = 1, ["mission"] = "Bold Cheetah Mission 01 - A Show of Force_Cold Start.miz", ["datetime"] = "Sat Nov 12 20:27:14 2022", ["aaKills"] = 0, ["agKills"] = 2, ["result"] = 100, ["deathsCount"] = 0, }, -- end of [1] [2] = { -- ///// THIS IS THE NEXT MISSION, ONLY THE FIELDS 'STAGE' NUMBER AND 'MISSION' FILE ARE LISTED ["stage"] = 2, ["mission"] = "Bold Cheetah Mission 02 - CAS for Badger_Cold Start.miz", }, -- end of [2] }, -- end of ["history"] }, -- end of [8] Previously, your logbook showed only the [1] section and it was empty as a "next mission". I copied the additional fields to make it a "flown mission" and added the next mission to fly under [2] (note: really make sure this is the next sequential number or bad things will happen). This is what we used to do to skip a mission before ED added the very convenient 'skip mission' button. The "stage" value usually corresponds to the mission number but it may not be the case for complex campaign setups with branches and stuff, YMMV. Try the attached file (I didn't test it, there might be bugs ). Make backups of your logbook.lua before any changes, obviously. logbook_bertog.lua

@bertog is your logbook corrupted ? What are the symptoms ? Send your logbook.lua and dcs.log and I'll take a look at it.

Definitely make a backup ! I was horrified when I saw all my campaigns disappear I thought my 1200h of flight time had all disappeared... But no, all was there. My fix, if you decide to try it, should not have any impact on your logbook. Regardless, backup backup backup.

I'm guessing the schedule Bignewy gave is for "regular" patches, it does not necessarily mean "no hotfix". Note that it could also mean something big is on the horizon !!! (or the team is taking some holidays, or doing double dose of QA, or going on strike ... ) In the meantime, feel free to grab my me_campaigns.lua from just a few posts above, it should work around the issue (or not, caveat emptor) until a proper fix is provided. Or roll back to stable (you said it, beta !). Cheers

Anytime. Happy to help.

I just flew the CE, it's working as intended. So EE only.

OK, answering to myself: the magic switch works because it does not call the same function and the directories are a bit different : ***** BuzzLog: in refreshCampaigns, calling loadDir with campaignDir C:/Users/Windows/Saved Games/DCS/Missions/Campaigns/en/ vs ***** BuzzLog: in onListModulsChange, calling loadDir with item.dir C:/Users/Windows/Saved Games/DCS/Missions/Campaigns/en No idea why the paths are not the same but this explains why the campaigns magically reappear. However on mission end, it is similar to the first call so the EndMission button will not work (lol, my curse ). @Flappie : This is my fix in me_campaigns.lua, around line 338. It's not pretty, I'm not proud of it, I would really prefer to fix the root cause, but it gets the job done. local fullName -- BuzzLine's protection against trailing '/' that causes mismatch between campaignsByPath and game.campaign read from logbook -- note : it's a poor man's os.path.join(dirName,f) but I don't know if we have better if string.sub(dirName,-1)=='/' then fullName = dirName .. f else fullName = dirName .. '/' .. f end So, I'm attaching my modded version below. Drop in the main DCS directory DCSWorld\MissionEditor\modules , overwrite existing file. I have no idea why the issue popped up, why this trailing slash appeared, why now, etc. Also, I don't work for ED so use at your own risks, etc. I just hope this helps people enjoy DCS and their campaigns until a proper fix is found and pushed. Cheers, Buzz me_campaign.lua