MPK

Bug #1 If you cold start a jet when it is dark enough to need the red HUD, the HUD colour selection lever will be in the green position instead of the red position. To change the HUD to green you must pull, then push the lever. Bug #2 If you jettison the external fuel tanks during the flight, then do air to air refueling, the fuel gauge will stop at 16200 as expected but the tanker will never give the "refuelling complete" message.

I am not sure if this is a bug or intentional, but it seems that the "new contact" sound will interrupt the lock or missile warning sound. Shouldn't a missile warning always be the highest priority, followed by a lock, and the new contact sounds be the lowest priority?

No, F-14A, plus it also happens while landing, which is obviously idle throttle.

Could we get a way to have jester fix / realign INS after landing at a different airbase? This would be especially useful in multiplayer, as right now you have to get a fresh plane every sortie due to INS errors.

If I take off or land at Bassel Al Assad 17R/35L on the Syria map Jester says I am going too fast and that the CO is going to do things to my balls. It doesn't happen on the other runway (17L/35R).

Thank you!

I am not sure if this should be in the bugs section or if it is intentional .... Can Jester stop calling out speeds and bandit positions after the bandit is killed? I know that jester knows the enemy is dead because he calls it out, yet he keeps calling out the enemy position and my speed for quite a while after the fight is over. For example: "he is behind us" / "he is getting ready to fire" etc as the bandit is heading to the ground in flames. Also, a feature request in the jester menu ... is there a reason for the menu that replaces the BVR menu when a bandit is within visual range? I really hate that menu ... I have never used anything on it (I jettison tanks using the WVR menu, and break lock using the pilot lock on button). At the very least, can this menu please go away when the bandit you are fighting is dead? The first thing I want to do after killing an enemy is reset the radar range / elevation etc but it takes extra effort to navigate to the BVR menu (and even worse, all the options on the BVR menu have moved position). Thank you!

I just tried today's patch and performance is significantly improved for me compared to the initial 2.8 release. I have clouds low, shadows low, secondary shadows off, terrain shadows off in case that makes any difference

Is this today's patch? Version DCS 2.8.0.32235.1?

This is the F/A-18 free flight Caucuses mission: This is multiplayer on a full 4YA server on the ground at Ramat David on the Syria map, waiting to take off: The situation got slightly better when airborne but not by much. The average frame rate was enough to maintain 45 fps with motion smoothing but the stuttering was nausea inducing. Settings that look like ass to try and get a stutter free experience in multi player: I think I have spent more time tweaking settings than playing the game over the last 2 years since I got my headset (Valve index). This is the only game I have that doesn't run well. I am feeling pretty frustrated with the lack of progress improving performance in this game. It might be time to take a break for a while until Vulkan / multicore / heat death of the universe happens.

I have been working out that a large cause of stuttering for me is running out of video memory, particularly in multiplayer. The alleviate this, I would like the option to force all other player and AI planes to be rendered on my client with the default skin for that aircraft, to save on video memory. Thanks.

This is the second DCS bug I ever noticed when I started with the game during Hornet early access (the first being that heat blur on other planes affects your hud). I was getting locked on the ground on Georgia At War at Krasnodar when the nearest enemy was 250+ miles away near Beslan, according to the web GCI page. Here is a 3 year old thread on the issue: Even then, people were saying it was an old bug. This will NEVER be fixed.

I just tried this with the latest (497.09) drivers. I do not get the "NIS" on screen when DCS is running. This is testing in 2D mode with a monitor. Either it doesn't work with DCS or it doesn't like my hardware (2080 super). Has anyone got this to actually activate with DCS?

In the hornet, if you are in AG mode with a bomb selected and configured for CCIP release mode then designate the waypoint as a target, the HUD symbology switches to CCRP. I am not a real hornet pilot, but I feel that this must be a bug. If I configure CCIP, it should stay CCIP until I configure another release mode. Having it switch automatically every time "target designate" is selected is so inconvenient that I cannot believe the real jet would do this. Another hint that this might be a bug: the configured mode on the MFD still says CCIP:

Your message triggered something in my brain, and I remembered reading this article about them: https://www.thedrive.com/the-war-zone/7099/__trashed-9

Working well so far! I just finished the "Training day - the LANTIRN pod" mission ... very cool, and I normally hate scripted missions One question though: when hitting the targets at the start of the mission, switching the bottom screen in the front seat to the TID showed blank, which matched what Redkite said would happen in his vid. However, after hitting the tanker, the bottom screen showed the normal A/G radar mode. Is this a bug? Did jester forget to turn the TID to TV/FLIR mode in the second half of the mission, even though he was still clearly using the pod? For reference, I switched to A/A mode to find the tanker and jester (or the system) definitely switched the display from the LANTIRN to the camera. It is when I went back to A/G mode that this happened.

