Redglyph

I'll take you up on it ;) If you have problems with the editing, don't hesitate to post the log ... somewhere, here? If another thread, you can ping me otherwise I probably won't see it. A problem in logbook.lua may prevent DCS from starting (or cause it to freeze when you open the campaign screen). In any event of error you can parse the session log file to find out what went wrong, like here (pg 7 in this thread).

I had a non-related bug that broke any campaign progression, so I entered the results manually into the logbook, it's no trouble explaing how. Yes, it's a little bit like cheating... but needs must ;) The log is in this file: %USERPROFILE%\Saved Games\DCS.openbeta\MissionEditor\logbook.lua (%userprofile% being c:\users\<user name>) 1) MAKE A BACKUP of this file! ;) 2) Find the campaign part, in this case, search for the line with: ["campaign"] = "./Mods/aircraft/M-2000C/Missions/Campaigns/M-2000C Campaign.cmp", 3) Included in the ["history"] part are the missions you have flown, the pain is that they are not sorted out. The last one - the next to come, is incomplete, for ex if you have to fly mission 5: ... [6] = { ["stage"] = 5, ["mission"] = "Mission 05 FINAL.miz", }, -- end of [6] [5] = { ["datetime"] = "12/07/16 23:37:17", ["agKills"] = 0, ["result"] = 100, ["aaKills"] = 0, ["deathsCount"] = 0, ["stage"] = 4, ["mission"] = "Mission 04 FINAL.miz", }, -- end of [5] ... Note that if you failed a mission, for ex. mission 5, you would have one entry with ["stage"]=5, ["result"]=0 ... 50, and one entry [i+1] incomplete, still with stage 5, stating you have to fly it again (or it could even be stage 4 if your score is less than 50, meaning you regressed back one mission in the campaign). 4) If you want to bypass mission 05, just add the missing info to make it look like it has succeeded (the datetime isn't really checked for now): [6] = { ["datetime"] = "12/07/16 23:37:17", ["agKills"] = 0, ["result"] = 100, ["aaKills"] = 0, ["deathsCount"] = 0, ["stage"] = 5, ["mission"] = "Mission 05 FINAL.miz", }, -- end of [6] [5] = { ["datetime"] = "12/07/16 23:37:17", ["agKills"] = 0, ["result"] = 100, ["aaKills"] = 0, ["deathsCount"] = 0, ["stage"] = 4, ["mission"] = "Mission 04 FINAL.miz", }, -- end of [5] 5) Create the stub for the next mission to run, here mission 6, making sure the .miz filename is correct by looking into the campaign directory. Don't forget to increase the ["stage"] value: [6] = { ["datetime"] = "12/07/16 23:37:17", ["agKills"] = 0, ["result"] = 100, ["aaKills"] = 0, ["deathsCount"] = 0, ["stage"] = 5, ["mission"] = "Mission 05 FINAL.miz", }, -- end of [6] [5] = { ["datetime"] = "12/07/16 23:37:17", ["agKills"] = 0, ["result"] = 100, ["aaKills"] = 0, ["deathsCount"] = 0, ["stage"] = 4, ["mission"] = "Mission 04 FINAL.miz", }, -- end of [5] [7] = { ["stage"] = 6, ["mission"] = "Mission 06 FINAL.miz", }, -- end of [7] And you should be good! If you have remorses, you can still run the mission later in single mission mode, once bugs have been solved / skills have been honed / ...

Haven't tried, so I'm not sure but I saw posts mentioning similar problems in the campaign. Something to test, one of these days :)

Standing on the bleeding edge of technology hurts, sometimes :D But more seriously, I'm pretty sure everyone is very glad to have those training and campaign missions now and not in a few months! :)

Lots of messages for you ;) Not sure you've seen this one, something else that must have changed since training mission 9 was wroten, might confuse the poor cadet:

Well spotted! I've put a bug report on their bug tracker a while ago, but I don't think they use it anymore. They don't much read the forums either, so...

That's probably a sign it's a good campaign, it uses a lot of features and deters what little bugs may still hide in the dark corners of DCS ;)

