Aetherin

I'll share my experience on patch 2.9 here, since I'm affected by this issue. I'm based in western NA, and frequently play on EU-based servers. My ping to the servers in the server browser is what I'd expect (40-90ms in CONUS, 130-150ms connecting to EU servers) across the board. However, once I actually connect to the server, my displayed ping in the scoreboard essentially doubles from its value in the scoreboard. For example: Connecting NA->NA: ~70ms in the server browser, ~130ms in-game once connected to the server. Connecting NA->EU: ~145ms in the server browser, ~280ms in-game after connecting. As @dutchie_031 mentioned, this already creates issue with servers that have reasonable latency limits of, say, 350ms, as any spike in ping will easily cause my connection to exceed this value. Additionally, I have also seen the issue mentioned above about the latency spikes 'persisting' for a long time (even if the actual ping should already be back to normal), causing me to often get kicked from EU-based servers. Additionally, it seems like the ping displayed for other players changes when they reslot. Without having tested this properly, we have seen the pings of player B double and triple on player A's scoreboard when player B reslots.

Thank you so much. Adding a keybind for the keyboard in UI layer - recenter VR Headset (I did RCTL +RSHFT + RALT + Scroll lock) fixed the issue for me too. Removing the keyboard keybind for UI layer - recenter VR Headset causes the bug to reappear. As of patch 2.8.2.35632 Open Beta there must be a conflicting command not shown to the user for the UI layer - recenter VR Headset keyboard that takes over whenever the user leaves the command empty.

I am only experiencing the issue in VR, not in 2D without headtracking. I do not have any headtracking other than VR, so will need others to confirm that the issue does not persist for, e.g., TrackIR in 2D. No controls-related mods in use. There are no red exclamation point warnings next to any of the commands related to centering view in my "UI Layers", "General", and aircraft commands.

Thanks for your reply. My experience from yesterday is that NUM 5 is now hardcoded to recenter the VR view as of this current open beta patch. As you suggest and I also mentioned in my first post, I have removed every single keybind using NUM 5 from the categories "UI Layer", "General", as well as the appropriate aircraft (for me the F-16C), as well as removed every single recenter view command from the keyboard. The only command left is "recenter VR headset" under UI Layer bound to my HOTAS. Yet the issue still persists: pressing NUM 5 will recenter the VR view. This was not an issue in the prior patches. If I pressed NUM 5 while in VR, nothing would happen (except for, of course, any command I bound to NUM 5 myself such as the 5 key on the Viper ICP or the 5 key on the Apache KU).

Following patch 2.8.2.35632 Open Beta, pressing NUMPAD 5 will recenter VR view (same command as "recenter VR headset" under UI Layer), even if one unbinds all commands related to recentering view / recentering VR view from UI Layers, General, and the flown Aircraft. Using SteamVR as my current OpenXR runtime. I've been using my numerical keypad as keys for the ICP in the Viper and the KU in the Apache, but after today's patch am unable to do so since pressing NUM 5 will recenter my view even if I unbind all recenter view functions for the keyboard.

While I cannot answer that with certainty, the fact that ground crew will not refuel external tanks at all was present prior to this bug occurring. I believe that ground crew will not refuel ext. tanks for most aircraft in DCS? This is certainly a possibility. I will try playing around with getting the same fuel flow without bags (with a fast KC-130) as I do with two bags, and see if that changes things. I will say, though, that there were no issues with bags prior to patch 2.5.6.49798, and flying the same mission on the older patch and on patch 2.5.6.49798 or greater yields different results. Perhaps ED changed the flow logic for the F-15C in patch 2.5.6.49798, but then I believe it was not documented at all in the patch notes.

Apologies if this has been wished for in a previous post - I wasn't able to find a post by searching the forum. Would it be possible to implement a 3-position keybind for the Autopilot PITCH (ATT Hold <> A/P Off and ALT Hold <> A/P Off), as has already been done for Autopilot ROLL under the Special for Joystick category?

As of the open beta patch 2.7.11.22211 this bug is still present. If carrying any external fuel tanks on the player's F-15C, the KC-135 will not terminate the refueling process once the internal + external fuel tanks are full. The refueling process continues indefinitely. To this reply I attach several tracks that highlight this behavior for different configurations. If fuel tanks carried are jettisoned, it seems that the bug persists. Refueling_Clean_Normal_2022.trk Refueling_1Bag_Bugged_2022.trk Due to the attachment size limit of 5mb, I attach here a track for 2 external fuel tanks. Refueling_2Bags_Bugged_2022.trk

With the open beta patch 2.7.11.22041 that released March 30, the "Radio Listen Mode" (cycled by pressing RShift+M) is no longer functional. While the menu does cycle through the different options, of which "Radio Listen Mode: player communication" is the most important as it allows FC3 players to mute the AWACS automatic callouts, none of the modes are functional as of patch 2.7.11.22041. For multiplayer servers where there is more than one AWACS airborne (say, E-2D and E-3A), this makes FC3 modules unplayable due to the constant radio spam that cannot be muted. Attached is a simple track in which the non-functionality of the Radio Listen Mode is demonstrated. The track was recorded on the open beta patch 2.7.11.22041. Edit: I should mention that this feature was working in open beta patch 2.7.11.21408.1 and prior to that particular patch. Second edit: After re-reading the patch notes for open beta patch 2.7.11.22041, I am guessing that this is related to the bulletpoint "Fixed problem with not working human-AI radio communications for many aircraft" under "DCS World". Presumably something was changed that broke the "Radio Listen Mode". RadioListenMode_bugged.trk

