mkel2010

My exact experience with this MB/CPU combo.

I just built a very similar system using the same CPU and motherboard (I'm using the Ryujin 360 Water Cooler, 96GB of RAM and a RTX 5070 Ti OC.) I had a hell of a time getting the motherboard working correctly at first. The first board had to be returned because a of a memory slot issue. The second board initially gave me CPU errors which I later determined was caused by an older BIOS that came with the board. I had to flash the BIOS three or four times to finally get everything working correctly. I have not changed any settings to memory or CPU overclocking and my CPU at idle is running about 43 degrees Centigrade. When I load a mission or start DCS it might briefly spike up to the mid 70s and then drop back down for the rest of the session. I would suggest re-flashing the BIOS with the system shut down and see if that changes anything.

That seems to have fixed it. Thanks.

@cfrag I used DML to create an air to air training mission today. Before doing so I downloaded the latest version of DML. When I started testing my work, the Clone Zone routine started generating the error pictured below. After spending some time trying to figure out what the error was (and not having any success,) I switched the Clone Zone routine to version 2.4.0. That fixed the error and the mission works. Just passing on the information.

For some reason, the mod is not saving the options I've selected. For example, activating the Color Change requires a game restart. I've used the save at the bottom of the add-on as well as the preset save button on the home tab. However, when I restart the game none of the options are saved. I did test with your options.lua file and get the same behavior. I've attached the log file. Let me know if you need anything else. ReShade.log

That was the first thing I checked: Anderson AFB frequency is 250.1 which is what the mission set for Comm 1. The most recent version of the mission is from this month, I believe.

Getting back into DCS after almost a year off. I'm using the latest versions of VoiceAttack and Vaicom Pro which seem to work correctly on other missions/maps. However, when I fly the F-16 on either of the Marianas Proving Ground Missions, I can't get a response from ATC either on the ground or in the air. I have the main DCS menu set to Easy Comms off. I've tried initiating calls to start engines, taxi, take off, etc. from both the menu options and using Vaicom Pro. I get "my" voice repeating the command, but never get a response. I initially thought my version might be out of date so I downloaded the newest version and get the same behavior. Any ideas how to fix this?

F-16 Lesson 13 - Air-Air TWS and TNDL Use only progresses as far as the first set of targets for the TWS portion of the lesson. Once those targets are shot down, the next part of the lesson never appears. I flew it twice with the same result. The Track file is from the second time through. Lesson 13 - Air-Air TWS and TNDL Use.miz_14082025_14-28.trk

I think I've resolved the issue by switching to MSAAx2 and turning off DLSS. The only things Ive set inside the NVIDIA control panel are the power setting to Performance and prerendering 3 frames. I'm using Virtual Desktop to connect. And yes, the Gamma slider does react in-game. With the changes I made today, the HUD colors are now consistent regardless of the background.

1 & 3: Meta Quest 3 (VR) 2: New system, but I had a similar issue on the old system with a RTX 3060 Ti card. On the old system, resetting Gamma pretty much took care of of it.

I built a new system for playing DCS in VR which incudes an RTX 5070 Ti OC graphics card. When flying in the F16 and there are clouds/haze in the background, I find the HUD colors to be washed out and difficult to see. I've played with the Gamma setting (currently at 1.3) and while it helps, it really darkens everything else. Are there any other settings in VR that can address this issue?

The only Winwing base that is force sensing is the MFSSB base; the Orion II base is the analog base. The shaker kit is meant to give feedback through the stick when you're pulling Gs, firing ordinance, landing, etc. I've had the Orion II base with the F16EX grip without the shaker kit for awhile. I recently got the shaker kit and had the same question about getting it to work. The video below explains how to get it to work about half way through. Basically, you have to have SimApp Pro running, go to the Dynamic Vibration Motor page and chose the game and aircraft. On the Game icon there is a Settings option. Click on that and you get a window that lets you chose Default or Advanced. Default gives you basic shaker behavior while advanced allows you access to downloading other profiles from users or creating a new one on your own. I ended up using a profile uploaded by Reflected. Once downloaded, you will have a run button and three dots. The three dots will open another window with an Edit tab. This allows you to adjust the settings. I haven't a clue what the best settings are. You'll find that the shaker is very subtle. It's not going to even come close to vibrating the stick out of your hand. Unless you have the MFSSB base, set the settings in the Special menu to on and the dead zones to Zero. If you need dead zones for the Orion base, set them in the Controls section.

I'm not sure how I fixed the issue, but everything is working normally following the last DCS update as well as a Windows 11 update.

I'm not sure. I believe the dead zone settings on the Special Menu are for the MFSS version of the Winwing stick (or others with similar function.)

I've moved DCS to a new computer build, and updated to the latest DCS version as part of that process. On my old setup, I used HTCC in VR to provide hand tracking in game, but now the hand movements are confined to a small two by two area in the upper left corner of the menu screens. For example, on the Main DCS menu screen, any hand movements of the cursor are restricted to the D and C in DCS in the upper left corner of the window. The same goes for the Mission menu. Once in the game, the cursor appears to follow my eyes and is difficult to override with the actual mouse. If I turn off HTCC, then the cursor somewhat returns to normal behavior with the mouse being the controlling factor. If I switch to DCS' built in hand control, my hand movements appear on the screen but I can't manipulate any of the cockpit controls. I've looked at a couple of the tracks where this happens and nothing comes across in the track so I don't think that would be helpful. This did not happen in the earlier version so I believe something may have changed withe the update.

That CPU apparently has 24 PCie lanes, so coupled with the right motherboard, you should be able to have one nVMe and still take full advantage of 16 lanes for graphics. And with the AMD AM5 socket you'd be able to eventually upgrade the CPU without needing to change out the motherboard.

With the Intel chip you'll only get 20 PCie lanes versus 24 with the AMD chip. The number of PCie lanes in an important consideration, particularly with the video card you plan to use and any nVMe drives you plan. Depending on the motherboard and the configuration you chose, you could be in a situation where your video card is running at x8 vs x16 when coupled with nVMe drives. You're planning to spend money on a good video card so you don't want to box yourself into using half its capabilities at the very start (with the Intel chip.) An advantage to using the AMD chip is the motherboard socket. Intel boards change sockets every few years while AMD has stuck with the AM5 socket for a number of years and apparently has no plans to change it. What that boils down to is if you want to upgrade your CPU in a couple of years, you only need to buy the chip and not a whole system.

@talvikko These are the specs of the system I just built: Asus ROG X870E-E Gaming Wifi motherboard AMD Ryzen 9 9950 x3D Asus Tuf Gaming RTX5070 TI OC Edition G.Skill Flare X5 DDR5-6000(48GBx2) Asus Ruyjin III 360 (non-RGB model) Samsung 9100 Pro 2TB nVMe (I reused a case that I had, also with another nVMe and SSD drives.) The build was not without issues. I had to return the first motherboard due to a defective memory channel. I thought the second motherboard was also defective but it turned out that the BIOS didn't support either the CPU or the Memory. Fortunately the Asus motherboard BIOS can be flashed without needing to boot into the BIOS. Once I got that sorted out, everything else has gone fine. One of the reasons I went with this motherboard is its use of the PCie lanes. I wanted to keep the graphics card at x16 speed while also taking advantage of the PCie version 5 speed for the nVMe drive. This board has a specific slot for the nVMe drive that will allow it to run at x4 speeds and the graphics card to keep running at x16. These two slots go directly to the CPU; it has two other nVMe slots on the same channel and using either of those drops the graphics card slot to x8. Finally, the board has two more nVMe slots that run through the chipset and don't impact the CPU PCie channels. I saw no point in spending what I did for the graphics card and not be able to use its full capacity. One of the reasons that I went with AMD is the socket - AM5. Unlike Intel, AMD hasn't changed their sockets for awhile. That means you could by a cheaper CPU and then upgrade later without having to change anything else. As for the memory brand, I would decide on the motherboard first and then use the boards QVL (qualified vendor list) to choose your memory. Most of the major memory manufacturers also have a way to search their products for compatibility to a particular motherboard. I'd also suggest sticking to two sticks of memory. Modern systems sometimes have problems with more than that.

I just built a system that I'm still in the process of setting up. I went with 96GB of g.Skill RAM and an ASUS TUF RTX 5070 TI OC Edition graphics card. I haven't overclocked anything yet, but I ran a baseline on the graphics card and got a maximum frame rate of 214 with an average of 172 FPS. If you'd like the details on the rest of the system I built, I'm happy to provide them.

I believe the process would be: Export the bindings from DCS Controls Menu on the old computer, transfer the exported files to the new Computer and then import them from DCS Controls Menu on the new computer.

if you are both having a similar issue, I'd suggest joining the Virtual Desktop Discord and posting the issue there.

Do you have another program open on the desktop, underlying the area you've shown? I had a similar issue where I couldn't click menus (when I tried to click on a particular menu item I would get a Window Out of Focus error.) By reducing the window to the tray it resolved the problem. The other thing you could try is a complete repair of DCS through the Updater module to make sure you don't have a corrupted file somewhere.

In the Special menu, turn both to on and set the dead zones in that menu to Zero. Then in Axis tunings play around with a small dead zone for pitch and roll.

I found a post a few days ago that recommended turning both on, but setting the dead zone to zero on the Special menu page. Then setting a small dead zone for each axis in the Control section. I set a small, 3-5% dead zone on each axis and saw a noticeable improvement on mine.

I too have been interested in OpenXR Toolkit, but this advice on the Github site has stopped me; "AS OF 2024, SUPPORT FOR OPENXR TOOLKIT IS DISCONTINUED. THERE IS NO NEW DEVELOPMENT AND NO TECH SUPPORT OF ANY SORT. THE DEVELOPER DOES NOT RECOMMEND TO INSTALL/USE OPENXR TOOLKIT, AS IT IS KNOWN TO CAUSE ISSUES WITH MANY OF THE NEWER GAMES RELEASED IN SINCE 2024" Any comments on the above statement?