diego999

Pretty much this. Will try the mod you mention. Thanks.

It can be used in fixed mode. If your CPU can take it, it's a great tool to gain performance.

How this map doesn't have soviet presence to simulate the Afghan-Soviet war is absurd. Same as Iraq not having iranian bases for some Iran-Iraq conflict missions. A map with a rich history and lots of possibilities reduced to bombing some insurgents in a Toyota. Come on.

There is a category or early warning radars for what you're trying to do. All these can perform the task you want.

It does nothing in my case. FPS seem to be limited by the headset, as long as you set the limiter above the native framerate you're using in VR (72 or 90 in most cases).

Put a piece of tape over the sensor between the lenses. Not very elegant but it does the job.

Quest 3 is the logical choice. It's a solid headset with a decent price which will be supported for several years.

A Q3 will never look as good and sharp as a monitor. You're trading visual quality for immersion.

Place your airplane over the airport you want to start from and select "takeoff from runway" on the right panel "TYPE" menu. If you want a cold start from the parking slot, select "takeoff from ramp" in the same menu. "takeoff from parking hot" does the same but the aircraft is already powered on and ready to go. In these cases you get an additional option to choose your parking spot.

Put 10 of these side to side in an airfield and you'll be looking at (very beautiful) single digit FPS. Screenshot simulator as you said.

I'd go for a 4070ti Super, those 16GB of VRAM look juicy for VR and you won't need a more porwerful PSU, but I think you should start considering a new PC entirely if you play in VR. I don't know if a 5950 (or a 5800x3d) are worth the upgrade. To know where the bottleneck is you should look at frametimes, not some online tool. I don't know what you're using but Open XR Toolkit or Oculus Tray Tool can show CPU and GPU frametimes in the headset while you're playing.

Turning engine anti-ice on? It's on the right side near the ejection seat arming control.

I bought all my planes and modules and now I should keep paying monthly to use them. Great idea my dude.

Did those two soldiers said something offensive? I don't know what I'm supposed to see.

1 - Yes. Just the link cable. Mine never goes below 85% or so with a generic $15 USB 3.0 cable. 2 - Never used hand tracking in DCS so I can't help you, but Q3's hand tracking is solid in general.

This is spot on. I don't think you can get better image quality than the Quest 3 for the same price, but it comes with its own set of drawbacks.

This is a question that can only be answered by yourself. You can't explain the VR experience, you have to try it. In my case, once I've tried there's no going back. If for some reason I can't play in VR anymore I will be leaving the game. The immersion is sensational, the feeling of sitting inside the cockpit cannot be compared to anything else, even if you're giving up some visual quality (as 2D will always look better than VR). Some people are not convinced and prefer 2D, and that's ok. There's no right or wrong here, play the way you like.

I did exactly that. Q3 is a logical evolution of the Q2. It's better in almost every sense, but it's not a massive 'omg I can't believe this' improvement. Still, it was worth it for me. Q3 pros: - Lenses. Clarity from edge to edge of the image. No more blurriness outside of the center sweet spot. This is the main difference. - Better sound. - Massively improved color passthrough (this isn't important in DCS, but still). - Better tracking (it started worse than the Q2 but it has improved over time). - Better resolution (cockpit is perfectly readable with PD 1.0, in Q2 I had to push the resolution to overcome the lacking definition / fresnel lenses. So Q3 looks better while pushing less pixels overall compared to Q2). Q3 cons: - Standard strap is atrocious. Very uncomfortable. - Battery comsumption is a little higher than Q2. A couple of weeks ago I plugged my old Q2 for the sake of nostalgia after 6 months of using the Q3. It was awful and I unplugged it again after five minutes. I'd say go for it.

Try replacing the cable. I've had crashes and disconnects when mine was on its last legs. You can try airlink to test if the problems remain. If it keeps crashing, then it's not the cable.

Mirage F1, Phantom, MiG-19, MiG-21, F-5, MiG-23, MiG-25, Su-22, Su-25. If you want to go with mods, A-4. All those are roughly balanced. You can add the F-14A but it would be much better than anything else, like it was in real life during that period. If you want to push to the late 80's you could add the Mirage 2000, F-15, F-18 and F-16 (without AMRAAMs), Su-27 and MiG-29 (without R-77 if you use the S version). For AI, avoid MiG-15 and MiG-21. Their AI flight model is broken unless you add some weight via scripting. F-5 is questionable too, and F1 is annoying in the sense it can fly with perfect control at minimum speed without stalling, in situations YOU flying that plane would drop down like a brick. The rest are decent. SA-2, SA-3 and SA-6 for the red side. Hawk for the blue. If you go into the 80's there are more modern systems, but they become too good for these older planes, at least in my preference. For AAA units, red side ZSU-23-4 and 57-2, M163 for blue. The 23-4 will absolutely murder anything that gets into range. I don't know how realistic is that, but is something to have in mind. You can add older artillery for variety, like the Bofors or the 100mm for the soviets.

Clarity and definition from edge to edge of the image triumphs over anything else the G2 might offer over the Quest 3, in my opinion.

In my experience, changing those values was always for the worse. Leave those settings as default. Meta software does a good enough job adjusting the numbers on its own.

If you're using a cable, try a different one. It might be on its last legs. If you're using air link, check your router for conectivity issues.

This is solid advice.

You have active radar missiles. He doesn't. If you go into a merge with a Tomcat against a Su-27, you're doing it wrong.