Quip

Guys, this saved me in Liberation. It uses "dead" and even "crashed" and the outcome is anything but predictable or correct. Using "lost" solved it. I just have to manually edit dcs_liberation manually Thanks!

And now that one has had no love for over one year??

The wi-fi here is rock stable. It's something else messing up But I think that moving to SteamVR with VD is the way to go. I've been playing around with that today (got the same tip elsewhere) and it seems better. Thanks!

Quest 2-players... Does anyone use Airlink or are you all using Link cables? And if you're using Airlink, do you too experience problems with the Airlink dropping from time to time? When that happens, DCS isn't able to recapture the graphics and I end up having to quit the session. The Headset will start tracking etc again, and I can see the head movements on the PC monitor, but inside the VR the image is black. Anyone experiencing this and is there any way to get the game to "recapture" the graphics or to prevent this from happening at all? (Other games, such as MSFS, can recapture the gfx easily when this happens)

You guys that have this problem: Try turning back just _one_ setting in DCS and see if it helps you. I think I know what it is you're seeing. Let's try confirming it. Do this... Set "Textures" to Medium. Let me know if this helps.

I have a new problem plying on Quest 2 and 3080 gfx, win10, lots of RAM etc. I have only seen it in multiplayer games, but I have very little playtime in the latest openbeta so I can't be certain that it's only in MP or not. I get stable 36fps _entering_ the mission. I press F10 and then F1 I get 6-12 fps. So far I haven't been able to get out of this situation. So something's happening... I'm going to wager a bet. Lately in DCS, the F10 map is slow on initial load. It takes several seconds for it to load the textures (even in "2D mode"). But this is only true the first time you load it. Thereafter it stays cached (for the most part). I bet what's happening is that when you go to F10, the map debuffers the world and takes its place so to speak. So when you get back to F1, the game plays catch up, trying to reload the world but failing to. Partly because it just can't do it and partly because the F10 map is taking up its place in memory. This is a guess, but an educated guess and I wouldn't be surprised if at least part of this is true.

Yes, that helps for a while.

See here It's a real problem.

See here, is this the same?

Switch? Can you show me to an article or such as to what that switch is etc? So I haven't missed anything on my end. What card? And congrats!

That doesn't change or show anything. This is what's important. The game makes the GPU peak at 100% while at the same time drop power to 50%. It's only this game It's not only me I'm 90% certain this is due to how DCS uses the texture memory.

I don't know if you said this as an answer to my reply, but if you read my post you will see I say the same thing: it's only in DCS, and I can hapily run any other game at full draw on the gfx card without any similar problems.

I can push it to occur in the menu - but that takes really over-driving the gfx settings in the occulus and such. So I would answer "it's only in-game for me", as there is a limit to what you should expect to be possible in the first place.

Yup! Precisely! This is what I see too (although I didn't mention the re-projection errors as those are an artifact of the other problems. See here!! (Preferably, delete this thread and add it to mine? Also Uprate my post to make it visible) Edit: It's a good thing you're on a different VR set (I have Quest 2) and a slightly different Gfx card (even better than mine, I only have an RTX 3080). This proves it's not a VR kit or specific gfx card issue. PS: I'm sorry you have it too, but glad I'm not alone...

I suspect these two are related