Glide

This is related to the weather setting. Try Overcast with Rain.

The pilot in the first shot is touching the hillside. He slowly tracks down until he encounters the "crease" in the terrain, then his chute collapses as normal. Caucasus map.

I removed the weather, and although I am hitting the target FPS, I can clearly see that facing north from that viewpoint takes 15% more GPU than facing south. Something is odd about the Batumi airfield.

On my Batumi mission, I have a strange situation where I miss my FPS target, but it only happens when I'm facing one direction. I can't seem to pin down the culprit. Any ideas? Caucasus Assault on Batumi Day 1 AM.miz

Zoom in on this image. There is a checkerboard pattern in the terrain at a certain distance. It's very visible in the game. Any ideas?

https://www.twz.com/news-features/f-4-phantoms-conduct-phinal-popeye-missile-live-fire-before-south-korea-bids-them-pharewell

They are part of the standard load for SEAD missions when you intend to get within range. I don't mount them for dogfighting or BVR.

Caucasus is a "light" map. The others are larger, suggesting you are hitting some limit in our system. Try lowering the resolution. In my VR system, if I run at full resolution, I get massive ground jitter. When I run at a lower resolution, it's smooth.

Bought. The RB debacle hit me hard as well. The solution to banishing unhappy memories is to replace them with new happy memories. I am happy to support ED and the future of my favorite hobby.

Do you mind performing a simple test with just keyboard inputs? I can see what you are describing in the ACMI file.

Could it be the rudder? Slightly out of position, one foot heavier than the other?

It's called Main Mast Assembly (MMA). Look for MMA under loadout, and add the pod.

VR screenshots seem to be squished and stretched after today's update. I have HMD mask enabled.

Regardless of the public data, YT videos of viper pilots don't agree that the FM is correct. It's as correct as they can get it within the limits of the sim, I suppose. I wish it was faster and didn't bleed energy like a popped balloon. Then it would be more fun. If it's "realistic" and not fun, it's a fail.

This is a good tutorial.

I tried twice to get that bird to fly. Both times I uninstalled it. It might be "realistic" but it's no fun at all.

Ghosting in a side effect of TAA, and DLSS is a form of TAA. We will have to wait as the technology evolves.

If you have a brake axis mapped, check that it is not reversed. Also, you release the brake with a little tap on the brake. The handle on the stick should move away when the brakes are off.

This has been said before, but I'll repeat it. DLSS is binary compatible. Although you can drop the latest dll into place, you will not see the new features until the devs implement them.

You didn't out rate that Mig-29; he came to you. That video reflects my experiences as well. The Viper can't catch the Mig-29 ai's. You can turn inside them, but you bleed energy too quickly to keep up.

https://github.com/mbucchia/Quad-Views-Foveated/wiki Any OpenXR headset with eye tracking should work.

QuadViews (QVFR) is only available on supported vr headsets like the Pimax Crystal.

Interesting tests today. My goal was to get my 3080Ti to run Maximum resolution, and so I started tuning my settings accordingly. I started out with nothing enabled in PimaxXR, no OpenXRTK enabled, just dlss performance, and my light performance settings from above. I wanted to check again how Smart Smoothing works. I found that it doesn't show very many of those vsync-like screen artifacts when it's BELOW half the refresh rate. When I could hit say 45fps, I believe the Smart Smoothing was struggling a bit. You can see some evidence in the FPS counter when the screen artifacts appear. Kind of a de-sync pattern for a second or two. The screenshots are not great. Then I turned on Low Latency Mode to On (Ultra did not make any difference). Now, I started to see brief periods where I would go from CPU bound to GPU bound with a theoretical FPS of 110ish. But, it would cycle back and forth, perhaps indicating that Smart Smoothing was struggling. Then I turn off Smart Smoothing, and the FPS counter stayed solidly on GPU bound theoretically fps 110ish thanks to Low Latency Mode. If I want to go higher, I need more VRAM because I can hit 12gb with this resolution quite easily. Low Latency Mode On No Quadviews, no Smart Smoothing, no Dynamic FOV rendering and no scaling. Note: I am also testing Eye Tracking OFF and Auto IPD OFF to see how that effects stability, but I don't think it was a factor in this test.

And is Smart Smoothing the exact same tech as Motion Reprojection? Does it naturally lock at half frame rate? Or does it work some new way? I guess it would be nice to see a technical definition of smart smoothing and how it differs from other smoothing technologies. Some background: https://www.uploadvr.com/reprojection-explained/?ref=uploadvr.com