dugite57

Because I "fly" in VR, I thouight it would be great to map the 3 cooling flap sliders to my logitech Flight Throttle Quadrant. Hower I can't do it as they are not listed as axis. Is there a fix for this or am I snookered? Thanks

Doh, I worked it out. I added on extra flight and you need to wait for the initial flight to take off then it spawns. Patience

I've been trying to make the single player F4u mission multiplayer. I've had no success. Turning the second plane in the players Uzi flight from AI to Client does not work. I end up in a map view. I assume it's got something to do with the flight's timing delay, but have no clue how to fix it. Has anyone managed to do this yet? Any tips appreciated.

Meta did a link software uipdate this morning. V67.xxx. When trying to start DCS in VR it crashes. and sends ED the reports. I can start it in 2D no problem.dcs.log-20240730-053721.zipdcs.log-20240730-053721.zipdcs.log-20240730-053721.zip

Same here. I only use VR quest 3. After patching I started game and as soon as I was in the cockpit I got OpenXR prompting me and I notioced my setings had reverted to default. Fixed that up and noticed game was stuttering. Saw thread on redit and disabled the lauicher. Started game fropm, desktop shortcut to MT exe and no stutters. I'm amazed they never picked this up in testing. PC's 4090, 7800x3d, 64GB@6000 and NVME drives.

Before I hose my open XR based settings, will the MT native Oculus API likely improve performance etc? I'm using 7800X3D and 4090 Quest 3 while the second copilot's PC is an old 4770k with RTX2080 Quest 2. Both use the MT dcs.exe. Thanks in advance.

It's a crying shame they are unable or worse unwilling to do a hot fix. I have spent too many hours getting DCS to run how I want it to run on my two PC's (one Q3 and one Q2) to risk hosing it by trying the various workarounds. Having disappointed customers is never good for any business, even if we are ignorable due low numbers (which I suspect is not correct as we're probably only the tip of the iceberg)

This is a well known issue and ED are including the fix in a patch on Wednesdqay 4th April. Why they did'nt put a message up on their DCS site is beyond comprhension as it would have avoided a lot of Meta/Quest users a lot of grief,,,

It's easy to invest a lot in ED over many years. I've got two accoints so as I can fly two up in VR. It's Easter Holidays and I'm unable to play. Leaves a very bad taste and I am, to put it mildly, very dissappointed. It's not ok to not release a hot fix just because of with some inflexible corporate patch regimen.

The games working fine in VR, but crashes when you take it off is a common problem. It got hosed in one of the meta or DCS updates some time ago. There's a big thread on it somewhere.I overcome this by fiting a bit of sticky note paper over the "face sensor", this enables me to take a break without crashing the game. Just remeber to take it off when finished or else the headset won't shut down.

yeah, not happy, ED should have put the customer first and put out a hot fix.

Some feedback. So I got the 2 x 32 sticks of Adata 6000 C30.40.40.76 stuff and replaced the 2 x 16 sticks of G,Skill 6000 C36 with it. Expo1 set it to C36, Expo2 set it to C30.40.40.76 6000 as "advertised". PC has run faultless since mainly using DCS. My most subjective "test" mission is the Instant mission HUEY Syria Free Flioght over Beruit, I fly towards the centre of town, do a couple of loops around the big places of worship and go land on the Hospital helipad. The jump up to 64gb @ C30 6000hz removed the last of the stutters for me. The stutters were actualy worse with 4 x 16 (but the bios would set it a 3600hz and so I got smoother results vs 4x16 = 64 when I extracted 2 sticks and ran it at 32gb 6000 c36. So I'm very happy with the result of moving to 2 x 32 6000 c30. I'm also running it in VR link cable Quest 3. System's a 7800X3D Asus Tuif Gaming X670E-Plus Wifi and a RTX4090

Great, thanks very much for the advice.

So after my 4 sticks debacle and in order to feed the insatiable DCS beast, I've decided to go from 32gb 2 x 16 to 64gb 2 x 32. MB is an Asus X6760E-Plus Wifi. CPU 7800X3D. I've looked at the QVL and before I take the leap I'd like some advice on whats the fastest from the selections below. It's the timmings that I'm vauge on. ADATA AX5U6000C3032G-DCLARWH 2x 32GB XMP/EXPO 6000 6000 DS Hynix A 30-40-40-76 1.35 G.SKILL F5-6000J3238G32GX2-TZ5N 2x 32GB EXPO 6000 6000 DS SK Hynix 32-38-38-96 1.4 KINGSTON KF560C36BBEAK2-64 2x 32GB XMP/EXPO 6000 6000 DS HYNIX A 36-38-38-80 1.35 If anyone knows of something else out there that is better and works on this mobo I'd be happy to consider it. Thanks in advance

1 - The memory is: Two of G.Skill 32gb kit {2x16) DDR5 Trident Z5 Neo AMD EXPO RGB C36 6000mhz. Serial numbers of both kits were pretty close for whatever that's worth. My understanding is you can't by 4 stick kits of EXPO at this stage. 2 - Yes the PC shop I got it from sold me a pup with regards to RAM. My dealings and experience with the joint were probably the worst consumer experience I've had. 3 - Set ram to 3600 and I get DCS stutters. Set ram to 6000 and I don't. This is in VR. It's probably fine in 2d. 4 - So, for those who don't want to spend untold time tweeking and going up blind alleys, who simply want to hit EXPO and have it work, who are not expert memory tweekers etc, I strongly recomend 2 sticks. I do intend going back to 64 gig but will be doing it with 2 x 32gig kit. Yes, I know some can get 4 sticks running sweet. My recomendation is for those who don't want to have the potential hassels associated with setting up 4 sticks.