Is that specific to the military? I've never seen that in GA, for example, all references I've read on IFR, or exercices I've done, always mention radials in degrees (some omit the degree unit). And well, other radial-related missions in DCS. Or BMS. Even searching for TACAN radial, that's what I find. For a runway, it's of course another story. Anyway, I don't care that much, as long as the system used is clear from the start, it should work :)

Do you still have this problem? For my part, I finally found out in the log file (%USERPROFILE%\Saved Games\DCS.openbeta\Logs\dcs.log) that error: 00054.658 ERROR Lua::Config: Call error onShowMainInterface:[string "./MissionEditor/modules/me_logbook.lua"]:1302: attempt to perform arithmetic on field 'faaKills' (a nil value) stack traceback: [C]: ? [string "./MissionEditor/modules/me_logbook.lua"]:1302: in function 'updateUserStatistics' [string "./MissionEditor/modules/me_debriefing.lua"]:326: in function 'load' [string "./MissionEditor/modules/me_debriefing.lua"]:257: in function 'show' [string "./MissionEditor/MissionEditor.lua"]:709: in function 'openReturnScreen' [string "./MissionEditor/MissionEditor.lua"]:732: in function <[string "./MissionEditor/MissionEditor.lua"]:723>. To solve it, I had to add the missing value, which had disappeared for some obscure reason. So if someone has a weird problem like DCS not registering the missions properly, not branching to the next mission correctly, ..., search for "logbook" in this log file, to make sure it's correct. If you find a similar error message, post the details in the appropriate "DCS World 1.5 & 2.0 Open Alpha" error sub-forum, so someone can help you fix it. DCS is not resistant at all regarding any problem in the logbook.lua. And sorry for spamming your thread, baltic_dragon :)

Looks like a strange DCS issue, indeed. Probably due to a change for VR, it's not the first time those tooltips behave.

Glad it helped :) It can be a little distressing to see the ailerons go completely the wrong way ;) I hope they address that at some point. But as Art-J said in the other thread, since it goes away when taxiing, and does not really do any harm, I'm not sure we'll see a fix anytime soon.

I think the problem comes from DCS or the logbook, not from the campaign. I'll check with another campaign to see if the problem is the same. Here's what I have in the logbook this time, the scores are good. But the problem is DCS is not writing the results, I have to do it manually for some reason (probably linked to this "Mission Editor" choice). And perhaps others have that too, due to something that changed in 1.5.5, or something else in the environment. ["campaign"] = "./Mods/aircraft/M-2000C/Missions/Campaigns/M-2000C Campaign.cmp", ["status"] = "Active", ["history"] = { [1] = { ["datetime"] = "12/04/16 22:55:24", ["agKills"] = 0, ["aaKills"] = 0, ["stage"] = 1, ["deathsCount"] = 0, ["result"] = 100, ["mission"] = "Mission 01 FINAL.miz", }, -- end of [1] [2] = { ["datetime"] = "12/04/16 23:55:24", ["agKills"] = 0, ["aaKills"] = 0, ["stage"] = 2, ["deathsCount"] = 0, ["result"] = 100, ["mission"] = "Mission 02 FINAL.miz", }, -- end of [2] [3] = { ["stage"] = 3, ["mission"] = "Caucasus M03 FINAL.miz", }, -- end of [3] }, -- end of ["history"]

Yep, I have the same problem and I don't know where it's coming from. I have to manually enter the campaign missions in the logbook.lua... I noticed that after each mission, I didn't have a cancel button on the left. Usually I have to press that to come back to the campaign screen and go on to the next mission or leave the campaign menu (which is a bit awkward as a menu system). Now I have "Mission editor" instead, for some reason, I don't know if that's the same for you? I even restarted the campaign from scratch, but it remains stuck to mission 1 again, so I suppose I'll go on editing the logbook by hand. Be careful if you do that, keep a backup!

