Redglyph

Glad you like it, it's mostly the work of Quatermaster, I just re-assembled the necessary files (which allows to switch between cockpits again). Unfortunately it's false advertising on my part - clickabledata.lua is still removed on every update. It's a bug, I proposed a solution to LN for that but got no reply yet, we'll have to wait they tackle this specific ticket :) So just keep a copy of this file, or you'll find it here after an update (last _backup.* directory): <DCS install dir>\_backup.*\Mods\aircraft\MIG-21bis\Cockpit\clickabledata.lua The other texture files are not removed. You may also want to check the fix for the buttons, if you're learning the Mig and want to keep the same left/right mouse click meaning as the other aircraft. It's a great, iconic aircraft, hope you'll have fun with it! For information, it seems the release/beta version has more updates than the alpha 2.0 version, which is older.

Yes, I had all that so the only thing seems to be this status. I don't think I missed a permission to RTB, I was mainly using green channel 3 for Ghost, and red 1 for Chevy 5.

The F-16 manuals, which don't count as many pages, don't really lay flat, and forcing them flat will quickly dislocate some pages after a while. It's probably the same for the A-10C. You should ask them, if they have to print it anyway that shouldn't be a big problem. Unless they need to respect some specifications given by the author.

I've just completed the campaign, and it was a blast! It's really a higher standard than current campaigns provided with other aircraft, some of which being already good to start with. So thanks a lot to Baltic Dragon for creating this, and to Razbam for including it with this fantastic aircraft! The immersion is very good, the interaction between the different groups is well managed and participates to this immersion. Even if that's sometimes difficult with the current AI there wasn't serious issues, nice. The documentation in the briefings and kneeboard pages is also very well done, it's concise, easy to go through during the mission, the story gives an interesting background. There are some inconsistencies but very minor (for instance METAR vs briefing winds / atm. pressure, or some INS coordinates, radial intercept, nothing really problematic). Overall it's very comprehensive. Another neat quality is the progression of the difficulty, it's quite even and that's one of those campaigns that makes you learn the aircraft a little further, bit by bit (if you don't already know it in details from the beginning of course). Or your limitations, I discovered that I'm really bad at defeating Fulcrums and at using INS bombing ;) There might be some difficulties for someone who's using the training and the campaign to learn the Mirage, especially because the documentation is not complete and features have changed after some missions were created, but that's probably part of the learning experience so I don't see that as a real problem. I think a sane approach is to review features required by a mission, when it's not fresh anymore or if it's not entirely clear yet. That's what I did before a few missions and I haven't regretted it.

I had some confusing moments when doing mission 13 as well. Part of it is surely due to my ignorance, still I'll share that here in case it benefits anyone. So, more training is definitely necessary for me, but perhaps others may ask themselves the same questions. Despite those little questions, it was a great mission, like the others, very immersive :) Note: for the kneeboard, I saw a Ghost 3-1 on pg. 5 instead of 2-1, and no QNH though it's easy to find in the "automated" briefing part and convert to mbar.

Some info in this thread, probably more info in Swedish than English, but there's a 497-page manual that should already keep you busy :)

Yeah, same problem here, the radio doesn't receive the signal so far from the emitter. I'm usually following the headings from FLUSH, you can have a look at RF IFG NTTR.pdf (in your campaign directory), pg 9. Note that following all the headings won't work, I think that between FYTTR and FLUSH something is not correct, or needs true North/magnetic conversion.

They're in the same directory, from your main DCS screen select "Mission", but then you have to find the directory. Select any aircraft, and select the up directory ".." until you see the "aircraft", "campaign" and "terrains" level. Then go down "campaign" and you'll find all the missions - campaign and practice. You can probably copy the practice missions in "My mission", so under %USERPROFILE%\Saved Games\DCS.openalpha\Missions to quickly access them.

I don't have much experience in scripting, so I'm not entirely sure how it holds when DCS is updated. Not that I would expect it to break entirely, and after all it's true of any mission. When/if I get something that looks easy to use I'll let you know (and probably post that somewhere in the mods section as well).

Bug still exists on 1.5.5.60565.216, very confusing.

Yeah, the AI is not yet entirely full-proof. I had that helo crash too, but there isn't much that can be done on the user or the mission designer part. You should consider that as an accident, I heard one of the involved pilot had just qualified, and by the skin of his teeth from what they say... they should never have put him on this mission so soon ;) The troops left on the ground is strange :huh: Perhaps they didn't trust the new pilot. Oh, by the way, a few handy links if you haven't them already. You can check the versions here (summary of what changed in the sticky threads), here (history) and here (current versions on the server, sometimes the news are earlier than the server update). And if you see you haven't been proposed to update, you can force it by running the DCS updater (you can also revert to older versions). Not sure this updater works with the Steam version though.

