Search the Community

When putting the FMU-152 tail fuze on the Mk-84 High Drag variant, the minimum arming delay is 2 seconds. However, if I put the same FMU-152 tail fuze on an Mk-84 Low Drag variant, for some reason the minimum arming delay is 4 seconds.

While in the NAV master mode it is impossible to enter ACM Bore Slave with the JHMCS. It is functioning properly in the A-A master mode and dogfight override mode. It should be possible to use ACM Bore Slave in the NAV master mode. acm_bore_slave_nav_mode.trk

Subject. I do not have any real data, but these oscillations look and feel weird when doing a basic crank maneuver. Oscillations are less violent when you are slower. Added: on 0.9M it feels nice and smooth. I think the current FCS implementation can't keep up on 1.4+. Have added second track with full stick deflection. F-18-oscillations.trk F-18-oscillations2.trk

In the current build, the command steering is activated automatically upon receiving localizer signal as advertised in the manual. But according to the HAF manual, command steering can be enabled/disabled by placing the asterisks on the CMD STRG in the T-ILF page and depressing the MSEL button.

In the real F-16 hud when doing abrupt movements the pitch ladder should not be 100% responsive, like in the Jf-17s hud

AIM-9X automatically cools down when powered on. So word WARM should be removed from MFD based on Movers words. COOL should stay (I suppose).

I've put a simple mission together (cold start) to rescue troops at elevation, in bad weather. Apart from fuel, the chinook is empty. I have noticed that I begin to lose rpm when I approach 6000ft ASL, and it continues to deteriorate as I climb, the whole time my torque is around 55-60%. At around 7500ft my RPM is 74% and I'm still airborne LOL dcs.log afghan test.trk CH47_2-ship_QRF_Transport_V2.miz

I was playing around with the flight model while trying to set up my pressure sensing stick, and I realized that the flight model, in particular the roll axis, seems to be incorrect. The DCS Viper had always seemed to fly a bit odd, not intuitive like a real airplane, but I could never figure out why. Something is off about it. I read numerous comments on the forums, and watched several videos, that have this odd pitch-up moment when rolling out of a turn to straight and level. It's done it to me, and real aircraft (even other DCS aircraft) don't do this. Why the DCS Viper? I've trained my muscle memory to pitch down when rolling out to hold an altitude, but this is not a trait with real airplanes. I think I've found out why it acts this way. I was doing some high AOA flight to sort out stick forces to hold different steady nose-high attitudes, and discovered that ED has programmed the rolling axis of the Viper to be on the Flight Path Marker, not the gun cross in the HUD. In any airplane, there are three axes of rotation (pitch, roll, yaw) that all intersect at the Center of Gravity. Every airplane, no matter the pitch condition, the ailerons (and stabilators) will only roll the aircraft about this lateral axis, which runs down the center of the fuselage from front to back, parallel to the long axis of the fuselage and does not move or change with AoA. This axis is depicted by the gun cross on the HUD. If I pitch up to 30 degrees AoA and then roll the airplane, the roll should always center on this axis (the gun cross), not the FPM which in this case will be well below. In this case, I would end up in a nose high turn and the nose would not roll through the horizon like it does now. But the DCS Viper rolls around the FPM with high AoA. You can see this by setting up a high AoA flight and inducing a roll. The gun cross will move laterally around the FPM, when it should roll around the gun cross and the FPM will then adjust to the direction of flight. There is one other thing that can contribute to this behavior. In the flight control software, rudder is added to the roll input to assist in maintaining coordinated flight. This is designed to counteract the situation of adverse yaw (where the nose points opposite of the direction of turn due to drag increase on the outside wing). Most airplanes compensate for this in various ways, and the Viper is no different. Rudder is added to the roll input by the flight computers. Again, in a real airplane I can manually duplicate this odd behavior by inputting positive rudder with aileron. But this would technically be a poor technique, as adding that much rudder would induce a skid, which is too much rudder input for good, coordinated flight. I'd like ED to have a look at this and see if I'm correct. It may be simply adjusting (reducing) the rudder input in the FM. The biggest issue I've seen is the weird pitch up when rolling back to wings level and having to add significant down stick to maintain an altitude. Cobb

It's really appreciated the introduction of the new logic for sending contacts over TNDL. Now instead of Bugged Target, the Track Targets are sent, it has a solid logic: if you have vector data its possible to share it. Good job! Now let'see the bug: Multiplayer: if your mate uses TWS, the HSD dashed line is applied to the last Track Target created and not to the Bugged Target.

EDIT : link to the original comment on another forum post AGM45noStationSTEP.trk

Hello, there are images floating around of F-16Cs carrying dual Lau-68 on a TER, as well as carrying dual LAU-3 on a TER. Unguided rockets are underrated and it would be great, if we could get some more options regarding those. Lau-3 on TERs would really add firepower, while availability of Lau-68 would add many options for lighter loadouts... *edit* not sure anymore about lau-3 on TER, but lau-68 on TER is definitely a thing.

When entering SPOTLIGHT mode, the radar antenna does not move at max speed to center on the curser azimuth. It currently moves at normal RWS speed to the curser. It should slew at max speed allowed when entering Spotlight, similar to when entering SAM or STT. Once centered on the curser azimuth it should slow back down to normal search speed. SplotlightSlewSpeed.trk

