Redglyph

I think the general idea is the same as here: https://forums.eagle.ru/showthread.php?p=2466551 1) You could have a continuous trigger checking for this button with a condition X:COCKPIT ARGUMENT IN RANGE, for that you need the "argument" which you can find in this file: Mods\aircraft\SpitfireLFMkIX\Cockpit\Scripts\clickabledata.lua The easiest is usually to hover your mouse, wait for the tooltip then search it in the file above. Here with the Spitfire it's slightly more complicated, the tooltip content is indirected from another file, so you can check your joystick input file, or the default one, or simply seach in the clickabledata.lua. In this case, it must be this line: elements["RCTRL_D"] = radio_channel_button(_("Cockpit.SpitfireLFMkIX.radio_d"), devices.VHF_RADIO, device_commands.Button_5, 119) So you must trigger on this argument 119, I haven't tested but it looks like the value should be 1. Obviously you need to temporarily disable this trigger once it fired, with a separate flag. 2) To perform the action of opening the communication menu, you must perform a X:COCKPIT PERFORM CLICKABLE ACTION, there's some info on that in the DCS manual, for ex. pg 93-99, it's worth the look to know what's possible. Check also this thread. Not sure how to find the command ID, what they say in the manual about that doesn't seem to work anymore (setting OPTIONS_ADD_COMMAND_CODES_TO_TOOLTIP to true). Here it seems all the aircraft are modelled on the P-51 for this "push-to-talk" command, and on the Mustang there is a "elements["pnt_44"] = default_button(_("Microphone On"),devices.CPT_MECH,device_commands.Button_1,44)", so perhaps it's simply 3001? Otherwise you'll have to search this one. :) Not sure about the device either. Just a few hints, but I hope it'll help a bit.

Have you tried to do a DCS repair? Seems like an installation problem more than a mission bug. It's not you, this is a bug in DCS 2.0.4, it's been like that for quite a while. Once you get on the runway it will generally say "unable to clear for take-off", then immediately "you are clear to take off", but they won't respond to the radio for this specific request.

Yep, that would have been my next try if the other wasn't working, I guess they're both equivalent. In 2.0.4 sometimes it's the only way, ATC is not working well at all.

I reported something somewhat similar in another thread for mission 7. The wingmen seem to stay put if I ask for clearance too early. The cue here is that the tower doesn't respond and I have to ask multiple times, that's usually the sign it won't work. Waiting for a little bit, for example that the initial dialogue is finished, and only then requesting clearance gets an immediate response, and the wingmen start their engines and follow later. So yes, there seems to be some link with ATC or the way the initialization is still undergoing.

I had a brief look, it must be possible but requires quite a few modifications in multiple files, I don't think I want to commit to that right now. Usually people won't switch cockpits too often anyway. What I wonder is how this will organized once there are several theatres in the same version. For example, the note with the radio and RSBN channels will have to be a kneeboard. Well, even the kneeboard will have to be configurable...

Apparently, it seems to work if I wait until the first dialogue is finished, then call ATC and request start-up. The response is immediate. The wingmen don't light their headlights though, that's disturbing but not a bad omen ;)

Simply launch any other mission first in DCS, or this one from the mission menu. Then launch it again - without leaving DCS in-between, the 2nd time it will be fine (most of the time, anyway). Or you can launch it two times from the campaign, you'll simply have a lower success rate unless you edit your logbook. Not a big deal :) Make sure you have the latest version of DCS.

Makes sense, that's how I saw it; I haven't found more details about these but it's worth keeping those rules in mind to avoid bad surprises :D

Yeah, I can't make mission 07 start, I've tried different things but no luck so far. The re-do trick is not working in this case. ATC is very slow to respond for the start-up, and then it doesn't respond anymore (only once I proceed to taxiing, taking off and so on). So if the AI depends on that, which seems to be the case, it's a problem. I had the same in the Red Flag missions, some aircraft would just remain grounded and ATC wouldn't respond.

DCS 1.5.5.60565.216 Here is a track file, take-off at 30", flame-out at 2'19", at 1440 km/h TAS (1400 IAS), so Mach 1.18. This is at 715 m ASL, no wind, 15°C. Not the smoothest take-off, I had to put a lot of right rudder for some reason. It's comparable with what I observe in DCS 2.0.4, though the altitude there is of course higher. Note that the table in pg 31 shows a limitation at 1300 km/h or Mach 2.05. I'm not too sure what to make of it, if that's the worst of the two, it means 1300 km/h IAS below 30 kft-ish (so about 1300 km/h TAS at sea level), then Mach 2.05 above. The confusion may come from that, I need to get more information about that. Something weird though, is the debriefing shows an engine shutdown at the very beginning, before actually taking off. And an engine start at the end. I've often seen those weird events in the case of the Mig-21Bis, there are usually a bunch of engine shutdown/engine start, when nothing really happened during the flight. EDIT: the replay is a little weird even when not changing the view, but it still works (at least for me, take-off was very bad when I replayed it but we still see the flame-out). Mig21bis.flameout.trk SARPP_DATA_2017_00_03_11_43.txt

I've finally created a thread here, with a link to the two missions I've spotted so far, if I see other ones I'll add them to the list. Hopefully that'll help pinpoint the problem. In the case of the other mission, blocked AI is not even in the same group, and there is no condition, nothing special for this AI group, it should simply start right away. It shouldn't be too hard to find, just requires some time and digging with a good debugger.

Yeah, it can be annoying, I have a few fixes I have to restore as well here and there. You could copy the whole campaign in your %USERPROFILE%, and only bother when there's an update in those missions. Or copy back what was moved to the latest <DCS install dir>\_backup.* by the DCS updater. Have you sent them your fixes? They'd probably be happy to integrate them.

