Yeti42

I'm running a 42' 4k TV with HDR and can see out to beyond 10 miles, twice as far out as when I was running 1080. I suspect it's something to do with the screen size... I'm not sure why you would run at 4k on anything smaller than a 30' display...

So I was returning home from a particularly dirty spat with a Mig 29 in my F14 the other day, when I realized I'd suffered a lot of damage and my wings were stuck at 68 degrees, my breaks were also degraded. My high-speed approach resulted in my shooting off the end of the runway and disappearing in a ball of flame. I was based at Nato military airfields in the 80's and 90's, all these airfields had arrestor gear and overrun gear for emergencies just like this. Are there any plans to implement this functionality in DCS? The mechanics are there as we have arrester gear on carriers, would be a good addition and add reality...

The quickest way is to enter them on the F10 map, make sure they are named correctly, you can then import them using the Jester menu. There's a great video on how to do this from Spudknocker:

I don't think he's irrational... parking brake is the last thing I'd bind... you use it once after start and once during shutdown...

https://foxtrotalpha.jalopnik.com/an-elite-f-14-airman-explains-why-the-tomcat-was-so-imp-1610043625 Gives some good insights into real word flight ops and comparisons with the F18...

It's my understanding that the RIO would normally handle ATC calls, Is there any way to get jester to do this (I'm talking about a Jester GUI menu option) I see we can get him to tune to various ATC frequencies but there is no option for him to interact with them. Calling for takeoff clearance, inbound, vectors, landing clearance would be useful..

As it has a key binding available...I've just used voice attack to say "check" which then hit's the key without even having to enter the jester UI, simples ;)

I've been wondering about this exact same question for a while... I suspect the tracks would run faster as AI is not dynamic when replayed or is it? would be interesting to run a track file with lots of AI and then compare it a few times on Tacview to see if the AI was behaving in exactly the same way, you should be able to force some randomization be setting AI skill to random. If the track always behaves the same, you have your answer...

Yes it does.... but maybe not in DCS.... ;) Apart from actually having worked on it during my 12 years in the Air Force, there is plenty of documentation out there explaining how it works from reputable sources... Like:https://en.wikipedia.org/wiki/Link_16 From Northop Grumman: https://www.northropgrumman.com/Capabilities/DataLinkProcessingAndManagement/Documents/Understanding_Voice+Data_Link_Networking.pdf

Basically, you don't need all that Eclipse stuff if you're just modding scripts: Download and install notepadd++ Download a demo mission here, any demo mission: https://github.com/FlightControl-Master/MOOSE_MISSIONS/ change the miz format to .zip and unpack the file, you should find a file in there, <mission name>.lua THIS IS THE MOOSE MISSION FILE that you can edit in notepad ++ Download moose.lua https://github.com/FlightControl-Master/MOOSE/releases THIS IS THE MAIN MOOSE lua file you need to load at mission start, don't edit it!!! Save moose.lua in a safe place <user/yadayada/saved games/MOOSE> or something. change the zip back to a miz file mission.zip to mission.miz Open the mission file in the mission editor, there will be at least two trigger actions at the start, one loads moose.lua and the other will load the mission file lua, ensure that these trigger actions are pointing correctly at moose.lua (the one you downloaded) and the moose mission file.lua the one you extracted from the zip file. Save the mission and then start it, it should run with MOOSE doing all the cool stuff it's scripted to do in the moose mission file. If you want to change the mission you can do so by editing the <mission name.lua file> and re-saving the mission. Best to edit the lua file in notepadd++ and enable "lua" as the language. If you open it up in a normal text editor, sometimes strange things happen with line breaks and it becomes unusable. I'm not going to teach you how to lua program in this post.... that's what you need to do yourself, lots of copy and paste... it's fairly straight forward to customise basic stuff using a demo mission template though...

Link 16 is LOS (Line of sight) but some units have the ability to relay signals from one node to another, essentially creating a mesh network, I doubt however that ED have modelled this due to a number of reasons... so It would be pure LOS which could be anything up to 200 km ish... So if you're the other side of a mountain, you're wingman shouldn't be able to communicate with you via Link 16...

Why don't you try it and find out?

Not if you select Offset on the ALR 67, you'll see the RWR symbols in the HUD separated and be able to cycle between them easily...

The only way I can see to do it would be to edit the lua file here: <YourInstallDIR>\CoreMods\tech\TechWeaponPack\Database\vehicles\SAM The files are called: Rapier_FSA_BlindfireTracker.lua Rapier_FSA_OpticalTracker.lua If you altered the GT.WS.maxTargetDetectionRange in the Rapier_FSA_OpticalTracker.lua to a very low value... (1) it may force use of the radar tracker detailed in the Rapier_FSA_BlindfireTracker.lua file. Not tested! DONT do this until you've backed up these files! Not sure why you would do it as the launch and track parameters appear the same apart from detection range (GT.WS.maxTargetDetectionRange) and the ECM resilience which is set to -1 for the optical tracker (is not affected by ECM).

If you are using a Thrustmaster device and are not using the TARGET scripting engine or macro's then you don't really need it. I use the Warthog and headset fine without out, it's just another service running that takes up resources.

Ether dead reckoning or they'll bounce off a radial from another Tacan with a calculated course. Most of them (the pilots) will know roughly where they are at all times, It's basically situational awareness which becomes kind of automatic.

It can be used in fully autonomous mode... Rapier FS'C' "The Blindfire tracking radar, supplied by Alenia Marconi Systems, is a differential monopulse frequency agile radar operating at F-band which provides fully automatic all-weather engagement. The output is sufficiently powerful to burn through most jamming signals and the radar uses advanced frequency management techniques to evade jamming and other hostile electronic countermeasures. The system incorporates a self-surveillance reversionary mode of operation. A dedicated missile command link provides dual firing capability." I've also been stationed where these systems were deployed and have spoken to the Regiment operators...

It was only optically guided initially but updated after 1971 it had a radar tracker called Blindfire. DCS models the Blindfire radar (I haven't tested this but the Blindfire unit is part of the template)

That looks great, but it's missing the tape they used to put around it to stop it falling apart...which it used to do a lot...LOL

I'm not sure about middle earth but "space" would be cool, ED would have to tweak their flight models accordingly though, we could trade stuff between planets and dock instead of land... wait... ;)

I too am old but also watch ;) Basically it works like this (I'm not on my gaming PC so this is a very rough guide) 1. Find the targets using your LITENING pod 2. Lase the target and TMS short right to create the markpoint 3. repeat 1 and 2 for each target 4. Switch to mark on the CDU 5. Select JADAM program on MFCD (Ensure its set to CCRP) 6. HUD SOI 7. Fly towards first mark point 8. After drop cue for Mark A, cycle to Mark B using DMS up and down and pickle each Mark

Thanks Pikey, very informative. It would be very useful for the A10C to display bogey info supplied by AWACS and F/A 18's

@QuiGon SADL provides a gateway to Link16, they are compatible obviously when the link16 data is served through the Gateway.

Are there any plans to update the A10C to display link16 information from other aircraft, in the same way as the F/A 18 new functionality in the upcoming beta release?

Release dates are targets, you need them but you can't release a product that doesn't conform to normal quality standards, that's counterproductive for everyone. It hurts the company because their reputation is damaged and it hurts the consumer because they get frustrated and may not even be able to use the module. I work in QA (not for Heatblur), we can't release if we have high priority bugs (show stoppers) I'd rather them (Heatblur) get it right and have everything they said they would sort of working than stumble around with a buggy module. IF they just haven't finished the dev and miss the release date "end of winter" that's just poor planning... ;)