As of patch 2.5.6.49798, if carrying external fuel tanks on the (player) F-15C, the KC-135 will not terminate the refueling process once the internal and external tanks are full. Instead, the refueling process continues indefinitely. If no external tanks are carried, the KC-135 will terminate the AAR once the Eagle's internal tanks are full. I have attached one track, 'Refueling_Clean_Normal.trk', highlighting expected behavior once the internal tanks are full, as well as two tracks, 'Refueling_2Bags_Bugged.trk' and 'Refueling_3Bags_Bugged.trk', which show the failure to terminate the refueling process when external fuel tanks are present. All tracks were recorded on patch 2.5.6.49718. Refueling_2Bags_Bugged.trk Refueling_3Bags_Bugged.trk Refueling_Clean_Normal.trk

The F-15's lights have definitely changed from the previous patch 2.5.6.47404 (and many patches before that) to patch 2.5.6.49314. Here are the changes that I've observed thus far: 1): External light control logic has changed. To be specific, in prior patches the keyboard shortcut RCTRL+L (labeled "Navigation Lights" under the category "Systems") has toggled navigation lights on/off. To toggle on/off the anti-collision lights, we had to press RCTRL+RALT+L (labeled "Anti-collision Lights" under the category "Systems"). The two were independent, and there were only two settings (on/off) for each. As of the current patch, navigation lights and anti-collision lights now follow a different 3-stage control logic on RCTRL+L: No external lights, navigation lights only, and navigation lights + anti-collision lights. I would guess that this new control logic originates in a different Flaming Cliffs 3 aircraft, perhaps the Su-25? Anti-collision lights may still be toggled with RCTRL+RALT+L. However, there's now an additional twist: If I press RCTRL+L twice, i.e. the F-15 now has both navigation lights and anti-collision lights turned on, and I THEN toggle the anti-collision lights off using RCTRL+RALT+L, the next press of RCTRL+L will NOT turn off the external lights but instead turn on the anti-collision lights (in addition to keeping the nav lights on). From my findings, the logic seems to be the following: There are four stages of lights: (A) no lights, (B) nav lights only, © nav lights + anti-coll lights, and (D) anti-coll lights only. RCTRL+L will switch (A)->(B), (B)->©, ©->(A), and (D)->©. Meanwhile, RCTRL+RALT+L will switch (A)->(D), (B)->©, and ©->(B). 2): Navigation light brightness has changed. As USA_Recon reports, the wingtip navigation lights are quite dim in this patch compared to the previous patch. I would say that the navigational light brightness is on par with what the Tomcat had prior to patch 2.5.6.49314, which IMO was unusable for anything. Navigation lights patch 2.5.6.47404: https://i.imgur.com/AnRb65F.png Navigation lights patch 2.5.6.49314: https://i.imgur.com/QxSNcAt.png 3): Navigation lights are now flashing. While their brightness is now heavily dimmed, the navigation lights are also flashing in patch 2.5.6.49314. In previous patches the navigation lights were steady. I have made a short video to highlight this change, although the dimness of the navigation lights makes it difficult to make out the flashing on YouTube: . Later in the video, I turn on the anti-collision lights by a second press of RCTRL+L, and then turn on the taxi and takeoff lights. For comparison, here are the patch 2.5.6.47404 lights: . 4): The taxi light model does not show the taxi light being active. When turning on the taxi light (RALT+L once), the taxi light illumination turns on (though with a changed illumination cone, see point 5 below), however the actual taxi light model does not show the light active. Taxi light patch 2.5.6.47404: https://i.imgur.com/ZFBxt1L.png Taxi light patch 2.5.6.49314: https://i.imgur.com/IQxk2Mm.png The difference can also be seen in both videos attached to point (3). The takeoff/landing light (mounted directly beneath the taxi light) does turn on when commanding takeoff/landing light (RALT+L twice from no lights). Takeoff/landing light patch 2.5.6.47404: https://i.imgur.com/Ak8mNbD.png Takeoff/landing light patch 2.5.6.49314: https://i.imgur.com/VTRuorR.png 5) Taxi light and takeoff/landing light illumination patterns have changed. In patch 2.5.6.47404 and prior, both the taxi and landing light illuminated a narrow cone in front of the airplane. This can be seen in both of the patch 2.5.6.47404 images above as well as my two videos. As of patch 2.5.6.49314, the takeoff/landing light has become an elongated spot in front of the airplane nose, while the taxi light is now a wide illumination cone. Both have also changed to a warmer (yellow-ish) white. For both lights, an 'additional' illumination cone is present on the ground at the nose wheel, as if an additional light source is mounted there. This additional light is visible in both patch 2.5.6.49314 pictures above and in the video. EDIT: I just noticed that when switching from taxi lights to takeoff/landing lights, the taxi light model will flash once during the transition. The same flash occurs when the takeoff/landing light is turned off.