LorenLuke

Because I'd like to be useful for something other than firing 4/8 missiles, and then twiddling my thumbs after.

How are these expected to function, and what's the scope of their function? Within a single mission, or somehow having cumulative wear across multiple missions or a campaign? A setting in the ME, perhaps?

Consider though that the Mudhen would have to come out of early access, lose the 20% discount, then be around long enough to THEN go on sale for something more than 20%. I imagine people who want it will weigh the 'eh, it's just eight bucks anyway' and eat the difference rather than wait God-knows-how-long.

But if they don't warn, all the people who'd get it then don't get the 30% discount, but only 20%; RB would make an extra $8 per sale. I don't see why they'd not seize this opportunity for more money.

Alternatively, maybe he asks here because he trusts people to know what he's talking about and answer accordingly, instead of just googling and finding either the same four images repeated everywhere for a niche hobby, or possibly providing him wrong information that he may not trust himself or his knowledge enough to know it's wrong. Those are certainly reasons why I ask people instead of, or in addition to, just going to google like it's a magical library (mind, even if it is, it still has no human librarian to clarify any questions you have).

I don't know if they have their settings to yours, but I can say that my experience was that if you turn SSAA off, it 'fixes' the problem. (You can still see a drastic change of perspective around the monocle, but the perspective within the monocle remains the same as when it's not equipped. Hopefully that serves as a workaround for you.) https://forum.dcs.world/topic/321912-nvg-monacle-fovperspective-broken/#comment-5180801

It appears that this effect is directly tied to the Super Sampled AntiAliasing setting (SSAA). Turning this from 1.5x or 2x to Off/0x eliminated this effect for me. Hopefully this information helps ED fix this issue.

NVG Monacle FOV/Perspective broken since MultiThreading Open Beta Update. Affects all planes. View also offset in CA for all night vision optics (JTAC thermal and visual modes FINE), including gun reticles (gun shoots low and to the right). Run on single monitor, non-VR. DCS Version 2.8.3.37854. AV8B Throttle.trk

I believe it's there in the track file. But yes, the laser is armed in both instances. It fires (or it indicates it's firing via symbology, at least) when the button is pressed for the GBU. It does no such thing with Mk82s as the active weapon. To my knowledge, it didn't have this lasing behavior before, so I'm seeing if this changed, or is somehow correct, or was something I just happened to miss.

Except it doesn't do this with regular unguided bombs.

Weapon release button with LGBs fires laser, even if outside release parameters, even if auto lase is set to 0 seconds, and even if the 1st trigger detent is not pressed. F16 Laser Bomb.trk

The ability to buddy lase for other laser guided weapons on Russian hats should be a thing (as should the weapons themselves, particularly the KAB LGBs), including for and by the Ka-50 Black Shark.

null

So, I could be wrong on this, but the way the datalink was explained to me was that it uses the current position and orientation of the aircraft, as read by the PVI800, and then the angle of the shkval and the laser distance, all to produce some point in 3D space somewhere as the target point. Therefore, as your INU drifts over time, your relative space is going to produce a difference from your actual coordinates, so when you go to uncage the SHKVAL to the target, it's orientating itself to the target point using your PVI800 coords and orientation as the reference. If your actual coordinates are in line with the PVI800 coords, this is fine, but if they're not, there's going to be an off-set from that point, which should be basically equal to the disparity between your PVI800 and actual coordinates.

Yes, it was.

Yellow indicates a laser of some sort being pointed at you. Red indicates a missile being launched/flying at you. Yellow is only in 90 degree arcs, while the missile is narrower.

Allow mission editor drop-down box for GNSS availability with the following options: Auto- As it is now, requires Russia on coalition Always- Available always regardless of coalition Never- Not available regardless of coalition

For the Vikhrs, the target ring is offset to one side of the center, and can be used to predict, rocket pods are always fired in some multiple of a pair, and for both vikhrs and iglas, it's always the left pylon that fires first. In case of the iglas, it empties the pylon, while for the vikhrs, it alternates. So if you have more than 2 Iglas it's the left side, and if you have an even number of Vikhrs remaining, it's the left-side (or left side first, in the case of salvo mode).

Dropping this here just so I don't have to retype everything.

Did you set it to English under the BS3 special tab? There's a different tab for BS3 and BS2.

Check your in-game volume settings. Perhaps whichever one that corresponds to in-helmet/radio volume has been lowered.

Last I heard it was removed. Needs testing though.

Su-24/Su-34 FF Su-25 B1-B F-111

They literally have options to align from a stored heading. In the Viper just hit ICP enter after switching to ground align, and PB19 on the MPCD immediately after going to ground align on the Hornet.

That's all fine, but I'm talking about the Shark's Kh-25MLs. Or lasing any other platform that has laser guided weapons.