mkel2010

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?

I just placed an order through the Winwing USA web site. The order had no added Tax. Are you sure you're not on the Global shipping site?

Right Hardpoint power on should be: LCtrl -LWin - W. Off is LShift - LWin - W.

@NIGHTHAWK1 I'm curious if you're using a link cable or Virtual desktop? I haven't been able to get hand controls to work well with either method, but Virtual Desktop seems to be a little better. I've been using HTCC but even that has detection issues with pinch control movements.

As far as I know, Virtual Desktop is through a wireless connection, regardless whether or not a link cable is used. The link cable in this situation will keep the headset charged and that's about it. That said, I came across the video linked below that describes how to hook the Quest 3 directly into a wired router and use Virtual Desktop. I just ordered what I need to try this so it will be next week before I know whether or not it will work.

Who makes the stand that you're using?

If DCS crashes, there should be files that end in .crash and .dmp. Otherwise. you should have a log file called DCS.log and dcs.log.old (the previous version of the last dcs.log file.) Both can also be opened by using Notepad++.

Have you checked for any crash logs in the Saved Games/Logs folder? I've recently had issues with DCS failing to load and found that it was another program causing an Access Violation error. The Logs can be opened with Notepad++.

Did you make sure your developer account setting are active?

Don't know if you're still having issues, but I was just able to get hand tracking working in DCS while connecting via link cable. First, in order to turn on the Devoloper Runtime Features, Meta - in their infinite wisdom - requires a Developer account. You can get the account either by setting up a business or by submitting ID verification. I chose the latter and it took about 48 hours to get back the approval. Second, I've found an app by the same developer who does Openkneeboard called Hand Tracked Cockpit Clicking (HTCC.) This app gives you a cursor in the cockpit for both hands (as long as you hand is visible to your headset cameras. You can then use finger gestures to flick switches and turn knobs. (It will take some getting used to.) If you go this route, make sure to read - and then re-read - the instructions for setting it up on the web site. If you need help, the developer has been very responsive through the Discord channel. Meta, and by extension DCS, certainly doesn't make this VR stuff plug and play. Link to HTCC: https://htcc.fredemmott.com/

What link cable are you using?

Is that something you can do with Virtual Desktop, or are you using the direct link? I'd love to know how to do that in Virtual Desktop (if it's even possible.)

Using Quest 3 and Virtual Desktop to connect to the PC and DCS. I've noticed that when I load a mission, I don't get any progress bar for the load screen and it seem to take much longer to load than 2D. Is this normal? I have an NVidia RTX 3060, a Core i9-129000K processor and 128GB of RAM. Latency in game seems to average about 70ms just sitting in the cockpit. The Quest 3 is connected to a dedicated router at a solid 2400 megabits per second. Are there settings that I can change to improve the latency?

I'm referring to the Meta Virtual Desktop App available on the Meta web site for $25. The site you linked to provides the streamer app for Meta's Virtual Desktop to operate and the authors on that web site likely wrote Virtual Desktop, but the app itself is not free. The streaming app from this site runs along side Meta Link on the PC and allow the headset to connect to the PC with Virtual Desktop.

I was finally able to get hand tracking within DCS to work. For anyone else going down this path, it is important to understand that hand tracking ONLY works in Meta's Virtual Desktop app; IT DOES NOT WORK when connecting directly to a computer via link cable or AirLink. Also, apparently it is important to create a Meta Developer account in order to activate Hand Tracking. All that is required for the account is identity verification and takes about 48 hours.

Plenty of YouTube videos show it does, going back at least a year.