ssamayoa

Same here: This happens getting into busy server (actually I only play in 4ya). I will try your solution.

Someone using this in late 2024 with latest DCS? or is abandonware?

1000s of hours have been spent to get what we currently have then move thousands of lines of code in C, C++, LUA and who knows what else languages to rust just because? That would cost MILLIONS of dollars, QA nightmare, hundreds (more likely thousands) of new bugs and lost revenue - those adventures proven to be companies' killers! If you are in application development business I recommend you two books: - The mythical man-month - In Search of Stupidity - Over 20 Years of High-Tech Marketing Disasters

If you remove your headset even for a fraction of a second (scratch your forehead for example) the game stuck. Or image you are in a multiplayer server, land to rest for few minutes or need to go to the bathroom - impossible! That happens with Quest 2 and 3 with cable and airlink, maybe same fate on other devices.

Did you mapped in "UI layer" > "toggle VR Zoom"? I don't quite understand your complaint.

I want a clickable F-15C. No need to be FF, just clickable because I fly with VR. Because of that I skip low fidelity planes.

Looks like I bumped with the same problem. Did you resolved it?

Hi I have been using Wingwin F-16EX for almost a year now flying mostly F-18 and wondering for what are you using them.

UPDATE I installed Intel's PresentMon then with this config (most relevant to GPU): Antialias DLAA Textures: High Terrain Textures: High Shadows: Flat Only Visibility Range: High (I hear that for VR Medium is enough) Lens Effect: Flare Heat Blur: Low OpenXR Toolkit: Turbo mode ON Quest 3 at native resolution: 4128 x 2208 @72 Hz I connected to 4YA with +/-15 additional users and get 60 - 72 fps in the base then ~72 fps on air even near land. The data collected by PresentMon was interesting: Average CPU usage: 55% (from time to time small shuttering with DCS's FPS showing "CPU bound") Average GPU usage: 90% taxing and takeoff, 80% flying So, it looks like I need to get a better GPU to be able to use a Pimax Crystal Light with my current rig BTW instead of Airlink I used USB cable: In the past I tried to use it but was simply awful, looks that they fixed whatever bad it had and now works well. BOTTOM LINE: Intel's PresentMon is what I was looking for.

What's that? The FPS counter? If so, how to interpret it. TIA.

Hi, I'm disappointed with the performance of DCS in my rig and before investing on new one I would like to know what component the bottleneck is, my rig specs: i7 11770k Asus B560-plus-Wifi 64G 3200 Nvidia 4070 OC DCS is installed in m2 PCIe 3 Quest 3 at 72Hz native resolution connected via Airlink Dedicated Wifi 6 router (TP-Link Archer AX21) connected to the rig Sometimes I see the Meta Link´s sand clock: is the CPU holding everything compressing? Is the network card? Is the GPU? Is DCS? I already use OpenXR Toolkit with "Turbo Mode" on. And yes, even tho I'm still a lousy pilot I play mostly on 4YA servers. There is some Software that can monitor while I'm playing then give me the status of the components? Some help appreciated. PD: I may change Quest 3 for a Pimax Crystal Light but I'm afraid my rig will not handle it.

I started to use F-86 again (not precisely that I'm an expert) and bump with this issue: very easy to blackout and last forever! Is correctly modeled?

4YA acrobatic has VC enabled. I can hear other players but when I try PPT nobody can hear me. Mic test passes - I can hear myself. "VoiceChat push-to-talk mic. mode: On/Off voice transfer" is set to joystick button, I can see when I press the button the green border but nothing FWIW attached my last flight. dcs.log

I thought to do something as you did but hoped that there is a less "low tech" This problem is very annoying! BTW happens also with Quest 3 with or without OpenXR Toolkit with cable or airlink.

I ran a repair, it was very quick but seems to fixed whatever was the problem. And for any doubt, I created a new shortcut with --force_OpenXR (according to the log already started on OpenXR ) Thanks for your support, these last weeks have been little frustrating because the problem introduced by meta so I guess I had no more patience left to figure out by mylself.

Yep, as I said I can see in the device the hangar for a second then then exits. Note that the hangar is rendered without textures. Maybe is not v63 related problem

According to changelog the problem with Meta link v63 should be resolved but is not I can see briefly the hangar with missing textures then quit. Frustrating... FWIW I'm attaching log file. dcs.log

Takes a couple of mins then your browser should download. Check your downloads folder

I know that is not ED's fault and the best you can do is apologize but please, provide a date! One week from today? Two weeks? One month? Not giving a date feels like a lack of commitment even tho I'm pretty sure QA guys/gals are doing their best.

Note that the google drive files are here: https://www.reddit.com/r/dcsworld/comments/1bnspf6/recent_oculus_vr_bug_fix/?utm_source=share&utm_medium=web2x&context=3

Meta Quest Link v64? How you get it?

I was chasing Oculus PC v63 because supposedly it fixed some issues including the annoying "your computer..." but lucky I found this thread then disabled auto updates. Thanks guys!