This looks significantly more intense than what we currently have: From the 0:12 second mark of this video:

Should you have to re-box it every time you enter nav mode though? My understanding was that when you re-enter nav mode, it will still be boxed.

After boxing "Climb" on the FPAS screen, switch master modes then switch back (for example, toggle A/A mode on and off). Go back to the FPAS page and "Climb" is now unboxed. This started happening with the last patch.

That makes sense, however the spikes in CPU times are new in 2.7 for me, so I am sure something can be done about it.

I posted this in the SRS topic in "Mods and Apps" but I decided I should post it here as well. Unfortunately, I am one of the players who has been negatively impacted by performance in 2.7 in VR, specifically stuttering caused by spikes in CPU frame times. This is especially bad when joining any multiplayer server. Every 1.5 to 2 seconds I see a spike in CPU frame time. Here is an example using the F-14 caucases take off instant action mission: This is a freshly repaired install of DCS with no mods other than SRS. The issue is clearly visible on the CPU graph. If I do anything more strenuous than fly around in an empty mission, especially joining a multiplayer server, these spikes are enough to cause a visible stutter in the headset every 2 seconds. It has made VR unplayable for me, especially online. I have been experimenting with settings in DCS, NVidia control panel, Process Lasso, enabling and disabling various mods etc and I think I have finally tracked down the source of my issues. It seem that my problem is related to the Exports.lua file found in Saved Games\DCS.openbeta\Scripts. My Exports.lua file just has a single line related to SRS: pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil); I have discovered that if I delete the Exports.lua file the issue goes away: Not only are the spikes in CPU frame time gone, but the average CPU frame time is 1 - 2 ms lower. The headset was on the table in the same position for both test runs, all settings were the same, and the applications running in the background in windows was identical in each case. The only difference was the deleted Export.lua file. As a test I tried joining one of the hoggit servers with Export.lua deleted and 90% of the stutters in VR are gone. Note that these stutters happen even when SRS is not actually running, just having the entry in the Export.lua file is enough to cause them.

I just discovered this thread. I am having the same issue with Export.lua / SRS: https://forums.eagle.ru/topic/142491-dcs-simpleradio-standalone/page/116/?tab=comments#comment-4657461

Hi Ciribob, Firstly, thank you so much for creating this great add on. It absolutely transforms the experience in multiplayer servers! Unfortunately, I am one of the players who has been negatively impacted by performance in 2.7 in VR, specifially stuttering caused by spikes in CPU frame times. This is especially bad when joining any multiplayer server. Every 1.5 to 2 seconds I see a spike in CPU frame time. Here is an example using the F-14 caucases take off instant action mission: This is a freshly repaired install of DCS with no mods other than SRS. The issue is clearly visible on the CPU graph. If I do anything more strenuous than fly around in an empty mission, especially joining a multiplayer server, these spikes are enough to cause a visible stutter in the headset every 2 seconds. It has made VR unplayable for me, especially online. I have been experimenting with settings in DCS, NVidia control panel, Process Lasso, enabling and disabling various mods etc and I think I have finally tracked down the source of my issues. It seem that my problem is related to the Exports.lua file found in Saved Games\DCS.openbeta\Scripts. My Exports.lua file just has a single line related to SRS: pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil); I have discovered that if I delete the Exports.lua file the issue goes away: Not only are the spikes in CPU frame time gone, but the average CPU frame time is 1 - 2 ms lower. The headset was on the table in the same position for both test runs, all settings were the same, and the applications running in the background in windows was identical in each case. The only difference was the deleted Export.lua file. As a test I tried joining one of the hoggit servers tonight with Export.lua deleted and 90% of the stutters in VR are gone. I have no idea whether this is an SRS issue or a general DCS issue, but I am posting here since the only thing in my Exports.lua file was for SRS. Is there anything that I as a player can do about this, or am I stuck waiting for DCS or SRS code changes to address this issue?

I tested this tonight and I can 100% confirm that with the settings in your screenshots anisotropic filtering is forced off. You must set it to "Application controlled" in the nvidia control panel to allow it. The easiest test is to try to see the carrier centreline from a mile away. It is a blurry mess with it off and it is nice and clear with it set to a high value. Also what are the conditions that you are testing under? If I fly around in an empty world I get acceptable framerates and no stuttering. If I join a multiplayer server, particularly one with a lot of AI units like the hoggit GAW/PAW servers I get a worse frame rate but the real issue is horrific stuttering due to spikes in the CPU frame time.

In the NVIDIA settings you have "Anisotropic Filtering" set of "Off" instead of "Application controlled", then in DCS you have it enabled. Does this enable or disable it? It seems like those two settings conflict.