Did you get any dialogue when flying above Kutaisi? I think this one: "[PLAYER] Colt. Pontiac. Overhead TACAN station in Kutaisi, turning to follow outbound radial 18." The first time I flew close, but not close enough, and nothing triggered after, I also did some flying in circles with the rest of the flight as you did ;) Then I got back and tried to fly more precisely above the TACAN, and sure enough, I got this message out, and it worked from that moment on! EDIT: nevermind, I see your problem is happening before that. Still, I'm leaving my comment here in case someone stumbles on it later. Did you use the F10 menu, once at WP2?

For 2, I actually meant it the other way round ;) The picture is non-ambiguous, the dialogue is: if told to intercept radial 18, pilots will understand 18°, not 180°. IMHO it's always best to mention the degree unit, otherwise for small values there's always a risk of confusion (as in the map when DCS doesn't show whether it's feet or metres, which are both acceptable units in the context). I quickly saw 18° didn't make sense, and the radar showed echoes in the general South direction so it was quickly clarified, not a real problem :)

As I said, it's a known bug. See above.

I just checked the coordinates on the map, but the fireworks were visible enough ;)

Two little pitfalls for mission 2: 1) I'm not sure it's in the normal procedure, I don't think so, the pilot needs to setup his decoy release mode switch, otherwise he won't be able to throw any flare. Since it's not mentioned in the manual (or if it is, I missed it), a "reminder" could avoid many questions ;) 2) "Radial 18". I was confused at first by seeing that after the briefing panel showing radial 180. It's perhaps better to give the radial in degrees and not tens of degrees (isn't that how it's usually done? If not, my mistake).

It's a bit more than "slightly" ;) But yeah, if you select metrics in the general options, then it's a mix of both, and in the ME it's even more confusing because some units must be in meters. It could also be interesting to get mbars on the briefing panel (I know that's handled by DCS), but the conversion is easy enough. I'm always slightly off, though, it's weird. Now that you mention the wind for the METAR, it seems obvious :D Thanks! I've got something else, but I do feel a bit silly. During mission 2, Colt 1-1 says "The shooting takes place 5 miles to the North from the following coordinates: N 42 42 3, E 44 43 15.", and I assumed that was the destination. But it's quite far and I'm not sure how the guy could have spotted fire there, on the other side of the mountains, more than 50 nm away. On the map, a much closer location contains ground units, I suppose it's there, but the coordinates are entirely different. What am I missing with those coordinates? :huh:

OK, thanks! :) Wasn't sure it was specific to the area or a generic term.

Every mission comes with all the necessary information, that is great :) But something caught my eye in mission 2 (I haven't paid attention to that in 1 to be honest), the METAR mentions QNH1009 (1009 mbar), but in the briefing the QNH is 31.10 (in Hg) or 790 Torr which corresponds to 1053 mbar. Though UG27 is the ICAO code for Viziani, so it's the same airfield. I can't interpret most of it anyway so it's probably just me, however it seems it's the METAR of another mission. The "SCT099" is "Scattered clouds at 9,900 feet", but in the briefing it says the base is at 3300 ... ft? or are those meters? I know that DCS has bugs with mixing both imperial and metric units on the map and perhaps in the brief panel, but in this case the conversion doesn't match either. There's a "299/04", but there is no runway 29 so it must be something else, I'm not sure what, it's not temperature and dewpoint either (or 299 in °K?). EDIT: I must set 1045 mbar for the altitude to match what is shown on the map for my aircraft, I've already noticed those discrepencies in 2.0, so this part is probably a DCS issue, or perhaps I misunderstand the data given in the brief panel (I suppose that for this mission the weather is the same for the whole map, since it is version 1.5.x).

Love the campaign so far, dialogues feel real and spontaneous, missions are immersive! :) Silly question, what does ABL stand for? There are of course a bunch of acronyms, like in any domain, but I haven't found this one.

OK, maybe this AI mountain problem will sort itself out, that's what we all hope ;) Another thing that may interest you for the training 9, for the gun K1/K2, has apparently changed (no "K1"/"K2" and the current "K2" should be "S"): https://forums.eagle.ru/showthread.php?p=2971749

:huh: It seems that since I've mapped the slew TDC controls, this problem disappeared. Ah well.

Thanks for the info, spiddx!