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.

^ This.

No, you'll need a slider or rotator for it.

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).

Noting that the Devs recently lowered the rotate speed (with keypresses at least, unsure on analog axis) and included a 'notch' at the 82 degree point, I suspect the lowered rotation rate is a concession to make the nozzles more controllable via key binding. Have you tried with both keypress and analog axis?

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?

That's good to know, so it might just be a labelling issue then.

Per your community manager's comment, the Subject Matter Expert he consulted indicates that the markpoint option should be visible in Air to Ground mode as it is in NAV mode. I do not have any documentation as I am taking the word of your community manager. If you don't trust him, then I guess we're at an impasse.. Pls see below for your community managers comment, and some very large an clearly annotated imagery that outlines the issue. Have a nice day.

Currently the Markpoint function (MK# on OSB 19 of the MFD when displaying the EHSD) disappears when switching from NAV to A/G mode. RAZBAM_ELMO told me to post the issue here as his AV8B SME confirms that the functionality should remain in A/G mode. The steps to set a markpoint (on a target of interest) are as follows: 1. be in NAV mode with the EHSD on one of the MFDs 2. lock up a target on the DMT/TGP 3. push OSB 19 on the HSI MFD ('MK#', where # is the next Markpoint number to be assigned), you should see the MP# number increase by one. When switched to A/G mode, Step 3 is not possible as the MK# option disappears from OSB19 and is not replaced with anything else. Desired behaviour is that the MK# option on OSB19 remains whenever the EHSD is an active MFD regardless of mode.

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.