Test conditions: -the plane is at the airfield with the engine off; -but with the electric power supply connected; -included power toggle switches to all systems. When connecting ground power at the airfield, the TGP does not work, at the same time, the AGM-65 missiles received power and worked normally. TGP starts working only when the engine is running... https://drive.google.com/file/d/17nc0jeXwXUucNFuTZHCtB6IIBAkzJr8L/view?usp=sharing

Tested with DCS 2.7.6.13436 Current behavior: The ASE cue seems to point into the flight path of the target aircraft Desired behavior: The ASE cue should point into the ballistic trajectory that the AIM-120 wants to maneuver into after launch, so that the pilot can put the aircraft in an attitude where the missile will not have to maneuver after launch For testing: This is most obvious for high-altitude long-range missile shots, e.g. head-on, both aircraft at 30k ft altitude, distance ~30nm. The small circle will be displayed at the bottom of the large circle, indicating that the pilot should point the aircraft's nose down, but after the missile is launched, it will immediately pitch up about 30 degrees. Therefore, the ASE cue should show the small circle in the middle of the large circle when the aircraft is pointed into the ballistic trajectory of the missile, instead of into the flight path of the target aircraft.

F-16 checklists have a section to check AR door & system but when I follow them, I can't check the AR system on ground after start. Indeed, the checks says to open door, check blue light RDY on in right indexer => works OK then click DISC button on stick (same as NWS = index finger button) and check that yellow DISC comes on, RDY light comes OFF 3 seconds later, DISC light should extinguish and RDY light comes ON again. => this does not work Upon pressing the index finger button on the stick, NWS comes ON (green) This is not correct as AR doors open inhibits NWS to give consent to DISC operation which is on the same button tested this morning with latest version

When in air, and at the moment de gear handle is selected down, the light in the Handel does not immediately illuminate. Any time the gear handle position (Up or Down) is not the same as the condition of the landing gear system at that moment (up and locked, or down and locked), the handle light should be on. The way it seams to be simulated at the moment is that, when selecting the gear handle down, the gear handle remains dark until the doors are fully opened. This is most likely wrong, because if the gear handle is selected down, the gear system at that moment is not in the down and locked position. Minor thing, but still..

Hi all! I don't know if this is a bug or working as intended but I'll submit it anyway even if someone may find it "minor"... When starting the aircraft, if the Internal Light switch is set to NITE (and probably NVG, too - haven't checked it) BEFORE electrical power is supplied, the IFEI lights always starts in DAY mode regardless of MODE switch position. This happens both with battery and ground power. I'm attaching two track files (one battery startup and one ground startup). P.S. As a side note, IFEI's light in NITE and NVG mode seems to me a bit too bright at night. To make it readable, I usually set it to "zero" first and then to the first "tick" above it; higher settings provide too much backlight in my opinion... Nite Light Mode Battery .trk Nite Light Mode Ground .trk

F16 BLK50 Radar is still so weak. now we only have around 40NM heavy fighters scan range. According to 90s USAF official clip it shows F16c early vision that possibly Blk30/35 APG68 radar have at least 58NM heavy fighter scan range. I will leave link here. I think this is strong reference for prove Apg68 not only have such weak scan range. https://www.youtube.com/watch?v=Aq5HXTGUHGI

In NAV mode, the Radar Target Locator Line, doesn't appear in the HMCS. Is this correct ? NAV A/A no Radar Target Locator Line HMCS.trk

Maybe this is perfectly accurate/realistic, but I guess I'm a bit surprised that a clean Lot 20 Hornet with no pylons and 85% fuel capacity is not 7.5 G capable?

Hi, currently you can't adjust antenna elevation while in SIL (the elevation caret will move to the commanded position when the radar is taken out of SIL though). This "looks odd" and I can't find any mention of this on any document, so I sort of report it just in case... Is it is possible for you to consult this with your SMEs?

Hello all, Will there be an option to arm mixed load on the BRU racks? e.g - 1 JSOW + 1 JDAM on station 7 and 1 CBU 105 + CBU 103 on station 3? Best, desert

my goal was dropping 2 jdams from same station(8) using TOO1 and TOO2 I was going to drop first bomb then change it to TOO2 and drop second, so I selected station 8 via QTY, after the first bomb dropped stores page selection jumped to station 2, and second release didn't happen of course because no coordinates was entered on station 2, I think if QTY is selected for only 1 station stores page shouldn't change, it might be a bug, jdamQTY bug.trk

As shown in the 16_rws_expected track, the expected behaviour of the cursor after commanding a SAM lock on a target is that the cursor snaps to target, allowing you to command an STT lock on your target without having to reposition your cursor over the target. The radar screen when in SAM will automatically reduce radar scale when the locked target comes within a certain range, however, this transition of radar scale causes problems with the aforementioned behaviour of the cursor locking to the locked target. When a SAM lock is commanded on a target that is near or within the range where the radar scale will automatically scale down, the cursor will either not lock to the target at all, or lag behind. This lag means you can no longer TMS UP to command an STT lock on target without repositioning the cursor. In some circumstances, especially in closer ranges, the cursor might not lock onto the target on the radar cursor at all. This behaviour gets more apparent the closer the target is. 16_rws_expected.trk 16_rws_snap_1.trk 16_rws_snap_2.trk

It doesnt matter which tracking INR/SCENE/AUTO you use, all three continuosly updating distance even without TDC depress = WRONG, No Laser measurment should be done. No one on battlefield wants to shine targets by laser unless necessary for getting accurate coordinates or wpn delivery. This make AUTO low level delivery (CCRP) or LOFT attacks after ATFLIR target designation almost impossible. ATFLIR_INR_Range_BUG.trk