LorenLuke

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.

So, the reason for that is if you do that at night, it auto picks the head mounted sight used. There's the sight which can cue the Shkval, or the NVG Monocle. These can be switched out by the ground crew OR set as specifically one or the other in the mission editor. What I'm referring to is not any sort of night vision via light amplification, but straight up Black/White thermal cameras for the Shkval.

With the updating of the module, would it be possible to update the laser logic, or include an editor option to enable cross platform laser codes. Seeing it be able to interface with the FC3 Russian aircraft, or with NATO aircraft die to the lack of Russian full fidelity modules, an option for setting the platform as buddy lase capable, as well as if the laser is soviet capable or set to preset NATO codes for Shark laser settings 1, 2, and 3.

We already have the Iglas added as part of a what-if/FrankenHelo scenario for what the Ka-50 would have been (and these options for those who want super-serious, hyper-accurate, realistic Black Sharks can deselect the relevant boxes in the mission editor), there exist the Black sharks, namely the N/Sh variants that both have FLIR systems and in the case of the N variant, a radar, which appears to be similar to the Ka-52's radar, and in various other versions, a Radar Warning Receiver. Granted, the sordid history of the Black Shark makes for the interesting scenarios of various models having a particular capability and not the other, and the fact that it really never entered full production to have a 'standardized' model, we see the hodgepodge of capabilities that it could have had, but doesn't (at least in DCS). Because of these things, and because we've progressed to the point of hypothetical extrapolation with the addition of Iglas and the whole 'third pylon' business, having these features included would expand the hypothetical capability of the platform, while still being built upon platforms and systems that were confirmed to have been joined to the Ka-50 platform at some point in its development. It would give Redfor a capable night attack potential for its helos, and would align the Black Shark much closer to the current iteration of the Ka-52, which the 50s were originally designed to work with in a 'wolf pack' anyway.

Hell of a necro, but they can carry them, and I think we should have them.

Alas, not quite every binding. Still hoping for a dedicated ON and OFF command for this: null

Please either make it so that our body, seat, or the entire back of the helicopter can block out sun glare from directly behind the player, or at least change the time of day so that the INU reset mission makes it near impossible to see the target.

If I had to guess, it's probably due to missile smoke ingestion. Have you tried it in 120kph forward flight?

Any and all things for datalink points (NOTE: not the constant stream of aircraft locations that an AWACS gives) would be nice, as far as any of the following for the mission editor/script/events/etc. The ability to create a datalink target, for a specific target/frequency/whatever for a target (or target coordinates), with a couple of sub-variables for things like type, label, etc.; given the range of datalink systems available, some API or universal reference for what may correspond to what may need to be used. An event listener for all of the above, including the sending aircraft. With the above this could create the following: Event related tasking via link16 JTACs for appropriate platforms. Additional tasking from AWACs or other units, including possibility to handle assigning points as a force commander or game master using map markers and an interpretation script to convert the map point into a datalink location. Datalink integration cross-platforms to create stopgap links (albeit fictitious ones) between incompatible platforms to fulfill roles that otherwise would take place with platforms not in DCS (e.g. an AH-64 serving as a ka-52 stand-in command and search helicopter for a Black Shark wolfpack)