moggel

Trying to understand how the DLNK DED page really works but the manual is not revealing much and experiments so far hasn't delivered a clear and reliable pattern either. So, sometimes when I drop a bunch of singleton Vipers on a map, and they end up with different series of Datalink ids (DED "DLNK", page 3) me and a buddy can just make sure the first two numbers in the first (left) column correspond in each jet, and that each of us set "OWN" to different values (me as "1" and he as "2", or vice versa) . That sometimes makes us show as blue circles with that number in it, on the HSD. But more often than not this procedure doesn't do anything. We both remain green circles on one another's HSDs. Is this system bugged or am I just missing something. Would be great if ED would add more info in the manual for this.

I recently discovered this lovely Mod. The light towers doesn't seem to actually be lit during the dark hours. According to the website they should be lit up between 2200 and 0600. Do I need to do something other than just placing them?

Yes. Tankers and AWACS

How do you set this thing up, as mission author? Is it supposed to sit near a SAM site and activate when incoming HARM is detected, or should it be positioned far out with the intention of transmitting a fake radar signal? The latter seems unlikely, from what I have seen in experiments (it never shows on my RWR, or on the HAD page). A bit weird there's no info whatsoever on how to use this.

I don't if it's just me doing some solo/ad-hoc flying but in MP combat ops we're 25-30ppl so there's usually a takeoff slot time to wait for. GND power allows me to power up all systems, including my Braun shaving machine, while I wait. As my group gets close to taxi time we fire up the engines.

Come to think of it, I often turn on all of the switches to ON as I wait for GND power to get connected. That might be it. Will experiment and see if there's a difference. Thanks again!

So, this happened again yesterday and it took me a while before I remembered @Moonshine's solution but that was it! The "DLNK" GPS TIME was OFF and switching it ON immediately gave me Timber again. So, as this happens regularly to me I suspect I might be doing something in the wrong order or I am omitting some step in my cold starts but I can't figure out what it might be. This is basically what my cold start looks like: BATTERY ON, then connect ground power and then MAIN PWR ON INS to STOR HDG then all avionics panel switched switches to ON (MIDS LVT knob to ON) FCR and RADAR ALT on, relevant cheek stations ON Lights set, IFF to stand by (expected departure squawk punched in), RWR on, SEARCH on Altimeter to ELEC, stand-by attitude indicator uncaged Countermeasures (in STDBY) powered and on. ECM on (if installed) ...wait for alignment to reach 10 (1.6/10)... INS to NAV HMD alignment Possible rearming and setting up weapons, if time allows I wrote this from memory so I might have missed something but this is pretty much what it looks like and more often than not this, apparently, result in my GPS TIME being OFF for some reason. Any clues on why that is? Also, is anyone else seeing this regularly? The non-deterministic nature of this issue (same cold start result in different results; usually I do get DL but very often not) makes me suspect there's some timing aspect at play here. Maybe I do something too fast, or too slow?

No, I always do a stored alignment.

Very, very often these days I end up with no datalink when cold starting and I can't figure out why. All the switches are on, INS is ran to full and I never ever rearm or start rolling until alignment is done. Has anyone else seen this? Am I missing some detail I need to be aware of?

Just confirming I can reproduce this. Please fix ED.

So, what you're saying is that older / less sophisticated systems, like SA-2, SA-5, SA-6 etc, that are not active, are actually safer in this regard than more modern ones, like SA-10+, Patriot etc.?

As NASAMs are AMRAAMs fired from the ground, that actually makes sense, and tells me the AMRAAM is way better modeled than larger SAM missiles. Unless someone can tell me they have indeed seen RED flights getting shot down by their own SA-X systems. Even older stuff, like an SA-2 or SA-5 seems to be flawless in this respect.