Update to the latest version, 1.5.5.60565, a few trigger problems occurred lately. It's fine with 1.5.5.59992.205, but it should also be fine with the latest :)

Sounds like a bug that was solved recently, which version of DCS are you running?

Yeah, for sure they won't give that any priority if some claim it is a good work-around ;) Even by setting everything down, it's barely audible most of the time. Not sure why others and I have to repeat that so many times. Maybe those who have lowered the other sounds so much can't hear us anymore :D Anyway, I'm happy to provide the corrected ogg files if that helps, it takes a few seconds to do it.

+1 Strange, apparently the only case, but there's an indirect reference in WP2 that shouldn't be there. ["DictKey_subtitle_645"] = "DictKey_subtitle_551", ["DictKey_subtitle_551"] = "[CHEVY 1-1] Two, one. Turning to waypoint 2, we will climb to 15 000 feet, ground speed 340 knots.",

So does it start normally if that's the first mission you run after launching DCS? That bug really had me nonplussed. :huh:

As said multiple times above, this isn't a good solution unfortunately.

To add to what MAD-MM and Sydy said, there are also individual missions that directly start at Rachel in the engagement area, for training purpose.

Yeah sometimes I'm distracted and miss bits of text instructions ;) A repeat should be part of the comm menu, it's probably on the DCS wishlist for a while. It's funny you mention the disappearing text, earlier today I was toying a little bit with a very simple function below, that adds a repeat feature without having to complicate the flow logic. I then set out to check a simpler way to use it in actions than using "DO SCRIPT", and looked at the mission files. I first thought that simply replacing the 'a_out_text_delay_g' in the mission.trig.actions[] with 'showText' would do the trick, but apparently those are not used when running a mission :huh: So it's apparently the part in mission.trigrules that is used both in the ME (to easily get the parms back) and when the mission is running. Weird. Perhaps I'll do a script to modify all the stuff automatically to integrate this repeat feature in any mission post-ME. I'm posting that as-is in case you're interested, as you see it's not finished and I'm not convinced yet it's worth pursuing ;)

Oh, oops. Can I ask a good soul to share mission 12? ... I haven't copied the update before reverting :doh:

I thought those tanks were not mounted on Spitfire Mk IX? http://spitfiresite.com/2010/04/concise-guide-to-spitfire-wing-types.html/2 I see now mention of leading edge fuel tanks in the description of the C wing, in the DCS manual, and I haven't found any reference to such tanks in either Morgan/Shacklady's or Price's books. Besides, those wing tanks usually had capacity for 30-33 gallons, not just 17. So I believe that's either a mistake, or something that should be explained somewhere in the manual, unless I missed it.

pp. 38, there is a remnant of Russian text at the bottom, it's the repetition of the last sentence in English just above. pp. 39 Figure 15 is missing. It's only a legend ;) pp. 79 2nd paragraph, first phrase is repeated a 2nd time "Fuel from the upper tank flows on its own into the lower tank".

A Trojan... perhaps that was a desperate plan B to win the war? :D

If you don't want to wait for a fix: I reverted to 1.5.5.59992, like others, and it's much better :) The only caveat with mission 9 is that you must start any other mission before doing this one in DCS (or start it a first time, exit, and re-start it - without leaving DCS), otherwise some AI groups like Saxon won't start. This will happen no matter which version you are using. The revert was quick, it had to download about 1 GB. It's recommended to keep a backup of your user configuration, though I didn't have any trouble with that, it's here: beta: %USERPROFILE%\Saved Games\DCS.openbeta or if you have the release version: %USERPROFILE%\Saved Games\DCS

Hi Bignewy, any news on that weird bug? I have another shorter track if that makes it easier to debug (it's recorded with DCS 1.5.5.59992). Saxon 01 is the AI group of 2 Tornado GR4s parked next to the player's aircraft. If you play the track in DCS before doing anything else, you will see Saxon is not starting. If you play it a 2nd time, or after any mission / track, you will see Saxon start (their taxi lights are visible after a few seconds in front of the player's aircraft). This looks like a strange initialization bug, there is no condition on this AI group, it's happening to other groups as well. mission09.03.ko.trk