Search the Community
Showing results for tags 'missing evidence'.
Found 10 results
-
Is it now possible to delete mark points? The "old" module did not have that feature...
-
Raptor could probably do it easily but can the Hornet turn at 470 kts, at 10k feet MSL with 8.5 fuel and 2xAim9X? Full stick back ~ 6.8G This is nothing new. I've been wondering about this for a while but usually I stay below 450 during gun fights and at those speeds Hornet bleeds profusely... Short clip:
-
Right now the F-16 radar is way too powerful, and is easily able to pick up anything of various size before 40nm flying in the notch or a beam while the Hornet, and even the F-15c won't be able to detect the same targets if I just sub out the F-16 for one of the other mentioned modules. The radar In the F-16 is supposed to only be slightly worse then the one in the F/A 18C hornet, but definitely worse then the one in the Eagle -
Before I say anything, I'm a Hornet pilot mainly. Did some testing tonight, at 10,000 ASL, x2 AIM 9s and x2 AIM 7s, 60% internal fuel. It sustained 14.7 degrees per second at around mach 0.8, and around 7G. According to all charts I can find (which, granted, aren't the real charts, but one I used is supposedly BASED on the real charts) it should do just over 13 degrees per second. ED, you don't have to artificially inflate the performance of the jet to sell it. Please, please give us the correct performance. Going by the Viper's real charts it shouldn't be out rated by a Hornet in this scenario.
-
So for a while now I've been thinking about all the FM artefacts we are seeing in DCS Range Cruise AOA is too low (3.2 vs 4.2 IRL) Low speed fuel burn is too high Bleed during turns is too low Sustained turn rate is too high (suspected) It's occurred to me that all of the above can be explained by hornet having too much lift, or more specifically a Lift/Drag ratio that's too high. If the airframe produces too much lift, then it wont need to meet the same AOA to fly level at a given speed, so we will see lower AOA values for cruise flight. If the fuel burn was calibrated for range cruise, it would have to be increased to account for this lower L/D. This would make the burn match the specific range charts for maximum range flight, but when you fly slower, the fuel burn becomes artificially increased above where it should, which is why the fuel burn is much higher than the specific range charts indicate at low speed. Too much L/D means less AOA required to make the G specified, so less AOA during turns, less AOA means less bleed. Same as point 3, less bleed means more thrust overhead. Hopefully ED will fix hornets FM at some point in the immediate, perhaps all thats needed is a simple L/D adjustment, perhaps more is needed, idk
-
I think text should also turn black when in black hot. Can't read white text on white background when in black hot. Thanks!
-
As the title says, when loaded with AGM88C, no BULLSEYE information is displayed in the HUD. Once you have MAGNUM'd all, BE info returns. -
I believe I found a bug with the HTS/HAD and how it changes the steerpoint diamond location in the HMCS after producing a SPI with the HAD as SOI. A trackfile is provided to demonstrate the incorrect behavior against an SA-2 site on the Syria map. 2x Harms are loaded on stations 3 and 7. After slewing the HAD cursor to a surface radar-emitter on the HAD, TMS Forward/Up will designate the emitter (e.g., an SA-2 in the trackfile) and perform a handoff to a HARM. This all works as intended, including the creation of a SPI; however, the trackfile also shows how this process currently changes the location of the steerpoint diamond in the HMCS as well. This is demonstrated in the trackfile by the steerpoint diamond symbol switching positions to the location of the new SPI (i.e., the box) set by the HTS/HAD. I believe the correct behavior would keep the steerpoint diamond at the location of the current steerpoint as indicated on the DED. To further demonstrate the bug, I cycle the current steerpoint from STP 1 up to STP 2 and back to STP 1 to show how the steerpoint diamond in the HMCS should be in a different location than the SPI set by the HTS/HAD. Doing this in the trackfile resets the steerpoint diamond to the correct location (i.e., the current steerpoint) with the SPI remaining in place based on the data from the HTS/HAD. I then repeat the process again after cycling the current steerpoint, at which point TMS Forward/UP on an emitter causes the steerpoint diamond to again change to the location of the SPI. Thank you in advance! hts_stp_spi_bug.trk
-
I wish this weapon (on par with CBU 99) to be more effective against light armor). Nowaday i find this weapon very frustrating in term of results... Thx
-
I saw that in the latest Wags video, the Mode 4 interrogation gives a negative reply. This is not correct unless the target being interrogated has its parrot bent or the A/B code switch is set wrong in either aircraft. Mode 4 encrypts both interrogation and reply, and an incorrect interrogation (such as one from a hostile aircraft) would not return any reply. This is precisely so you can't use IFF to locate enemy aircraft.