I'm not sure this forum is the right placer for this one but I couldn't find a more suitable one (mods, please move as appropriate). Seeing how VKS are very reluctant to fly in Ukraine is reportedly, at least in part, rooted in the the very high risk of being shot down by their own GBADs, and how even sofisticated SAM systems, like Patriot, have indeed caused blue-on-blue (2 allied aircraft was mistakenly shot down in the Iraq war, killing three crew members, and a third narrowly escaped that same fate), I feel the DCS implementation of GBAD systems are far too precise. I have yet to see a SAM system shoot down a friendly. At the same time, any pilot who locks up a bandit engaged in a scrap with a friendly, and shoots a fox 3 at it, risk causing a BoB, as the AMRAAM might simply switch target during flight. This never seems to happen with SAM missile, not even really unsofisticated ones. Over all, skilled SAM crews (AI) should simply refrain from shooting at bandits that share a volume of airspace with friendlies, to avoid friendly fire. Less skilled AI might take such a shot but there should be a high risk doing so. Or am I missing something?

As I enter a TIME DELTA all Waypoint's TOS data gets updated accordingly, but the DELTA value itself, in TIME DED, is back at 00:00:00 after I dobber out of TIME and then pick TIME again on the ICP. That means I need to make a note what DELTA is currently active as there's no way to get that information. Is that a bug or just a design flaw in the actual Block50?

I agree, but I have successfully tossed WCMD CBUs before with better accuracy than CBUs without WCMD so if that's the case ED must've nerfed the 103 and 105s

I do have the latest hot fix and CBU-105 falls short consistently. I'll double check on multiple maps. Not that it should matter butt we've heard that before so ...

I lofted all the time prior to 2.8 and never had any problems hitting TGT but in 2.8 the bombs falls short every time. I usually loft CBS with WCMD but they too fall short. Anyone else seen this?

I'm going nuts over this one. Every now and then I get into missions where the author have set the Viper up for a hot start. What happens is it immediately starts rolling and accelerating, even when my throttle is set to idle (and the virtual in-cockpit rendition of the throttle seems to match that). I have set the v-cockpit to sync with my hardware's position so I'm not sure what can be the cause of this. I also seem to be the only one in my group with this issue. Any hints are welcome

Just like with group sensors and engagement ranges, please add a third option to toggle group routes ON/OFF. The map gets very cluttered even with medium complex missions. Also, like with ranges, when routes are "OFF", they should still be rendered when a group is selected

Yeh, I tested both middle and forward positions (aft is "barrage", needs MAN, if I remember it right). Are you able to activate when XMIT is CENTER or FWD, C/M is SEMI/AUTO and the system is energized, by going CMS AFT? I have org buddies that are seeing what I am seeing ...

With the new patch the normal way to activate the ECM seems no longer to work. I energize the ECM pod, ensure countermeasures is set to SEMI or AUTO, activate all the modules and then go CMS aft to set the pod in active mode (waiting for spikes) but the "E" remains lit and the little "A" remains dimmed, suggesting it's not working. Did this change? I can't see anything suggesting it's changed in the log ...

Please make all non-player agents, such as GMs, TCs, JTACs and Observer slots, work as units and groups. This would allow mission/campaign authors the ability to build menus and send messages to Game Masters (etc) that aren't available to players. That would allow for greatly improved gameplay. Thanks

Thanks, but the problem is the lua context doesn't recognize the GetDevice() method. My question was how to enable it. Do you have an example on how you set up your export to enable device querying?

Hi all, seasoned coder since 35+ years but a newb to LUA and DCS scripting. For my current hobby project I need to get the state of cockpit switches (external lights) and my "research" has lead me to understand I need the GetDevice() function. However, when I use that function in my own .lua file I get this in the log ... attempt to call global 'GetDevice' (a nil value) ... implying GetDevice is not available. What do I need to do to enable it? My .lua file was loaded on the MISSION START event, after MOOSE and MIST libraries. Thanks

Seems the reason was I was in A-A master mode. So, even if the TGP is slaved to the HTS I cannot slew it unless I am in A-G mode. Not sure if that's how the real system works but it doesn't make much sense to me. Can someone explained this design?