Redglyph

Here is the track file, hopefully that should help them. Due to the limitations of these forums, I had to split the file and rename the 2nd part "mission09.z01" to "mission09.z01.zip", it should be renamed back before attempting to unzip. mission09.zip mission09.z01.zip

You will love this. I just tried once more and it failed to start again. Then I wondered whether it could be failing only the first time the mission is run after booting DCS... I saved the track (easier than doing the start-up every time...) and sure enough, when I play it the first time after launching DCS, the Saxon flight doesn't start (which seems to be the first clue here). If I play it again, they start right away, I can see their head lights, the engine starting, and they begin taxiing. I did it a few times, it's reproducible. Wondering whether it could be an uninitialized flag or similar, I ran another mission first after launching DCS, a mission with another aircraft. But watching the track of mission 9 right after, Saxon was starting. So much for the uninitialized theory, unless you see something I don't. It must be some peculiar bug of DCS where something is wrong the first time. Anyway, it seems that the easiest work-around is launching any other mission before this one.

So that's what I've been doing wrong all this time :D And a 5-word summary in the post, of course ;)

It seems neither of you has read my post, probably just the title :rolleyes: Anyway, it's possible to simply adjust the gain in the .ogg file, for example with a tool like xrecode2. Works perfectly and no need to record them again, I suggest to do that to fix the problem.

DCS 1.5.5.60314.211 The volume of the instructor's voice should be increased, it's very low and inaudible over the engine. It is said that if the user can't hear the instructor, he may turn down the "World" or the "In-Cockpit" volume, but (1) it's not enough even lowering those within acceptable limits, (2) it's not a good idea to change the overall settings and make it worse for other missions and modules when it's possible to simply speak louder. I also tried with the "Hear like helmet" but it's not enough either, the voice volume is simply too low.

It blocked two times with further attempts, then it was fine with three more, and I couldn't find what made a difference so far. I first thought it was ATC, but it's not (though sometimes I get a denial for start-up, taxi or take-off - even when still taxiing for the latter). That's pretty weird, I must do something different when lead doesn't start but no luck finding what. When it happened, I jumped into lead's seat and his engine had not started (or was shut down after). And I didn't check whether Saxon was off or not, shame.

Wasn't that one selected for the theme, finally? :(

Thanks! :)

Yes, less work for you with the new kneeboard :)

It's very surprising, takes off very quickly, but not easy to land without scratches on the wings ;) What a beauty! You have to map this control, it's not mapped by default. When you toggle it, the image will just freeze, like in the M-2000C. It's very misleading, hopefully they'll find a better way to switch it off in the future, but in the mean time it'll save you some framerate :)

Yeah, it makes more sense like that, the pilot should do a pre-check, and switch those on when needed :)

I must have missed it before, I was looking at the lead with F2, but probably didn't zoom out enough. I could, but I'm just ignoring them, makes me feel like a rebel ;) I'm talking about the mission kneeboard, or the image on the briefing. Or the pdf, just realized they were there :) Here are the pics. It's not too far off. UPDATE I still have the previous mission 9 of 1.5.5 update 2, since I tried to modify the parking number. The coordinates were correct, did you change something? Erm. I quickly checked mission 1 and there's a difference too. The values I get on the map, by zooming to the maximum and pointing my mouse to the center of the aircraft (and which were matching the briefings before update 3), seem to correspond what is on the new Mirage kneeboard, although the latter are in decimal for the 3rd value and not in second. But they don't match the briefing...

DCS 1.5.5.60314.211 I'm not entirely sure it's a bug, so I'm starting the thread here. The behaviour of the control for the radar elevation antenna has changed in 1.5.5 update 3: - before it was a direct mapping of the elevation, which is fine, - now it's the rate of change of the elevation, which is awkward. Was this intentional? It certainly is less convenient to use, and one would expect it to be a direct mapping on a HOTAS, not the control of the rate of change. The axis direction has been fixed though, now it's not necessary to invert it anymore (which was a one-shot setting and not an annoyance at all, though).

