Sinclair_76

My guess as well. A close second might be the Master Arm in Safe.

Pilots in general tend to make things easy for themselves. I think you're method is the standard as in swing roles you get to switch from A-G to MSL with just the Override switch.

I agree. Iirc the long left on TMS does NCTR as well as an IFF spot interrogation. Sure... IFF in DCS is automagically configured but it will differentiate between blue en redfor in the end. Te other Viper shows Red beacuse it doesn't respond correctly to the IFF interrogation. Disregard. After a failed IFF contact should show unknown and not hostile. So the red target should not been happening. Good catch. In the case of a bent IFF resulting in a blue on blue. Generally ROE are pretty robust and are resilient enough to exclude a single point of failure. For example an aircraft can be designated hostile after being determined by two independant modes. Visual and no/wrong mode 4. Or NCTR and not adhering to corridors. Etc.

With the tracks I submitted I specifically did not use the TGP to update the weapons with TMS up. I used preplanned coordinates so the error would be isolated to the weapon itself. Besides the TGP error, as I've seen it is causing weapons to fall short, no lateral errors reported. So the lateral error you see in the submitted tracks is due to lack of correcting for wind.

Correction, I did some testing about a year ago ... and the AGM-154A compensated nicely for wind dropping submunition wel on the upward side to compensate for drift. Now the JSOW doesn't seem to compensate anymore. The105 remain unadjusted and fails miserably in a strong breeze. Due to the shorter drift time compared to the -105, the -103 submunition scatter less and actually do some damage. But the drift is still there Test-xwind-AGM-154A.trk Test-xwind-CBU-103.trk Test-xwind-CBU-105.trk

Within DCS The AGM-154A compensate for bomblet wind drift and the CBU-105 doesn't.

Thanks. I was trying to get it displayed with unknown. That didn't work.

The SA-11 Search Radar (Snowdrift or SD) does not show up on the RWR. The HTS and the AGM-88C do pick it up and show it on the relevant pages. When the SD radar activates, the RWR will chirp. The SA-11 TELAR, once active, shows 11 on RWR and WPN page as well as HAD. Test-SA11.trk

Sure. If it really was an issue Ukraine would be without GPS. Unless of course you don't consider Russia near peer....

To further develop the statement Early WW2 shaped charges where able to penetrate 150%-250% of the shaped charge diameter and modern ones up to 700%. (https://encyclopedia.pub/entry/history/show/75257). The BLU-97 shaped charge diame ter is approximately 63.5mm/2.5" (https://www.wikiwand.com/en/BLU-97/B_Combined_Effects_Bomb). So a 200mm RHA penetration would not seem out of the ordinary. (https://apps.dtic.mil/sti/pdfs/ADA264233.pdf) A T-72 has composite armor and translating RHA to composite is beyond what I am trying to prove. A T-55 however has 30mm armor on top of the turret (https://en.wikipedia.org/wiki/T-54/T-55) and the armor is of a cast type turret (http://www.military-today.com/tanks/t55.htm) so a direct translation of RHA would be more reasonable. By all metrics a BLU-97, with a 200mm RHA penetration effect should be able to penetrate the top of a T-55 hull consisting of 30mm cast steel. But in DCS, 1616x BLU-97 are unable to destroy a single T-55 in a small cluster of 9. QED that in DCS the BLU-97 is underperforming. Test-BLU-97-T55.trk

Isn't the IFF on the throttle reminiscent of another block? Afaik it's done with the TMS left long/short. Or are you referring to something else?

The problem may seem small. However accuracy is such that a GBU-38 can’t be targeted effectively.

The BLU-97 submunition, present in the CBU-87, CBU-103 and AGM-154A, underperforms in DCS. The BLU-97 is supposed to be a combined effects munition which is able to have effect on air defense radars, armor, artillery, and personnel. Basically it has 3 effects. (https://www.globalsecurity.org/military/systems/munitions/blu-97.htm) Anti-armor effect, due to shaped charge able to defeat the top armor of any known tank (edit 1993 document ) (https://apps.dtic.mil/sti/pdfs/ADA264233.pdf) or 7"/200mm in other pubs linked below. Fragmentation effect, 300 pieces of shrapnel able to penetrate 6 mm steel at 20meters (https://www.clusterconvention.org/files/publications/A-Guide-to-Cluster-Munitions.pdf) Incendiary effect, due to the zirconium ring. As it stands the 4x CBU-87 (808x BLU-97) are not able to defeat a single T-72 in a small cluster, as the included trackfile demonstrates. Further reading: http://googlebordello.crushhumanity.org/projectdoomsday/blu97.html https://bulletpicker.com/bomb_-heat_-blu-97_b_-blu-97a_.html https://tinyurl.com/3h4k2mtu Test-BLU-97-T72.trk

Not 100% sure but... Normally passive coordinate generation uses own position with azimuth/elevation of the line of sight from the TGP intersecting the DTED. But there's funky stuff happening with F-16 grid and the world grid.

Real life.

Yep sure that I did TMS up correctly. Crosschecked with the control panel. Besides it changed polarity with every direction of TMS.

Not the first time it happened. In certain conditions, which for now I am unable to replicate, the TMS up results in WH/BH/TV change in the TGP. Double checked bindings and correct input and functioned normal after I changed TGP to stby mode and back to A-G. Switchology TMS.trk

Slow brain day, story of my life When you start a mission with DML modules, it will display the active modules for say 30 sec. Is there a way to limit the message to 5 seconds or so?

How do you kill the list of active modules at the start or least limit the time?

In a cloner zone the source attribute won't work if it is a string of flags say 2-6. It only seems to work if the flags are seperated by a comma. Ie null Is that a bug or by design?

Can't wait to dig in. This will be awesome.

Long distance, short distance. All my drops were within the WEZ. Even at short distance (low in the WEZ bracket) the -38's fall well short. So I don't think distance plays an important factor in the error.

In the lower part of the WEZ. Direction of flight was from left to right. Still short. High precision, low accuracy. null-also a bug

I think the issues I am seeing might be related to Tried Caucasus and still have the same problems of -38's falling short.

I've done all the above and all -38's keep falling several meters short, never had a bomb go long. The one thing I haven't tried is gnd fuze. Could increase damage but will do nothing for falling short. Will try another theater as well as there were some problems with grid generation in NTTR in previous versions iirc.