PawlaczGMD

Yes, that's exactly what it is. I think they way they scale it causes the dots to be too big on lower res headsets, and too small on higher res ones. I've tried turning the improved dots on and off, and honestly I can barely tell the difference.

Therefore I'd like ED staff to take a look at the tracks and flag it as a bug to be fixed.

It really depends on what VR set they're using. When I had Quest 2 and Pico 4, the dots were huge. On Crystal, they almost don't exist. The way they scale it with headset resolution needs tuning.

I don't have the DLAA option because I'm on an AMD gpu. TAA is best in the sense that it makes everything else except small distant targets look way better than MSAA. The game is simply more enjoyable to look at, but I have serious issues with keeping track of targets. You might be right about the difference between 2D and VR, and so it is difficult for me to provide examples of how these settings look in the VR headset. The point is that every available option has serious drawbacks. Not sure it can be helped by ED to be fair.

I will double-check that it was in auto, but the safety cover was down and I didn't touch it before noticing the problems at maybe 20k ft. I'm just starting with flying this thing so it might be my issue for sure. Well, I only managed to climb to 30k because I mapped the High setting to my HOTAS and kept it pressed in.

Just experienced this as well. Turbo didn't kick in until 30k ft in the navigation mission from the challenge campaign. I ended up having to keep the high position pressed to climb that high.

I second this. Having used 2 different headsets over the last months, low- to medium- resolution VR = huge spotting dots. High-resolution VR = almost no spotting dots, with Pimax Crystal I only see them for bombers and naval vessels. The resolution scaling of the dots should be changed, at least for VR.

TAA is by far the best AA method available IMHO. In VR, the terrain looks quite bad for me with no AA, and even with MSAA it doesn't improve much, and it is expensive in terms of performance. This might be a VR specific display thing, as the 2D mirror looks way better on my monitor without AA. TAA makes the game look really great. It is also necessary if you are using upscaling, which is another great piece of tech. However, I notice a very serious limitation when using TAA. At long ranges, targets blink in and out of existence. The silhouettes of fighters are flickering, the details/ aircraft parts appear and disappear. It is very easy to lose a straight and level flying target against the ground even at medium distances, and now I am talking in terms of warbirds, so not BVR, maybe 100-200 meters. The issue is worse with upscaling added, but seems to be mainly caused by TAA. This forces me to make a choice, whether I want to make the game look good (TAA), or whether I want to be effective in a WVR dogfight (no AA). I don't know if it is within DCS control to change how such details look, or maybe it is just an inherent drawback of these technologies. But it would be great if there was a way of improving medium- to long-distance visibility of targets with TAA, perhaps via modified spotting dots? Does anyone have similar experiences?

Some additional feedback: I think the spotting dots still penalize high resolution too much. For example, I'm using the pimax crystal VR, with 100% PD and 125% central square resolution via Quad Views. I basically don't see dots for fighter-sized targets. Unless they are against clouds, then a weirdly larger white dot appears. If I manage to glance at the reduced resolution side area, the dots are big there, probably too big. I would say that the dots should still be smaller at lower res, and larger at higher res.

You're misunderstanding. This is an issue that happens in VR only. The 2 tracks attached show the difference. The non-VR HMD circle and HUD target circle agree perfectly. It does not depend on the helo moving, or any other such realistic effects, but on using VR or not as a player.

Bump. Can someone take a look at the tracks and acknowledge?

I would say it's only worth it if you want to run a springless stick for helicopters, for which you need the dampers. Otherwise, the dampers add a desirable feeling for fixed wing, but are probably not worth getting just for this. As for other cams and springs, I personally have tried them out, but returned to the default cams and medium springs. If you use an extension, you might benefit from heavy springs or even double cams/springs.

You can try downloading QuadViews Companion app, and tuning the size, position, and resolution of the high res area. For example, you could try to reduce the high res size, but increase the resolution scaling.

1) I'm not sure, it might be replacing it with another interpolation method. But having FPS locked at half is a sure symptom of some MR happening. 2) This probably means you're using 97% of your available GPU resources, aka you're maxed out. The harsh reality is that DCS in VR is extremely demanding, so with your specs you can only do so much to make it run better. Try lowering all graphics settings to minimum and check fps, go up from there. My current GPU is about 2.5x faster than yours, and I still don't get a good frame rate in many situations (albeit on Crystal, which has a higher resolution). So it is very likely your hardware is struggling. You definitely don't have extra capacity that DCS is not using. I recently had Quest 2 and a RTX 2080 TI, and I was having some performance problems. This is normal on your PC specs. What I'm trying to convey to you is that your problem is low framerate, not some magical setting or bug you need to find. You need to raise FPS to solve your issues. You can do it by: 1) buying a new GPU 2) reducing graphics settings in DCS 3) reducing pixel density in Q2. Anything else is fine-tuning, but is seems like you're not even close with the required performance. One Hail Mary I saw someone mention would be to use Quad Views Foveated in fixed mode. It decreases the resolution in the peripheral vision of the display, increasing performance. I don't know if this works on Q2, I saw someone use it on Q3.