I ran mission 9 again today, after update 3 of 1.5.5, and now there is a vehicle in front of 1-1 that I hadn't noticed before, and it works, the vehicle disappears once the player communicates he's ready and everything is fine. Of course I get the "hold position" annoyance from the ATC as usual, hope this ATC will get some revamp soon ;) Perhaps having to get too close to the lead before he decides to take off happens because I'm not waiting long enough? Ah, I noticed a difference between the starting coordinates on the kneeboard (41 37 66 N, 045 02 78 E) and what is given by the map (41°37'39" N, 45°02'04" E).

I have the same, even with the modified mission 9 that I saved elsewhere. You can see that the radio frequencies are not set at all ("-----"), actually it's off. It is a general M-2000C change where you apparently have to set the UHF and VHF mode switches first, whereas it was already set-up before: - set UHF Mode switch to "M" - set VHF Mode switch to "PoL" I've tested it on mission 1 and it works fine. Just set-up those two switches before switching the battery on, to make sure you don't miss anything. This seems to be done when starting the standard M-2000C missions & quick missions, though. See picture below, sorry if that's a bit dark.

Thanks! That's why I provided temporary alternative parkings that seem to work, in case of doubt. I can check again with today's update, if there is any related change. It's not a real problem, more a suggestion, since it's waiting in earlier missions I thought it was just a simple thing. In most configurations the player won't see the lead passing by anyway :)

Just as a test, I copied the mission file elsewhere and edited it with the ME. I put the player (Pontiac 1-2) and Pontiac 1-1 respectivelly on parking IDs 38 and 39, like the first mission, and it seems to unlock the situation, - Saxon 1-1 moves first, about 23 seconds into the mission (and Arco) - Saxon 1-2 moves second, right after Saxon 1-1 - Pontiac 1-1 moves third, right after Saxon 1-2 This is strange to see Pontiac 1-1 start so early though, obviously he doesn't wait for the alignment to complete ;-) Then, as before, - did the alignment and started the engine - communicated that I was ready to taxi (F10 "Two is ready for taxi") => received a "[PONTIAC 1-1] One. Taxi out." - taxiied to the runway threshold - had to get real close to 1-1 for the sequence to go on - rest of the mission went apparently fine. In conclusion, - it seems some of the parking spots are bugged, - shouldn't Pontiac 1-1 wait for the radio exchange before starting to taxi? - the player has to get very close to the lead for him to move on the runway and take off.

DCS 1.5.5.59992.205 In mission 9, I'm wingman, the other flights and my lead don't start taxiing. Steps: - did the alignment and started the engine - communicated that I was ready to taxi (F10 "Two is ready for taxi") => received a "[PONTIAC 1-1] One. Taxi out." - started taxiing, but apparently 1-1 remains in his box - heard dialogue with 1-1 "[PONTIAC 1-1] Hey, this will be your first combat air patrol since you started your training. Follow my lead, stick close to me and and we will be fine." and following - came to the runway threshold, waited a little longer, 1-1 still in his box - took off, WP1, WP2, WP3 => Pontiac 1-1 and Saxon remained in their parking, didn't move at all. I tried that two times, it seems very reproducible. I don't think I did anything wrong, I haven't encountered this problem in any other previous mission.

Really liked mission 8, and among other things, the ability to give precise commands to the wingman. The standard menu can be somewhat coarse, and not enough when one wants to split the tasks. I spotted this little typo, not terribly important, I'll put it here just in case you're updating this mission :) (two "yuour" i/o "your") There's another funny thing, the two "fi" letters merged into the "fi" symbol, I'm only seeing that now (with an editor) so I'm not sure it's a real problem:

A Flogger... that's certainly not an ordinary idea.

That's weird, with me it was spot on. Was this 420853N/0434428E?

