Amarok_73

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

I'd like to report issue with TSD showing wrong threats for the ones set to be displayed on MFD. It seems that in this particular test case, SA-19, SA-9 and SA-11 (Group names RSAM31V, RSAM311V and RSAM312V) threats are wrongly shown as SA-6 or not shown at all. AH-64 wrong SAM identification as SA6.trk

As in the post title - ASE autopage option "off" is not usable.

Did I missed something or it's still not possible to lock visually on dead contacts?

So far I can't make George to hover in full stop, and switching to CP/G after doing it personally, I can see the George sooner or later falls down getting into the VRS in meanwhile.

You like it the hard way, that's apparent from above, as there's already in FCR screen, on the left, place where You can see all targets that was found by FCR, and You can pass them to the TG points with one click. Then it's just matter of selecting one from the list and ACQing it with TADS slaved.

All right, we're polishing then what is currently available.

Guys may I ask what method do You use to switch between the FCR contacts and classify visually them on TADS? Using NTR to swtich between them on FCR, then switching to TADS and selecting FCR as ACQ to slave TADS to contact doesn't seems to be the optimal way of doing it, and so far this is the only way I could manage it.

+1