diego999

Can you share your settings? I play with 45/90 fps with a 3060ti. Your 4090 should be capable of much more than that.

There's a real Mirage F1 manual on the internet (won't post any links here just in case) stating the ceiling is 55.000 ft. Maybe those specs are from later variants?

Can you post your settings? It's impossible to spot your issue with no info.

Seems like you forgot to put yourself on the plane, and set it for an AI flight. On the right panel, in the "skill" menu, you need to select the last option: "player", the one with yellow letters. That means you will fly the plane. The option for cold start is "take off from ramp". The option you selected was "take off from parking hot", that's why it started with the engines running.

This. Reducing the fov was the setting that gave me the most gains in performance.

You can totally play in VR with modest settings. I played for a year with a 2060 + Quest 2. It didn't look pretty but it was workable. And motion reprojection was a must (36/72 fps). You can lower the fov to gain some performance. At 0.85 you barely notice it. I used to play at 0.60. Waaay to low for most people but it made DCS playable for me. Try it and see how it goes.

Works for the Quest 2 as well. Thanks!

No problem man. Even ED didn't got the name right

Nice! It's "Veinticinco", spanish for twenty five. Full name of the carrier is "May 25th" in spanish.

Close my eyes to avoid vomiting, as the flickering in VR is worse than bad acid.

It looks like it's going to be better than the Quest 2 but no omg this is amazing better. Increased resolution, nice, getting rid of the fresnel lenses would be a great step in the right direction, $100 more than the Quest 2, ok I can live with that. Please add a better battery and fix the headstrap, feels like it's going to fall off your head constantly. We'll find out soon enough.

Getting comfortable playing in VR takes some time and brain training. First time I almost fell off my chair when I tried some maneuvers, and for some days after I would get dizzy after playing. After a month I got over that barrier and the discomfort was gone for good, but it ever goes away for some people. I think you had a severe mismatch between your VR gear and your PC. The Quest 2 is an entry level headset with modest capabilities (I have the same one). No matter how high you crank all the settings, it will never look amazing just because the Quest 2 doesn't have the resolution to achieve that. Your hardware is totally able to drive a much better headset like the Varjo Aero or the Pimax Crystal. You raise some valid points about VR, specially having to waste time trying all the setting combinations to achieve reasonable results. I spent a month doing that. It wasn't fun. In the end, it's your game and you play it however you prefer. You tried VR, didn't like it and went back to 2D. That's totally fine. Will try your suggestion.

True. There's a sweet spot for resolution/performance, depending on your particular combination of headset/GPU/CPU/RAM, where cranking up the res past that point doesn't offer any noticeable visual improvements, but can tank your framerate. For me it's around 1.25 super sampling in OTT. Maybe better headsets can take advantage of higher resolutions, but with my Quest 2 I can't tell the difference if that setting is higher.

It happens when you have modules on trial. See this thread:

It's just personal preference. With 36/72 you can crank up the settings and the game will look better, but the asw artifacts will "feel" worse. I run 45/90 as I prefer the smoothness, but most settings are on medium/low. Just try both and see which one your brain prefers.

I can't speak for the F-4 but in my experience the MiG-21 is the worst offender when it comes to AI ufo performance. And Ace level only adds more cheating.

What has worked for me is to ask Jester to use TCS, then ask him to use the pod again.

Joystick Gremlin. I use it to average out some jitter I have on my X52 throttle. Works very well. Disclaimer: I don't have a clue about how it works. I just followed a step by step tutorial on youtube once, almost a year ago.

What this guy says. Throwing new hardware at the game won't solve the poor performance (specially in VR) for now. Let's wait for further MT development and Vulkan.

Here's a visual representation of what these numbers do (not exact, I just drew some rectangles with Paint)

Description is wrong. It totally affects VR. Try setting both values to 0.50 and you'll feel like you're looking through a shoe box 0.0 is default afaik. With 0.85 you're rendering 85% of vertical/horizontal resolution (I don't know which is which, I set both numbers to the same value). Set "visual hud" option in OTT to "pixel density", so you can see how resolution changes as you modify the values. Remember you cannot edit those numbers "on the fly". You need to set them before connecting the headset through link/airlink.

Makes sense, but I agree it should be stated somewhere.

You can set it on the Oculus Tray Tool. One is for the horizontal and the other one for the vertical if I'm not mistaken.

With these settings I get smooth fps with decent visual quality. Your PC is significantly better than mine (i5 10400, 3060ti, 64GB RAM) so start with these and work your way up. In my experience, don't touch bitrates and similar options. Leave it at default.

Update: today expired my MB.339 trial, so I tested it again: I can now access the modules. The bug is definitely related to trial modules as @JayJ said.