Hello! I tried the very good Quatermaster's English cockpit mod (metric variant), but since it replaces the existing Textures\MiG-21_Cockpit.zip file, it is removed on every update - with an extra 68 MB file to download each time. It's annoying, here's a way to install it permanently - at least, I hope. I'm not entering a debate of the language those cockpits should have. I just find it easier to be able to read the labels in English when learning the aircraft, even though I rather like having it in either the mixed Russian / English of the incomplete translation provided with the module, or pure Russian, for immersion. Quatermaster's mod also has the advantage it fixes the wrong channel numbering on the radio list. Easier than fixing all the frequencies of the existing missions, and other add-on kneeboards already feature the existing channels anyway. In summary, the description.lua (Liveries\Mig-21_CP\custom directory) contains a list of texture elements, in which: the first item is the name expected by the model, it cannot change and tells which texture is to be changed, the third item is the filename, without the .dds, and relative to the path of the description.lua file (you can take files from other directories) the fourth item is false if the file is to be replaced, true if it has to be taken from the MiG-21_Cockpit.zip file in the texture directory. So all I did was to create a description.lua that points to the existing textures, but I had to remove the non-English ones that were still in QM's mod, and point to the English directory provided by Leatherneck. Easy :p Anyway, I hope it helps! :) INSTALLING THE MOD - option I To simplify things, and hopefully without upsetting QM, I gathered just the necessary files in one archive, uploaded on the DCS server. Download the custom package Extract the custom.7z package and replace DCS' Mods\aircraft\MIG-21bis\Liveries\Mig-21_CP\custom directory Or... INSTALLING THE MOD - option II This simply uses the files in QM's mod, and adds the missing description.lua so all the files can be put in the custom directory. Download QM's mod Extract QM's mod a first time, then extract MiG-21_Cockpit.zip (found in the \Mods\aircraft\MiG-21BIS\Textures subdirectory of the extracted archive) copy the textures just extracted from MiG-21_Cockpit.zip, to DCS' Mods\aircraft\MIG-21bis\Liveries\Mig-21_CP\custom directory download the file attached to this post, and extract it copy the description.lua just extracted to DCS' Mods\aircraft\MIG-21bis\Liveries\Mig-21_CP\custom directory, replacing the existing one (keep a copy, just in case) So your DCS' Mods\aircraft\MIG-21bis\Liveries\Mig-21_CP\custom directory should contain (I'm not listing the whole directory): _READ_ME_EN.txt description.lua Mig-21-cockpit_001.tga.dds Mig-21-cockpit_002.bmp.dds [...] When you launch DCS, select the custom livery in the main settings menu, in the "misc" tab for the Mig-21Bis. That should do it. Check the correct installation by running an instant mission or your favourite one, look at the radio channel list, at the warning lights, at the gauges, everything should be in English.

Alrighty, now that I fixed the A-10C I could fix this one, would anyone be interested by such a fix, so that all switches behave the same as other aircraft?

Posted the fix in a new thread, since I'm not sure this one will be read with the "reported" status :) Hope it helps.

I have fixed most of the buttons and knobs that were turning the wrong way or wrapping around. I updated the Excel sheet I made in the original bug post with the results. This is the following file in the DCS installation directory: Mods\aircraft\A-10C\Cockpit\Scripts\clickabledata.lua It has been tested in DCS version 1.5.5.59992.205, but it seems that the current version in alpha 2.0.4.59428.142 is pretty much the same. I haven't tested it in the alpha version! There are a few switches I'm not sure about, like the push/pull convention (see original thread), in circuit breakers and cage/uncage, or other similar switches that don't really behave as the convention, but still in a "familiar way" for better way to put it. If you test it, you can always revert with a repair, but please keep a backup of the original file first. I also hope it won't disturb those who were already more or less familiar with those inconsistencies, but at least now you should know what to expect when clicking on any 3-way button, and not have a bad surprise with those wrapping around! UPDATE: v02 Fixed a few remaining, less important switches. There are still a few, like the IFF test and reply switch/rotating switch combo which turn the wrong way, but I don't think they're used very often. If someone finds something I missed and would like me to give it a try, let me know :) And if someone has the patience to use the fix in a few missions and report whether it's OK or not, that'd be great too. I've tested the result in a simple cold start / runway start mission, and in the "start-up" training mission, and found no problem; it's a pleasure to have something straight and not have to wonder which mouse button to click! Note: The Excel sheet shows which have been changed, check the "status" column. UPDATE: v03 Merged with modifications of DCS 1.5.6.1340.230 / DCS 2.0.5.1648.165. I hope it's integrated at some point to avoid those merges and multiple versions, this is getting awkward... The original file (renamed clickabledata.orig.lua) is in the archive as well, for comparison or restore in case of problem. The mod can be found here: https://www.digitalcombatsimulator.com/en/files/2268038/