Tomcat84

Frederf is correct. This should not be happening. But from the other thread it seems like ED has reached the same conclusion so hopefully they will fix it soon.

Not in SIM. You have to keep count of your simulated loadout yourself. That’s why people sometimes end up firing a “WishRAAM” if they shoot one too many haha It will show time of flight indications etc though.

No he did not. It’s perfectly fine to fly around in SIM (as opposed to OFF). ARM is a different matter.

The blackout switch on the throttle (for those jets that have it) is not used to adjust exterior lighting but to turn off/on lights in the cockpit that are not compatible with NVGs. At least in the variants that I’m familiar with.

You are incorrect, sorry. It is in fact a TMS left.

That is definitely true. If you are looking at this indicator during you're idle boards defensive BFM break turn then you're doing it wrong :lol:

The same modification that installed the MIDS and made the MIDS LVT knob responsible for powering the TACAN should also have had the TACAN knob altered to remove the OFF label. So if a jet is being modeled with MIDS to power the TACAN, then Frederf is correct and the TACAN knob should not have an OFF label.

My information mentions that they appear during switching but only "momentarily". Momentarily is not defined though and I'm having a hard time remembering. I think it's like a fraction of a second when actuating the switch but I'm unsure.

Nineline has clarified for me that this is being looked into and that this forum will be renamed to make it more clear that they aren't ignoring our posts about this. Thanks!

I'm hearing that it is because all controller and input bugs go to this forum. Hopefully that means that it is on ED's radar for an adjustment in the (near) future.

Please read before you move this to the Controllers forum. There have been multiple threads reporting this in here and they have all been moved to the Controllers forum without any kind of acknowledgement like [REPORTED], [FIXED], [KNOWN] etc. This leads me to believe that you think it is an issue with our controllers but it is not, it is an incorrect modelling of the F-16 PVI by DCS. Right now this happens: - elevation rotary in neutral, elevation doesn't move. - move rotary to 2/3s up, elevation starts going up and up and up and just keeps going until you stop it by going back to center, then it stays where it is at that time, not moving anymore. What it should do: - elevation rotary in neutral, elevation is set to neutral setting - move rotary to 2/3s up, elevation goes 2/3s up and stops there. Move rotary back to center: elevation goes back to center. It needs to be an absolute axis rather than a relative. The position of the ANT ELEV axis should basically be tied directly to a set position of the antenna elevation. Please adjust this, or make it a toggleable option or something as this completely alters the philosophy of how to operate the F-16 radar (and not in a good way IMO). It is not our throttles that are wrong. Thanks, and keep up the good work!

(and the answer!) :)

Not sure why this was moved out of the F-16 bugs forum as this is incorrect behavior for the F-16 and is not the fault of the controller? I'm seeing the same issue.

MLUs took that long when they didn't have the EGI yet. After they got the EGI in the M5 upgrade about ten years ago the alignment time reduced to the 4 minutes. Alignment time is higher (about 5 minutes) if you get closer to the north pole. (higher Latitudes).

I do. I have no urgent need for TWS. What I need is a bullseye display somewhere in the FCR. IFF is nice but a working datalink would give way more SA and even without both you can be fine if you talk to people and don’t blindly start lobbing missiles.