Floydii

Yep, that's orange.

I've had the same thing happen twice. Always when the helo is in motion.

Prob too much to ask, but the ability to change the laser code (on the kneeboard, like the F16) would be great. Maybe not 100% realistic for bombs underwing, but Ideally it would affect the Pave Penny and any GBUs fitted. That would allow us to use something other than the magic 1113 code. Maybe not 100% realistic for bombs underwing, but inflight code change would be realistic for the pave penny without adding too much complexity.

He's been posting as lately as 21 April, so still with us. May have gone off the project?

Interestingly, the Raz bam Harrier has a very similar issue with Mk20s.

So do you need it as part of the TOO JDAM process or is that accurately ranged automatically or by designating for a few seconds? Honestly more interested in the sim implementation rather than IRL (if they vary).

Currently when pressing RSHIFT-H, night vision goggles are turned on/off. This binding is indicated as 'HUD Brightness Decrease' in the control option menu. Desired behaviour is that 'HUD Brightness Decrease' actually decreases the HUD's brightness rather than turn on night vision. As an aside, having NVG in the Viggen is nice..

I've been wondering this myself. It appears to give a flashing 'R' in place of the 'D' on the HUD that usually flashes to indicate that the TPOD is designating with its laser. In the absence of other info, I suspect it is either a 'ranging only' mode for the TPOD, or is doing something that requires accurate ranging. As JDAMs off the harrier in TOO mode are somewhat.. unpredictable at the best of times, I've been unable to determine if LTIP gives a more accurate result.

Try holding down the Waypoint Increment button for a second once you have the laser spot acquired on the DMT. That should set that point as the CCRP release point.

https://forums.eagle.ru/forum/english/licensed-third-party-projects/heatblur-simulations/7127476-thank-you-so-much-for-the-invisible-farp Get on it.

It is literally the best thing Heatblur has ever done (and the Viggen/Tomcat are amazing). Tested it with AV8B, as long as you've got support vehicles nearby the FARP you can get service from ~100m away at least. Devs, can you advise what the exact service radius is for the FARP is?

Very nice. Might update mine.

What comes over the video feed could well be analogue data that is utilised by the aircraft avionics to generate what we see in the displays as opposed to a 1 for 1 visual image.

4 HARMs eh? Hoggit loadouts go on. ;)

I'm not convinced that is inaccurate on the Hornet as the HARM is looking for one radar in a very small area once you hand-off and get the box. Think of it like an 'STT' lock as opposed to regular radar search, the updates are now determined by the gaps between the target emitter painting the HARM seeker - much faster than the HARM searching about for an emitter. By design the seeker would need to be able to determine the relative off-angles from its boresight to steer itself to a target radar and those offsets could be pushed back to the jet, thereby giving you a box on the HUD. Much like how the AGM65 triangle on the HUD lines up with where the seeker is looking. The last comment on needing two HTS fitted F16s is more related to Geolocating an emitter in realtime (as opposed to simply telling you where the seeker is looking relative to your centre-line per what I've explained above). Of note, the DCS Viggen can already geolocate emitters as a single aircraft, but it takes time to build the picture as you need to get multiple 'cuts' on the emitter from different locations.

I noticed the HARM mode in the does not show a box on the HUD to indicate where the locked up emitter is. This is different to the Hornet when it uses its (largely similar) TOO mode. Additionally, the HARM interface on the Hornet also doesn't appear to have the same scan time or emitter count limitations as the Viper (for what should be the same as its the same AGM-88 seeker with the same limitations). Is this an omission from the Viper modelling, an abstraction in the Hornet's modelling or actually how it is supposed to be? Will we see these weapon limitations carried over to the Hornet eventually?

Assuming that this has yet to be added. It'd be particularly useful in MP when switching role or Aircraft.

Man on a mission. Yeah, they clearly do change and don't reflect the right stores often. For example AGM65s come up as 'Flares'. It looks like the weapon IDs got jumbled at one point and this didn't get updated in the A10A module. So maybe the old illumination flare ID is now used for Mavs.

Not 100% what you are trying to say here, but what I outlined above is how to get the Autopilot working on the FC3 A10A.

I'm curious what the technical limitation is here. I see the kneeboard and chat show up in VR, so it's not like it can't be placed that way.

The assumption here is that DCS has modelled all of its laser designation methods to be interoperable, which, while good for gameplay in hypothetical situations, isn't realistic. The four digit laser codes we see in DCS are NATO (or at least US) standard, not a global standard. Russian laser designators and related proceedures evolved separately so the code system used by western aircraft and JTACs isn't compatible with Russian systems. Now, the A10A and SU25T in DCS can both track code 1113 on their spot trackers, but as they are not full fidelity aircraft, this appears to be an abstraction for gameplay purposes (noting that an actual A10A could track any NATO standard code while the 25T shouldn't be able to track any). You could try 1113 for the KH25, but I've had no luck in the past with it.

From reading the manual and extensive experimentation, there doesn't appear to be a laser spot tracker (as per most TGP equipped DCS aircraft or the A10C/SU25T) as part of the Shkval on the KA50, so it doesn't actually have the ability to detect a lase. You can buddy lase KH25Ls for other KA50s, but the cue you see on the HUD is the Missile' s seeker picking up the laser, not the KA50's sensors.

Turn EAC on first, select your desired autopilot mode then engage LAAP to engage the Autopilot. I don't know how realistic it is, but I can reliably get Path Hold, Alt Hold and Heading/Alt hold.

Also, carrying two different types of launcher (both with practice smoke) is useful if you just want to fire a single rocket for marking targets and not pairs.

With the addition of the inboard pylons being able to carry (most) 500lb weapons, the ability to ripple more than four weapons has not been added. If you go to the SMS with bombs selected and select 'qty' it only allows up to four bombs to be selected. Can you pls add options for 1-6 bombs to be selected? Additionally, MK82 SnakeEyes and MK20 rockeyes cannot be loaded on the inboard stations. Is this a deliberate omission?