diego999

Yes definitely DCS looks better in a 2D monitor (unless you're using an expensive headset). What VR brings to the table is immersion: you're sitting inside the plane, and the feeling is amazing. But at the end of the day it's your game and you play it however you prefer. Nothing wrong with that. Maybe future VR headsets will solve most problems current ones have, heavy tweaking being one of them.

The Mirage F1 is not comparable to the Viper or the Strike Eagle. It's a 70's interceptor, designed to go straight and fast. Not a dogfighter but it can hold its ground against contemporaries as long as you remain fast. Relative to Fox 2 missiles: Magic 2 and AIM-9JULI are good, Magic 1 and the other Sidewinders range from mediocre to useless. Fox 1 missiles: 530F is somewhat decent, the others are pretty much dead weight (a lot of weight). The Mirage 2000 is a capable dogfighter, can maneuver much better and has as great radar and missiles. Being fbw, you can fly it in a careless way without worrying about stalling the engine or frying the avionics. You don't have that luxury in the F1.

Depends on the module really. In my country $80 is a lot. But I don't complain when it comes to, for example, the Hornet or the Viper (I own both actually). But those are complex machines with in-depth modeled systems and a lot of weapons. So there is much to learn and have fun with. On the other hand, $60 for the MB-339, an airplane that had no radar, no HUD, no navigation, no complex systems and with its whole arsenal consisting in a few bombs and rockets? Way too expensive. My 0.02

This. Syria map eats 25gb with you alone on the map. It goes downhill from there.

It does with a good one. I use a Kiwi cable. Never goes below 90% battery while playing.

Sounds like a cable issue. Had the same problem, but more severe (connection/disconnection ever 10 seconds or so). It went away once I got a better cable.

Yes. Your rig can handle VR, just not with max settings. Consistency is the key in VR. Steady 45fps are always better than, let's say, 72 but jumping all over the place. The effects can go from mild discomfort to vomiting over your keyboard. Everyone is different, you just need to find the settings your brain prefers. I can play no problem with interpolated frames at 36 "real" fps, but for other people that is unacceptable. Yeah, but no. You're sitting one meter away from your monitor, and when using your VR googles the screen is 2cm away from your eyes. I have a Quest 2 and while it has almost 1.5x the pixels of my 1080p monitor, the perceived quality is a lot less because it's almost glued to my eyes. I can read labels and instruments no problem, Quest 2 has 1,832×1,920 per eye (take that with a grain of salt). Index has a lower resolution, so I can't really answer. But in my non-expert opinion, you should go for a better headset. Your rig can handle it. EDIT: forgot to add, the only tricky instrument to read in VR for me is the Mirage F1's HUD (tiny numbers). But there are mods for that. Quest 3 comes next month. I'd wait to see what it offers.

Open Beta and Release are the exact same version right now: 2.8.7.42718

Glad I could help.

Went through the same headache couple of weeks ago. See this:

Strange. I can't spot anything wrong with your settings. And your PC should perform better with those specs. I've read some people reporting problems with windows 11. Did you have these issues with 10 too? MT or ST? Some have stutters with MT while ST runs fine. What I'd try to see if it makes any difference: Set in DCS: textures to med terrain textures to low visibility range to med terrain objects shadows to flat To access Open XT Toolkit, press ctrl+down while in game.

Your rig should be able to run VR at decent quality., but if you don't provide your settings (DCS, nvidia control panel and Oculus) we can't help you. It could be 100 different things.

I expect the Quest 3 to be better than the 2 with a reasonable price. Nothing more.

Quest 3. I hope it brings great improvements over the Quest 2 which I own. Those expensive headsets look amazing but I honestly can't pay u$s 1000 or more for a gaming gadget. Not to mention the rig you need to support them.

Totally. That monster 4090 deserves a better headset.

Pico 4 seems to be kinda troublesome if you read what people are posting on the forum. Quest 2 is ok, but, as @Nighthawk 117 says, I would wait until Quest 3 arrives to see what it offers.

I've played for months in VR with a 2060 during 2.7 era. Low details and simple missions, yes, but it was playable. With the first 2.8 patch the loss of performance was so big that card wasn't good anymore. Mind you, that was less than a year ago. And now with 2.8.7 it looks like the 3060 is not enough either. At the rate DCS is burning through generations, by mid 2024 you're going to need a 6090 to play at decent fps.

Thank you for this mod. Just got the F-5 and some labels are barely readable in VR with the stock cockpit.

Yes, but if this trend continues you'll find the same problem again 6 months down the road. This is some kind of memory leak/bug ED has to fix on their own.

I'd suggest testing your settings in single player with simple missions. Servers will add some latency of their own, and with heavily scripted missions or a lot of units in the map you end up with a stutter fest, no matter how powerful your rig is.

Create a mission with an AI MiG-21 dogfighting another AI plane and watch it pulling 7-8-9 Gs sustained turns without even losing speed. Absolutely ridiculous. Sad thing is, the realistic flight model works very well. I've ripped my wings off while flying the MiG-21 trying to copy the maneuvers the AI MiG-21 does. If you wanna test against old soviet fighters, MiG-23 or MiG-19 performance is at least believable.

As Skatelliza says, you're most likely running into power problems. Your estimated power consumption (keyword: estimated) is close to your PSU max rating. A spike could send it above the limit and trigger a freeze or a restart.

Maybe this is what you're looking for?

The only blue screen in 6 years using windows 10 was when I got too greedy with memory latency. I didn't break anything, but the lesson was learned.

As the guys above said, there is no noticeable difference.