Delta134

Awesome work! I'm curious; do you do these performance calculations through interpolated empirical data (graphs and tables from the manual) or is it done using flight mechanics and equations of motion?

Hello, The drag index is an important parameter for flight planning in the F-16C. From what I've read the drag index is already calculated in the background of DCS. Since it takes quite some time to calculate this manually for each loadout, it would be nice to have it displayed on the payload tab in the mission editor for example. There it would fit nicely along the weight indications. What do you think?

The description of the feature in the changelog implies that the HOTAS command should switch to AG Gun Strafe mode. This is described in the DCS F-16C Early Access manual on page 471. Whenever you are in Gun Strafe mode it is also displayed on the SMS. Just because a gun reticle is shown on the HUD, doesn't mean you are properly in Gun Strafe mode. The SMS page should display the relevant information for Gun Strafe mode. Such as the gun status, rounds remaining, in-range cue distance setting. Currently with the HOTAS command there is no way to verify these or change the setting. This is also page 471 and onward in the DCS F-16C Early Access manual. Imagine you select Gun Strafe through the SMS OSB 1. You now suddenly need to quickly select your underwing air to ground stores and configure them. You use the handy HOTAS function. Except this doesn't help because to cancel out of Gun Strafe mode, you first need to press OSB 1 on the SMS anyway.

Today's patch has introduced this feature

First and foremost, I am very happy to finally see this HOTAS function being implemented! Currently when switching to AG Gun Strafe using the HOTAS command, the proper SMS format is not displayed. Only after pressing OSB 1 on the SMS, does it switch to the Gun Strafe SMS format. Reversely, exiting out of Gun Strafe mode using the HOTAS command, does not cancel the Gun Strafe SMS format. EDIT: Added track without mods installed gunstrafe_hotas_smsformat_NOMODS.trk

The transmit power setting from the mission editor is not transferred to the jet. This setting can be set in the mission editor through the 'DATALINKS' tab -> SETTING -> Transmit Power. The mapping seems to be off: None in ME results in HI in the jet Low in ME results in MED in the jet Medium in ME results in LO in the jet High in ME results in MED in the jet tndl_transmitpower_me_transfer.trk

@lee1hy I asked @Wags about this on his Part 1 video of the Sniper pod: "Hey Wags, great to see the Sniper coming together! I'm looking forward to it! In February 2024 you asked users to submit liveries to be included by default for the F-16C. lee1hy was chosen to deliver these. It has been a while, what is the status on this project?" "Given the strong, negative feedback, we decided to hold off on that." Very sad to see there is such poor communication between ED and the community members who have put so much effort into their liveries. It's outrageous those involved weren't informed they decided to cancel it altogether.

The pilot can see the difference by pressing IFF out on the TQS. This will remove any datalink symbology such that the state of the track can be seen.

It is a sort of bloom effect to indicate it is set too bright I think. Try turning down the HMD brightness. That should make it less blurry.

Still happening dcs.20250528-185916.log

I just interpreted it to be a bug following the way it is described in the early access manual. You may very well be right though. If that's the case, perhaps the manual should be revised to make that more clear. That would just leave the strange reset logic to be reconsidered.

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

In ACM Bore Slave the radar should enter NO RAD as long as TMS UP is held. The radar should only go active once TMS Up is released. This prevents the radar inadvertently locking an unintended contact. This is described in the -34 and as posted by @BIGNEWY : Track attached. acm_bore_slave_norad_tmsup_held.trk

The newly added anchored orbit function is a welcome addition! Unfortunately, it does not seems to function correctly. During the turns between each leg the AI performs strange periodic rolling maneuvers, inconsistent bank angle, or turn flown exclusively with yaw/rudder (no bank). The track of one such test displaying the strange behavior is attached. Results are seemingly inconsistent between tests. The problems seems to get worse with increasing winds. It seems like the AI is not able to meet their waypoints and is compensating with erratic behavior. anchored_orbit_turn_behaviour.trk Tacview-20250405-012507-DCS-anchored_orbit_behavior.zip.acmi

There are two problems with the hack time start/stop and reset logic: Using DED Increment to start hack time progression. DED Increment again stops hack time progression. Pressing DED Increment a third time causes the hack time to continue counting as if it was never stopped. It should start counting from the value it stopped at. Using DED Increment to start hack time progression. DED Increment again to stop hack time progression. At this point it is impossible reset hack time with the progression stopped. It is only possible to reset the hack time with the progression running. It should also work with the hack time progression being stopped. Refer to page 114 of the DCS: F-16C Viper Early Access Guide (Version 20th December 2024). Track is attached. hacktime_logic_issues.trk