llOPPOTATOll

It is incorrect as is based on OFP

If the cue range is not zero and is less than the maximum range, the TTR display on the hud should read how many seconds until the aircraft is at the cue range. Once the TTR is zero and the weapon has not been release, the TTR should be blanked, not read 00:00. Currently the TTR just indicates time until RMAX and does not blank after it hits 0 seconds

nullThe GBU-24 CNTL page should look like the attached image instead of how it currently is in DCS. Image is not ITAR, i drew it myself

We are missing the MAN deliver option for the GBU-24

In the SMS page it should not read "2GB24" it should include the version of GBU-24, for example "2GB24A"

There are currently atleast 4 issues with the GBU-24 currently in DCS. The GBU-24 Modes aren't implemented properly Cue Range/Time to release indication is incorrect GBU-24 SMS CNTL page is not implemented properly Weapon type indication is not correct (less important) Without the proper GBU-24 Modes the GBU-24 is lacking some of the main features that makes a Paveway III and Paveway III

Correct, what do you need evidence of

Missing evidence of what

Please change the default MFD setup, it is very inefficient and realistically a MFD setup would be loaded by the DTC anyways which we dont have at the moment so please at least change it for now. Ive attached a very good MFD setup that you could make default that I use that is much more useful than the current one. However any change would be very welcome. Image is not ITAR or anything, I made it myself. Asterisked pages indicate the default page that gets called up.

The JDAMs are just not implemented correctly. There should be 2 LARs, one for a LOFT and one for a level release. This is what the JDAM DLZ should look like

Lol, it isn’t called the RDR ATTK page in the viper either.

The viper does not use HAFUs, that’s a hornet thing

There is a supposed “white paper” they are working on but I haven’t heard any update on that for a while. Is this still being done?

For example, a tacan based on 1 #1: 1X #2:64X #3:64Y #4:1Y that way, if #3 needs ranging to #1 you can just switch band from Y to X without changing the number

Who do I contact with evidence

For some reason when locking a hostile correlated target it becomes a SUSPECT track instead which is incorrect. In addition, the TOI circle around the target is yellow which is incorrect for M4.2+, it should be a white circle around the target.null

RWS, SAM, and STT are the only modes I use

I very dislike auto population of CMs and TGs, it often fills the 50 allotted points very quickly with a bunch of stuff I don’t want

Track: https://1drv.ms/u/s!Aixanfk_YcTj6Bl2BliGRDUqj4Z7?e=LdkOOW

+1

LITENING II

Not for a long time, there’s a lot more stuff that’s higher priority than the FCR and RF hellfire

Iirc the “Chaff Flare” Betty sound is just cued by the CMS switch, so if you don’t even have any counter measures it will still say “chaff flare”

Betty always says “chaff flare”, Betty has no way of knowing what exactly is being dispensed so it just says both

The GBU-39 hasn’t even met IOC on the warthog, any images you are seeing of it are from the test and eval squadron