Delta134

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

On the HAD threat page, the number behind each class disappears when the class is highlighted. The numbers should remain visible. Track attached. had_class_numbers_bug.trk

Thanks for the answers. @BIGNEWY could you perhaps check with the dev team if this is working as intended? Or if there is an update planned?

Page 506 of the DCS F-16C Early Access manual mentions the following: Limitations Standby time: 1 hour Video time: 30 minutes Page 510 on the manual suggests the missile will enter standby mode after the 3-minute warm-up period and as such has one hour of available duty time. Once a missile's video is activated, it has 30 minutes of available duty time. How do I select standby mode? Pressing OSB1 on the WPN page as the manual suggests on page 508 does not work. As soon as the warm-up period has passed the missile's video is automatically activated and OPER mode is selected, contrary to the manual. Power cycling puts the missile in standby mode for a short period of time; after three minutes, video is automatically activated again. I want to select standby mode to make use of the one hour duty cycle. Any suggestions?

KevinAu and I exchanged some PMs and he's convinced me that 15 degrees of bank is the better option for now, so I thought I would share why: ATP-56 (which was previously cited) indeed prescribes a 50nm x 20nm track. With the speeds tanker aircraft generally fly at for fighter aircraft (300kts), a 15 degree bank would result in roughly 20nm turning diameter (depending on altitude). That fits the 50nm x 20nm track perfectly. The 25 degree bank resulted in somewhat erratic AI behavior and throwing off other AI planes trying to refuel. I assume this could be fixed eventually. Although the tanker still somewhat struggles to fly the pattern whenever a receiver aircraft joins on the tanker's return leg, I was unable to replicate the glaring issues I remember having. The issue is more exaggerated with very short racetracks. With longer tracks this issue is less apparent. So I must have been wrong or ED fixed the issue. It doesn't change the fact the tanker doesn't behave like last advertised, so perhaps that description requires a correction. Ultimately, I think the option to set tanker bank angle would be nice. But now I agree 15 degrees of bank during refueling is more universally practical as opposed to 25 degrees.

It is not too violent and you can certainly easily stay connected. However, it should be improved, not removed. ED should either: 1. Provide 25 degrees of bank for the tanker and improve AI AAR capabilities while making sure the tanker remains level as well and/or 2. Make sure the tanker is able to fly its track properly at 15 degrees of bank Regardless, the way it is currently done is suboptimal

In my and my group's experience, 25 degrees wasn't violent at all. Only at roll initiation and rollout, the tanker had some minor trouble keeping altitude. I can't speak for the AI, however if that's the problem then the appropriate fix would be to improve AI AAR, not reducing tanker's bank angle. The 15nm racetrack in the track file is just so that it wouldn't take forever to start the first turn. The problem with the 15 degree bank is that the tanker has trouble reaching its required racetrack waypoint during the first orbit. When that's the case it can start doing weird circles or patterns (even with larger racetracks).

Update 2.9.11.4686 on the 24th of December 2024 featured the following change noted in the changelog: Since the update of 19th of February 2025 the KC-135 limits it bank angle to 15 degrees instead of the advertised 25 degrees (23 in actuality) upon being cleared contact. Now once again tankers are flying huge racetracks when refueling instead of the more manageable tracks with 25 degrees of bank. Track attacked. Simple 15nm racetrack setup for KC135. Issue become apparent at the first turn once cleared contact. kc135_bank15_rdyprecontact.trk

There is/was an initiative by ED to add liveries for the US and some other countries a little over a year ago. Sadly they've gone radio silent on this.

After firing an AIM-120 at a bugged target, the postlaunch time remaining is displayed on the HUD and FCR page. Once the missile has gone active, the "A" countdown mnemonic will change into "T" and the countdown represents the calculated time until the AIM-120 intercepts the bugged target. This is functioning as expected. However, upon the bugged target becoming a no-tack, the time until impact is removed from the HUD and FCR page. This is incorrect. If the tracked target becomes a no-track, the last displayed time remaining should be used to display time until impact. Track attached and supporting documentation sent to @BIGNEWY amraam_timeout_display.trk

Sorry? Why was this moved to the F-15C Wish List? This post is intended for the F-16C. Could the question please be answered? And just to clarify: this isn't a feature request. These are features that were outlined in the Viper Mini-updates as priority items some years ago. I don't think it belongs on a "wish list"

Hey @Wags Could you give an update on this project? I am eagerly awaiting the new default liveries

Hey @Lord Vader I am seeing the same issue and reproduced it with the following steps: ANT ELEV centered STT a contact that is not co altitude Break lock by flying contact outside of gimbal limits Antenna elevation is now not centered anymore despite the physical axis being at the center point This indeed results in the inability to use the full elevation range of the radar since the physical axis does not correspond to the center point in the simulator. ant_elev_center_bug.trk

The following features were mentioned in September of 2022 in the Viper Mini-Updates thread as priority items: Digital Maneuvering Cue (DMC) Loft indications (AIM-120 loft solution cue) IAM Loft Cue Adjusting AIFF and ROE Tree logic As far as I understand, these have not been implemented thus far. I understand current F16 development is focused on the Sniper ATP (and perhaps the DTC). But since these items were mentioned so long ago, I would like to ask where along the roadmap these features are planned to be implemented? Air-to-air datalinks and PRF tones were also listed in the aforementioned thread. However, these are on the roadmap for implementation after Early Access. For the features listed above this is not so clear. So clarification would be appreciated. That being said. After reading back through mini updates thread, I appreciate the work that has gone into the Viper. A lot of what was mentioned in the mini updates and roadmap (and more) has been implemented. I trust development will continue steadily and perhaps hopefully accelerate after some large development items have been addressed. Thanks.

Ah I see, you are correct. The HMCS specific chapter indeed suggest the radar is only commanded to radiate when TMS-forward is released. What might cause the confusion is that the ACM specific chapter does not mention this behaviour. After testing I am also experiencing the stuck NO RAD in BORE Slave after an initial lock. So there are in fact two problems: Holding TMS Up in ACM BORE SLAVE doesn't command the radar to NO RAD After an initial acquisition then debugging and trying to acquire lock through ACM BORE SLAVE again, the radar remains stuck in 'NO RAD' and it doesn't acquire a lock @BIGNEWY @Lord Vader could you please take a look at this? The workaround to getting Bore Slave to work again is by pressing TMS Aft several times until in 10x60 NO RAD, then going back to bore by pressing TMS Up ACM_BORE_SLAVE.trk

It's in the -34. I am not sure I can share it due to rule 1.16. Additionally, ED marked the thread correct as is now. If you have conflicting documentation I suggest you send it to a CM

Okay, let me phrase it this way. TMS Up should not command NO RAD in any way. TMS Aft has that function.

TMS Up Long slaves the radar to the HMCS when equipped. NO RAD is not supposed to show up. This was fixed in the lates update and included in the changelog:

If you want to check whether targets have been upgraded to systems track correctly, you can press IFF OUT to get rid of any TNDL symbology. That will solve a lot of the confusion regarding if TMS Right should cycle or not.