Amarok_73

This is what image shows. They all circle on holding point, awaiting for the free runway. The problem is that if the airport constantly generates new planes (by purpose, according to the tactical situation), the ones in the air will never have a moment to land, because the game engine seems to set it so when those on the ground start taxing, the runway is set as occupied. So even if the plane on the ground taxing from the farthest end of the airport and it will take him like 5-10 minutes, there's no possiblity to land in meanwhile these planes that are awaiting in holding pattern. Yes, using the Hold Short point and alternate runways as it is in the real life.

I think, some of us (especially mission editors using the scripting) would appreciate if ED would consider optimization of the landing/departing algorithms, so the landing planes would have priority before departing ones, or they would operate based on interleaved slots. And second thing is the taxing planes shouldn't automatically block the possibility for landing, especially when the latter is on final.

ETE is function of your speed and distance. If you're so close as on the screenshot (2.7), then with speed 66 kts you'll do it within 0.0409 hour or 2.45 minutes, what rouded down to single decimal gives 0.0 hours.

@LorenLuke Thanks for this information and confirmation of my suspicion.

I've had feelings that I have confirmed yesterday, that this part is not always work as supposed to. Most of the times, it is like, I am pressing second (and third and even fourth) time the POINT TRACK, but small cross is stuck to the center of the larger one. Can anyone confirm my observation? Is it feature, or bug?

Hi @Guille H. Mono, thanks for the answer but I saw already this video and to be strict, while I am easy with modes, it's still unclear to me what are functional differences between submodes, all these little crosses, diamonds, and smaller or bigger frames related related to them. Also I have noticed some inconsistency (?), that I couldn't find the explanation in the documentation related to when the offset cross (or more general pointer) can be moved, vs when it is fixed to the center of the MMS image.

Hello, I would really appreciate if anyone with such knowledge would be so nice to summarize for me shortly, in what scenarios which MMS mode/submode should be employed.

For me, who switched from the old and wonderful, but worn-out G940 to Virpil, the Fade In/Fade Out option known from Polychop helicopters is the only one that does not cause constant irritation at the inability to precisely trim the helicopter without struggling with the joystick. But my colleagues who fly on "springs" also highly praise this trim method. Therefore, I join the request to consider and positively respond to the request to make this trim method available not only in the Apache, but also in other helicopters such as Ka-50, Mi-8, Mi-24, UH-1 and the upcoming Chinook. And anticipating possible inquiries, I use the Virpil MongoosT base for the joystick, the one with clutches, which for someone used to FFB are quite a miserable and rather useless gadget, and after weeks of getting used to this mechanism, I finally gave up and settled for flying with a spring-centered joystick.

I'd suggest using the DCS-DTC. It's not instant, but still saves pleny of clicks. https://github.com/the-paid-actor/dcs-dtc/releases

Good old RTFM is still in use... ;-D null

Yes, it was short after departure. I thought it may be it, but that would mean Heatblur REALLY did his lessons well... Surprisingly and unbelievably well...

Has anyone else observed, that when flying supersonic, at some point, the fuel counter starts to increase it's numbers?

My friend and I both have FFB joysticks, and believe me, I have a lot of fun in the rear cockpit listening to my G940 beat the balls of the guy in the front with the Rhino.

Meaning, using this checkbox I can disable default "all-hearing" radio, and use the additionally defined in sound settings radios, to hear specific frequencies only?

Witchcraft seems to be abandoned, but in meanwhile there appeared some other projects offering the possiblity to debug Lua and real time programming. For me the best one is https://github.com/nielsvaes/dcs_code_injector

Come on ED, it's here, You just need to pick it up!

Sure, I'm available almost every evening and I usually practice these topics.

The DL switch is used to select the radio that will be used to exchange data via Datalink, not a preset. The settings of this radio can come from a preset or manual settings. If L1, L2 or L3, which are network identifiers, are not visible on the EUFD, next to the radio you selected using the DL rocker, it means that the setup required to support Datalink is not active on this radio. EDIT: It would be way easier to explain in some live training session.

Think of a preset as a template, containing predefined settings for all types of radio (except HF, which is not implemented yet), as well as a data link, the parameters of which can be changed as needed. It is up to you to decide which of the frequencies available in a given preset you will use to assign to the selected radio types, i.e. you can choose that Victor (VHF) and FM1 radios should have the frequency from the preset you have called "Kitten", Uniform (UHF) from the preset "Auntie", and FM2 from the "Kebab" preset. You confirm the frequency selection by pressing the B5 button (the one labeled "SC" - single channel). In the Datalink settings itself, it is important that the "Originator ID" is unique for each of the helicopters taking part in the mission and this is probably the only parameter that determines the occurrence of possible errors in Datalink operation. The rest of the settings, such as Callsign (C/S) or preset names, are simply decorations that do not affect the operation of Datalink itself. As for the values that can be entered in "Originator ID", these are values from the range (if I remember correctly) 0-39, A-Z, 1A-1Z, 2A-2Z or 3A-3I, which gives a total of 127 available identifiers. And of course, it is best to arrange the preset settings in such a way that they make using them as simple as possible depending on the phase of the mission, i.e., for example, you have a separate preset for the departure airport where the Victor frequency is set to tower, a separate one for the arrival airport with the same radio set to tower frequency of the arrival airport, but in all presets you have the same Uniform frequency, because you communicate with the HQ on it, and FM1 for communication within the package, and a separate preset with FM2 frequency specific to JTAC, whose services you may need to use during the mission . But of course it can be planned completely differently and from what I know, pilots usually spend a lot of time planning the so-called "communication ladder", and thus also setting presets, which are later loaded into the helicopter's computer using DTC. This is in a very general outline and probably not entirely consistent with real-life practice, and @NeedzWD40 would probably have more acurate and detailed information, but for me this approach is enough to sort out this topic.

I remember there was the change proposal to make it possible to set the weather conditions and time at the mission load on the server, but I don't think it was escalated any further.

Hello, Since yesterday, after I tried to update the SRS with updater downloaded from the SRS Github, I receive warnings from NOD32 related to this program. Does anybody knows if this is false-positive, and what causes this issue?

Hello, What is supposed to do the Radio Checkbox in the Airplane Group properties, and why frequency for the Client planes is not editable?

Now it's feels softer in position correction, but still requires from a pilot a bit too much attention to get him into HH regime.

null

Hello, If it wasn't yet considered, would it be possible, to existing Scripting API methods toAll, toCoalition, toGroup add another method like toClient for showing marker for specific Client?