Amarok_73

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?

Quite impressive I'd say...

Interesting. What MOOSE class do You use to manage the targets detection by the George?

So You confirm my colleague observations who also was using the Steam Deck and had to stop it to be able to fly the Apache.

Sorry for delay, here's the track file. First I am showing how it works without live CP/G, then, after he connect, and activate TADS, I am using the Greyscale again, this time receiving permanently the TADS symbology on IHADSS. IHADSS Grayscale issue.trk

Yeah, but it will take a moment, as my CP/G already gone to sleep, and the track from our recent session where I checked it is 156 MB large.

@NeedzWD40 Ok, I've tested it and it seems, that this happens only with live CP/G on board.

I am pretty sure that if I'll use this option again, the callibration symbology appears, then pressing it to disable it the described above TADS symbology reappears. I am not at home now, so if I'll return I'll recheck it though.

Yes, there...

...and I can't get the propper symbology on IHADSS, instead I have the TADS crosshair and FOV corners in it. Is it bugged or there's some trick I don't know to get the normal symbology back?

Something like this for instance. It's showing two messages before the time when the reboot have to be triggered. Then at the time set in RestartAfter variable, he's checking if the number of clients active in the slots is 0, and if so, then he sets the flag "MissionRestart" to true. This way, You're sure, that thie clients will not be "ejected" forcefully at the landing approach, but server will wait unitl all clients will leave to lobby. This script uses the MOOSE framework, so prior to loading it You have to load the MOOSE, then You have to set in ME the trigger for MissionRestart flag, so setting it to true will cause the mission restart. local RestartAfter = 4 * 60 * 60 function RestartMission() env.info("Checking number of active clients...") local ClientNum = SET_CLIENT:New():FilterActive(false):FilterOnce():CountAlive() env.info(ClientNum) if ClientNum == 0 then env.info(">>>> REBOOT:Restarting the mission.") MESSAGE:New("Time to say goodbye...", 60, "EOM", true):ToAll() trigger.action.setUserFlag("MissionRestart", true) else SchReboot = TIMER:New(RestartMission) SchReboot:Start(20) env.info(">>>> REBOOT:Scheduled next run") end end function Reminder1() MESSAGE:New("Mission end in 30 minutes, time to RTB.", 60, "INFO", false):ToAll() end function Reminder2() MESSAGE:New("Mission end in 5 minutes, time to RTB.", 60, "INFO", false):ToAll() end local SchReminder1 = TIMER:New(Reminder1) SchReminder1:Start(RestartAfter - (30 * 60)) local SchReminder2 = TIMER:New(Reminder2) SchReminder2:Start(RestartAfter - (5 * 60)) env.info(">>>> REBOOT:Scheduling first run after " .. RestartAfter .. " seconds.") local SchReboot = TIMER:New(RestartMission) SchReboot:Start(RestartAfter) env.info(">>>> REBOOT:Scheduled first run")

Five years later I still wonder how to move multiple groups without getting pissed every time I'll miss click trying to select another group. Does anybody know if there's any list of unpublished features for ME like the one where You can use Alt+Click to show the list of overlapping units? Perhaps there is already way to select multiple groups/units with mouse drag, but it wasn't mentioned anywhere officially yet?

Is the message from the subject showing in the log something I should be worried about? Is it something that can be related to significantly increased number of CTDs caused by module edterrain4.dll i notice recently?

Thank You very much @Zabuzard for all the help. All the best in 2024!

Taking in account, how much effort and luck it required to get through Fleet Defender F-18s circling around like vultures, waiting for the 37 to appear on RWR, shoot the "15s" and pray to live long enough to give'em chance to try to get through the defending CIWS of escort ships and carrier itself, while being the only one devoted to Viggen on the server? Naaah, I don't feel it was as easy job as it seems at glance. Anyway, being familiar with lua scripting, I'd be grateful and more than happy to get a hint if it is possible then if so, how to tweak RBs just a little just for use at least in missions played on our squadron's server.

About two patches ago I saw a some post about significantly degraded anti-ship weaponry efficiency, which was probably taken down because it revealed that all this "improving the realism of weapons" is some kind of grim joke. So naively hoping that issues with anti-ship missiles described in that post was just some bugs possibly repaired in more recent patches, I did some tests and... well.. Rezky requires 3 RB-15s, Moscow needs over 8, while after following two salvos the next ones don't even try to reach the target, getting lost somewhere along the way in the test scenario... After several more attempts, I gave up, and didn't even tried to check what fractions of percents I can cause damage with my once-beloved-now-just-patheticaly-puny RB-15s to the Kuznietsov. Yeah... I remember when it was explained to me on this subforum that in "real" Viggens attacks fleets in hordes counting dozens of planes, but the DCS reality is unfortunately not so colorful, and finding two wingmen ready to participate in antiship crusaide always was quite the challenge but possible and now such attempt can only trigger empty laughter in enemies in place of hitherto alert and anxiety. Sad to see what was pretty accurately and vividly was described by the @Glowingheat that Viggen becomes "the ugly child, unloved and uncared for, while the new baby (F-14) gets all the toys, and the new pregnancy (F-4) gets all the attention". Yeah, I can hear the HB fanboys scream "shut up and go buy F-4!" - unfortunately I did it already. XD RB-15 no-more-fun.trk

Definitely thread worth following if there's chance to get the answers on that questions. Thank's @FalcoGer for a neat synthesis of my doubts and questions