Glide

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

This error may be related to your onboard graphics card. Is it disabled in the bios? https://steamcommunity.com/app/250820/discussions/0/357284131806024168

You want to ride the afterburners at about 25000 pph to keep your rates up. You have about 5 minutes at this rate before you need to cut back to full mil power. Still, they will outrate you every time. Try against an AI Viper to see if you can keep up with a single engine.

That 4700 number was from a 4090 owner, so for my 3080Ti, I dialed it back to 4500. With DLSS Performance I get VRAM usage in the 70's, and I hold a rock solid 35fps. DLSS Balanced pushed my VRAM consumption almost to 100%, and that's too close for comfort.

So, I was reading about how some upscale the headset and use DLSS to fit the resolution on their hardware. I set a custom resolution of 4700 in ORXTK, and then worked my way up to DLSS Quality. This took me to 103% of my VRAM, which causes stutters during missions when memory starts swapping. Dropping Textures to Medium, Terrain Textures to Low, and Shadows to Medium, brought me down to 70% VRAM usage with DLSS Quality. So, you can upscale the headset quite nicely.

One final tweak, I brought the resolution back up to 3500x4142, and I might drop MSAA to X2. The key takeaway for this method is to watch the App GPU time. With the FPS locked at 30, if you are seeing 33ms frame times, then the GPU is working as hard as it can. If you see 24 ms frame times, you know you have 9ms of headroom before the GPU may skip a beat and you get a stutter. Tweaking the resolution allows you to find the limits of your hardware. Then with Quadviews and/or some DLSS type scaling, and you can bring the visuals back into the sim.

Yes! So, I lowered my resolution to 2880x3408, and this gave me even more headroom. This headset works excellently at lower resolutions. Then, to eliminate the jaggies, MSAA X4 and Quadviews, and it's perfect. No ghosting and smooth flight. Can't tell from the FPS counter from OpenXRtk what the app GPU time is, but is never moves from 35/36 fps during my busiest dogfight. Now to bring back some of the graphic fidelity from the Settings, and these are set and forget.

Okay, while those settings were good, in missions that are a bit busier, they can be a bit bumpy. Even better: Disable Smart Smoothing in the Play Client. Enable Prefer Framerate over Latency (turbo mode) in the PimaxXR client. Disable Low Latency Mode in the NCP (not sure if this conflicts with turbo mode). This allowed me to bump up the FPS to 35 in the Settings. So, in exchange for very little aliasing, no ghosting, the best sharpness you can get (the spotting "dot" is clearly a square with these settings), and perfectly smooth framerates. I still need to test a few more maps and missions. I would love to hear what the 40 series cards can do with these settings and maximum resolution.

I discovered some really nice performance settings in the sim today. They may seem odd, but give them a try if you can. My settings are below. As you can see I had to turn them down quite a bit in order to maintain an App GPU time below 33ms. With the FPS locked at 30 in the Settings, I was getting an App GPU time of around 24ms. This gave me a LOT of headroom for spikes in performance, and as a result I got a very, very solid 30 FPS. Here are the key ingredients: no AA, no AF. I am running a custom resolution of 3500x4142 on my 3080Ti, so the alaising was very minimal to begin with. Enable Smart Smoothing in the Pimax Play Client. I am running 72hz Lab Mode right now. Only thing set in the Nvidia Control Panel is Low Latency On. No Quadviews, No scaling in OpenXR Toolkit, no Foveated Rendering. Just pure frames with Smart Smoothing, and whatever settings you need to keep the App GPU time around 24ms. Clear, and smooth. (Update: even better settings below)

Now I have a mission to build! Thanks! I fly the Viper into a dogfight with AB on around 25000. This gives me high rates for a good few minutes down to 5000 lbs of fuel. Surviving the first few minutes is critical against a twin engine. Ride that afterburner folks. It's a ton of fun now. Update: I made my usual 8v8 guns only dogfight, me with 6 9x's, and we wiped them out very quickly 6 for 6 with the sidewinders. They don't have the same rate of chaff/flair dispensing that the Mig-29s have. I'll test a few more times. I know this is not strictly Viper performance related, but I did not feel threatened by the Hornet AI's the way I fear the Mig-29s. They weren't even in the fight.

I did the firmware update today for the Pimax Crystal Sim. I'm on v1.3.0_au0221 with client 1.18.02.01. Sometimes when I launch I get constant movement in the hangar. I have to force stop DCS when that happens. Other times I get the cockpit moving all around when I pan the headset around. Fix: I did a slow repair. Launched into a Viper mission with success. I also tested QuadViews with Turbo Mode in PimaxXR, and it is back to working smoothly.