Sarowa

Yes, given that you're trying to simulate the F-5 as accurately as possible and this sounds like the most accurate behavior, it makes sense to implement. To clarify, it sounds like the new growl conditions are: There is an aim9 on the wingtip The GUNS MSL & CAMR switch is Up/active The EXTERNAL STORES switch is SAFE The SELECT JETTISON switch is OFF Is this correct? Should the volume control be able to silence the growl? My personal preference is for the aim9 to only growl when it's possible for the aim9 to launch and track, but it seems this is at odds with accurate F-5 modeling.

nairb121's post above seems to indicate the current DCS F-5's SELECT JETTISON switch behavior is erroneous. It seems the aim9 growl should be silenced when the SELECT JETTISON switch is out of the OFF position. In other words, it seems the aim9 should growl ONLY if ALL the following conditions are met: There is an aim9 on the wingtip The relevant wingtip Armament Position Selector Switch is Up/active The GUNS MSL & CAMR switch is Up/active The EXTERNAL STORES switch is SAFE The SELECT JETTISON switch is OFF <--- ***key point of discussion here*** Do you agree? If so, are there plans fix this? It's probably no coincidence these are (mostly?*) the same conditions required to fire an aim9 using the Weapon Release button on the flight stick. *I think actually firing also requires the landing gear to be up?

This has always been one of my biggest complaints regarding wing rip in the f5. I'm okay with there being some kind of failure mode, but the lack of feedback as you approach the point of wing rip is very frustrating. This feedback is something I feel Heatblur's Tomcat does well in contrast with a lot of other DCS modules. If the f5 wing rip is here to stay, I'd like to see both wing rip and approaching wing rip feedback applied consistently across all DCS modules.

Actually the sound is the last unresolved part. Can you please confirm, is it expected for the aim9 to continue growling when the Select Jettison switch is up or down (not centered), as I showed in my track?

This seems to confirm the Select Jettison switch in Select Position or All Pylons is intended to inhibit the Weapon Release button for all weapons. Thanks! Maybe someone at ED knows for certain whether it should also silence the growl? Like nairb121 mentions, you can jettison aim9s, but the way the f5 does this is by launching them, and only with the Select Jettison switch in Select Position. You cannot jettison aim9s with this switch in the All Pylons position. To jettison the aim9: Activate one/both wingtip Armament Position Selector switches (up) Move the Select Jettison switch to Select Position (up) Hold the red Jettison Push Button If both wingtip Armament Position Selector switches are active, both aim9s launch at the same time

No, this is a different switch. I'm talking about the Jettison Select switch. Please see the attached track as requested: In the track, you can see the wingtip Armament Position Selector Switches are active (up). When I put the Select Jettison switch into Select Position (up), the aim9 continues to growl. When I hold the Weapon Release button, the aim9 does not fire. Likewise with the Select Jettison switch in All Pylons (down). When I put the Select Jettison switch into Off (center) and hold the Weapon Release button, the aim9 fires. Is it expected for the aim9 to continue growling when the Select Jettison switch is up or down (not centered)? Is it expected for the aim9 to be unable to fire when the Select Jettison switch is up or down (not centered)? (Courtesy of Chuck's Guide) f5-jettison-switch-missile-fire-test.trk

It looks like this now gives the pilot a good indication of when they cannot fire an aim9 due to switch configuration, with one exception: At the moment, having the Select Jettison switch in Select Position or All Pylons inhibits firing the aim9. However, the aim9 growls in all Select Jettison switch positions. Is this Select Jettison switch supposed to inhibit firing the aim9 in Select Position or All Pylons? If so, is the aim9 supposed to continue growling?

There's also this one. It seems like the f5 RWR (and other similar RWRs) isn't prioritizing missile launch warnings.

Probably not. Tim probably has some data floating around indicating the tailrotor isn't producing enough thrust, among other things. If I understand correctly, ED is working with Tim to adjust things further.

Here are a couple tracks collected by the Enigma Cold War (ECW) community. One is the control, Launch_Warning_Test_No_Radars.trk. It has no other radars besides the MiG-21 and we see the expected behavior. The target's RWR gives a launch warning. The other, Launch_Warning_Test_Radars.trk, has many radars that seem to saturate the RWR, causing the MiG-21 launching an R-3R to not trigger a launch warning on the target's RWR. Launch_Warning_Test_Radar.trk Launch_Warning_Test_No_Radars.trk

I disagree that RWR deadzones are the issue. In all the cases I've seen of this bug, the r3r was well within the RWR field of view. There do not appear to be any lateral or longitudinal deadzones, only vertical.

I was aware of the lack of lock warning. The lack of launch warning appears to be new, or at least a new exploit.

I was in the F-5 with my RWR's "Search" mode off. When "Search" mode is off, the F-5's RWR normally shows all radar-guided launch warnings, both visually and aurally. I'm well attuned to the launch warning sound. This MiG-21 was off my nose roughly co-altitude, clearly not in any RWR blind spot above or below me. The only warning I got was the smoke, at which point even an 8g pull was not enough to avoid the R-3R missile. I heard reports of similar experiences from other players in the A-10 and A-4. EDIT: See tracks in this post:

Are you trying to arm the plane during autostart?

A lot of what you describe as gameplay you enjoy is what happens on the server you seem to despise. Pairing up with some friends doing SEAD/DEAD and then going in yourself, under escort cover, to take out the main target is a thing that happens regularly on ECW.

Don't try to center the ball in the DCS Huey. The ball doesn't work right. You want it to look something like this in the DCS Huey.

As far as I can tell, the recent huey engine model changes were largely in response to Tim's earlier thread about the DCS huey not matching up with the real huey data: Please also see Tim's even older thread about the DCS huey's tailrotor:

Check the charts in Tim's thread, specifically the one at the top of the first post. tl;dr: Compared to the real huey, the DCS huey is underperforming at 100 ktas and above. The DCS huey is performing about right at 80-90 ktas. The DCS huey is overfperforming around 60 ktas, which means as you slow down, you need less torque than the real huey to maintain level flight. As you slow to 50 ktas and below, the DCS huey starts underperforming, meaning you need to increase torque even more than the real huey as the speed comes off. This makes for very awkward and dramatic collective changes during landing.

It's specifically mentioned in the patch notes. I managed to fly for quite a while the other day. Tim also updated the data in his thread and the fuel consumption seems much closer to the real world data. So it seems like it's fixed.

How about removing dots entirely and instead moving toward a dynamic scaling solution?

Updating the game probably overwrote your dots.fx. You need to re-add the mod file.

The F-5E turns better than the Mirage F1, AFAIK. The F-5E also has much better visibility. It can land on a carrier in a pinch.

Maybe people in this thead should specify which Mirage they're referring to: Mirage 2000 or Mirage F1.

If you scroll 2 posts above the one you quoted you'll see I'm aware this bug occurs without the mod.