By killing the engine, I mean you are overstressing it to the point it blows up internally, so no, you cannot restart it after this kind of failure Otherwise, if the engine cuts out briefly for lack of fuel supply, etc., it should self-restart as long as it's spinning.

He already said in another thread that with 72 Hz he's still in reprojection. He doesn't seem to understand what it does. I recommend reading up what motion reprojection / asynchronous warp is and what it does to the frames.

We told you this already in the other thread. Your PC is not strong enough to sustain 1/2 of the framerate in DCS, because DCS is very demanding. If your FPS is locked at 1/2, this means async warp is generating fake frames to make up the difference. It doesn't have the data to generate this on the edges, so you see a vibrating effect. "have heard that's the result of the headset effectively being 2 displays, one for each eye, thus 120/2 = 60." This is complete nonsense. You have less than 60 real frames because your PC is not strong enough for the settings you use. The headset is interpolating fake frames to pull it up to 60 because that's what it's programmed to do at low framerates with motion reprojection. You need to lower your graphics settings, or upgrade your PC.

Sounds like you're killing the engine by having too high boost at low RPM. You can't be maxing out the throttle, this takes you to a boost level that is not within spec, unless you are limited by altitude. 18 psi is the absolute max, and only at 3000 RPM for a few minutes. Try this: Just leave RPM at 2850. Don't go over 14 psi. It is not optimal but should be good enough to fight the AI and return home. Don't go full throttle.

What boost are you at? High RPM is not really what damages your engine, high boost at too low RPM is what's bad. At 2500 RPM you should not really exceed 6-7 psi, the manufacturer settings are : 2650 RPM - up to 8 psi, 2850 RPM - up to 12 psi, 3000 RPM - up to 18 psi (5 minutes max). So you want more RPM at high boost, not less. If your low fuel pressure is not coming on, I would guess that you're just killing the engine by managing it wrong. Including a track of this failure would help diagnose.

Yeah, your PC is just borderline when it comes to running DCS in VR. You have to use weird settings and suffer reprojection, which is frame interpolation, to make it playable. The only real solution is to upgrade your PC. Your problem is that you don't hold at least 1/2 of the nominal frame rate at any setting.

Are you using the multi threaded version of DCS? You really need to to even dream of using VR. If your FPS is hard locked at 1/2 of the nominal rate, I believe this means you are actually constantly under, and motion reprojection is making up the difference. It is the Quest that is locking you at 1/2, not DCS. It has been a while since I sold my Q2 so I don't remember how it works exactly. I would try to reduce all DCS graphics settings to minimum, reduce pixel density in Q2, and check the FPS and performance. I was never CPU bound unless using quad views, so I don't have experience with this, but again this might just indicate your PC is below the spec required to run DCS in VR. But overall you seem to have 2 independent issues: - DCS looks like crap in VR without using TAA, which causes its own issues. I also experience this on Pimax Crystal with decent framerate. Seems to be either a VR headset display or DCS VR bug/issue. - You are unable to sustain a minimum framerate at your current settings, which causes motion reprojection to kick in and ruin your day. PS there might be a way to disable motion reprojection (asynchronous warp). If you find it, you will see what framerate you actually have.

The "vibrating" at the edges sounds like motion reprojection. This indicates you have a low framerate. Check it, if so, decrease settings or resolution. If you can't hold 1/2 of the nominal hardware framerate, it is a problem. In fact, your GPU is on what I'd call a low end of viability for DCS VR. The ghosting is caused by TAA. It might be worse because of your low framerate. I just use FSR with TAA and accept the ghosting. With my framerate, it's not too bad. No AA makes terrain look really crappy on my headset, just in the way you describe (Crystal), and MSAA is very expensive and barely makes a difference. It might be the same for you. I have also noticed that the game looks a lot worse without TAA in my headset compared to on the 2D screen. It might be worth for ED to look into how no AA or MSAA looks in VR. I think it looks really bad, much much worse than the 2D mirror on my monitor. This might be some kind of graphical bug exclusive to VR. TLDR: use some debug tool to tell us your framerate when the issues occur.

Thanks, I did a Windows repair, I'll see if this comes back.

Log from another crash, with Reshade off. dcs.log

Sure, I will try to keep both DCS and Reshade updated. In fact, the latest 6.0.1 Reshade version is the only one I managed to get to work in VR MT, so I never used any previous versions.