Files uploaded in the proper user files section. :)

Since I saw the same problem in OPF and that it doesn't seem on their radar anymore, I've finally posted a report here: https://forums.eagle.ru/showthread.php?p=3004761

DCS 1.5.5.60565.216 For some missions, if the mission is started immediately after launching DCS, the AI fails to start some of the aircraft. If the mission is started after anything else (same mission, other mission or track file), the AI starts normally most of the time. I've seen two occurrences of this very nasty bug, it seems independent of the module so I'm reporting the links here to centralize, please add other cases if detected, preferably with track file. Tracks provided in the links below. Play it first after launching DCS, then a second time (or more). 1) In the M-2000C campaign, mission 9 Saxon's lights should be visible after first dialog over the radio, after a few seconds. 2) In the OPF campaign, mission 6 Wingmen's A-10C lights should be visible at about 23:26:39 (aircraft clock). Note: Funny thing, we also see the mouse bug when playing the tracks, the mouse cursor jumps after a few seconds of inactivity. When playing the mission, it fails to disappear, I suppose it's a temporary work-around. Note 2: see also this post, possible work-around / clues about what is wrong. I haven't tested it yet.

DCS 1.5.5.60565.216 Mission 06 suffers from the same DCS bug as mission 9 of the Mirage 2000C campaign, the flight will not start if the mission is run immediately after launching DCS. If you play any other mission of track file before, then there are good chances the mission will start correctly. I have included a track file to expose this problem in this campaign, but I'm not sure people can play it without the licence. If the flight does not light the taxi headlights at about 23h26'39", it won't start at all. It will remain grounded - to be honest I haven't taken off to check this out, given the bug is obviously there. Other missions could also suffer from this bug, I have no idea what triggers this but it looks like an uninitialized entity in the DCS code. Hopefully with two track files ED will be able to deter it more easily. Temporary work-around: play a few seconds of the track file (or run anything, really) before starting the mission. Sometimes it doesn't work but it's rare. EDIT I realize I'm using a fix for the A-10C cockpit mouse clicks. I don't think it will impact the track replay, hopefully the mouse clicks are not recorded but the changes in cockpit argument values are (or even further down the chain). If the track does look funny, let me know :D OPF_mission06.ko.trk

Any estimation on when the 32145 - LUA PREDICATE bug will be solved? Lost quite some time today before finding this...

Great news! I was really looking forward to this one :)

There's a recent video about it:

Didn't get any error in the logs. Communication is fine, I'm sure that part was just me. I probably used the communication menu instead of using the push to talk to set the R-863 radio communication when I had the correct "Skala", then tried the others with push-to-talk but 131 MHz instead of 127.5, that's why I'd set them all on the same frequency, but perhaps there's a problem when we do that.

Aha! Looking again with the ME, in other missions, I see why. :D Actually there are several heliports "skala", one at 131 MHz, the others at 127.5, that explains why we see several on the ATC menu. I couldn't see them in mission 2 because they're under another icon on the map. I suppose there isn't another way of doing that, for now. Interesting! That doesn't tell why they are not always answering though, perhaps it's a similar problem than in DCS 2.0, in which the ATC never gives take-off clearance anymore. Or perhaps I did something wrong. EDIT Now it's responding, I probably did something wrong. Perhaps all 3 FARPs could have the same frequency, or some could be renamed "skala (backup)" to avoid confusion and searching for the correct one?

(DCS 1.5.5.60565.216) I've got a strange behaviour with the outpost ATCs. 1) As you can see in the screenshot some are listed each 2 or 3 times. 2) Also, they're not always responding, I suppose there is a shorter distance than regular airfields but even when I'm close, sometimes I can't get any answer. For example in mission 2 I couldn't get Skala to give the permission to start, even though the radio was correctly set (I could communicate with other outposts), and I tried each of the 3 menu entries. It doesn't break the mission, I can just ignore this, but I was wondering whether this was a problem with helicopter custom airfields in DCS? When I edit mission 1 or 2, I see - in the briefing Player – “103” Java – “Skala” (131.0 MHz) Tskhinvali – “Shpora” (135.0 MHz) Gromi – “Podkova” (138.0 MHz) Leningor – “Vetka” (140.0 MHz) - when clicking on the outpost Skala, frequency = 127.5 AM Shpora, for example, is set at 135.0, as expected.

Thanks! Uploaded in first post, let me know if there's anything amiss. Hope it helps.

Unfortunately this drop-down feature never made it to the Mig-21Bis. Instead you have to tick the "Custom cockpit", so the same idea is there. You can also select the language, it's a separate settings. They're just the existing settings, the mod does not change that. Now that you mention it though... it should be possible to modify that as well.

Hey everyone! Is that OK for ED and Leatherneck Simulations if I upload the fixed training missions and quick missions in the DCS user files section? I'm aware I can't do that without a specific permission due to licencing terms, so I don't want to upset anyone. And I know anybody can do this in the ME but still, it's a bit tedious, so I thought it'd be easier if it was done once and for all. Archive is there, ready and waiting. For now it's mostly the fix for the radio, I may have a look at the cold start training mission if I have the time (minor, broken triggers and flow logic). EDIT Mig-21bis.quick_training.01.zip: training & quick missions: - radio channels fixed - taxi training: channel is already tuned and dialog asks pilot to contact tower - remark: channel 0 = 124, even though it's "149" on cockpit note. 149 MHz is not accepted, so I left it like that. Mig-21bis.quick_training.01.zip