FoxTwo

Based on his opinion it seems to not be an upgrade over the G2 for seated VR. He also felt the sweet spot was a lot smaller.

I'm on ultra. They're fine up close it's the distant clouds that go stair-step.

Much better this patch, no discernible jitter and I'm seeing much better overall detail and contrast in them in VR. However, distant clouds pixelate/get really jagged. Not sure what's going on there, some kind of LOD issue?

I was assuming you may want/need one to interact with steamVR. But I don't know for sure, maybe it can be avoided.

At minimum you'll need at least one controller and for seated VR, at least one base station.

This is a problem with DCS and asset loading/culling. I mean, you can brute force it with VRAM I guess, kind of? But if you want it fixed don't look for a hardware solution. I rarely see DCS actually using more than 7.5GB of VRAM. For those of you running mutli hour multiplayer missions and changing airframes often, maybe you should be asking ED to change their 32bit normal maps to 8 bit to reduce VRAM load.

2.7 changed something with the multiplayer menu and opening up the ground crew stores page. Both just take 100% CPU and all GPU draw calls stop. It's... neat. They broke this before in a previous patch but it's never been what I'd call good. The multiplayer menu gets worse the more servers that are populated in the list. If you type a filter for the name of the server you want fast enough, you can usually avoid it.

I've spent several hours in Hoggit GAW and SAW without issue.

I posted my DCS VR graphics config, and yes I'm using a 3080. Not really running into VRAM issues in multiplayer. Here are my nvidia and steamVR settings.

Display port 1.4's DSC is only necessary to push 120Hz at greater than 4k resolutions. It's using a lossy 3:1 compression algorithm on the data stream to fit over the bandwidth requirements of the display interface. They call it "visually lossless" so you shouldn't notice that it's on. At 90Hz 4k you're pretty close to the bandwidth limit of DP 1.3 so DSC is not required, hence none on the G2. It's a transport stream, it doesn't have anything to do with performance. The Pimax 8kx has been using it since it launched, but I guess it wasn't mainstream enough for the VR press to pick up on.

It's enough VRAM for DCS. I get consistent 45+ FPS with much higher settings than you, even in multiplayer. ["graphics"] = { ["DOF"] = 0, ["LensEffects"] = 0, ["MSAA"] = 1, ["SSAA"] = 0, ["SSAO"] = 1, ["SSLR"] = 0, ["anisotropy"] = 4, ["aspect"] = 1.7777777777778, ["box_mouse_cursor"] = true, ["chimneySmokeDensity"] = 1, ["civTraffic"] = "medium", ["clouds"] = 3, ["clutterMaxDistance"] = 1000, ["cockpitGI"] = 0, ["effects"] = 3, ["flatTerrainShadows"] = 0, ["forestDetailsFactor"] = 0.75, ["forestDistanceFactor"] = 0.75, ["fullScreen"] = true, ["heatBlr"] = 0, ["height"] = 2160, ["lights"] = 2, ["messagesFontScale"] = 1.25, ["motionBlur"] = 0, ["multiMonitorSetup"] = "1camera", ["outputGamma"] = 2, ["preloadRadius"] = 75400, ["rainDroplets"] = true, ["scaleGui"] = 1, ["sceneryDetailsFactor"] = 1, ["shadowTree"] = false, ["shadows"] = 4, ["sync"] = false, ["terrainTextures"] = "max", ["textures"] = 2, ["useDeferredShading"] = 1, ["visibRange"] = "High", ["water"] = 2, ["width"] = 3840, },

Really. No significant changes in cloud movement in VR in the latest open beta build.

Yeah can't say I agree. Not seeing any difference. Nineline mentioned that it was fixed internally not that it was ready for the patch. I expect we'll see it merged in with the hind/marianas in a few weeks.

DCS MiG-21bis by Magnitude 3 Adjusted Cockpit IBL and Ellipsoid Reflection settings. Thanks guys!

He was running it in the wrong mode. From reddit: I'd wait for more reviews before making a decision, either way.

The screen space reflections have a significant amount of high frequency noise. This is contributing to the creation of visual artifacts in both 2d and 3d (VR). It's very distracting and immersion breaking (as much as I hate that term). Please implement a temporal de-noise filter in your game engine. I've zoomed into a very obvious example of it here, but it's all over the engine, particularly with the water. https://1drv.ms/v/s!Ai9-upzOQAxagu4IAEO31DDZF24xjw?e=2MKFA0

If you can get one used for cheap? Maybe. But not at $150. For that much go a little more and get the Virpil warbrd base.

That's the president of HTC. So unless you think they're misrepresenting their product, it's not really debatable.

No, it's not.

120 degrees horizontal FoV is a pretty big step up over the reverb, which only clocks in at around 98. It matches the Pimax in small fov mode.

Have you edited your joystick/keyboard default.lua? There was a typo that was fixed in 2.7 (cptligths became cptlights) however the hotas binding in clickabledata.lua still had a typo. (THROTTLE_EXTERIOR_LIGHTS was THROTTLE_EXTERIOR_LIGTHS). I reported this when 2.7 fixed the cptlights and apparently it was fixed a patch or two back. Run a repair and try using the stock bindings and see if that fixes your issue.

Getting a lot of ships disappearing in the left but not the right eye (or vice versa), particularly in syria.

I believe this is an artifact of the screenspace reflections however I did not notice it prior to 2.7. It's super distracting but any object that is in the water or even objects on shore that have a sight light that goes over water will have a white ringing effect. You can (kind of, I know it's not the best screenshot) see an example of it here. Look at the boats in the water or the offshore island. It even extends along the shoreline.

ED has stated multiple times that they're not going to integrate proprietary solutions. DLSS is one of them.

It's not going to happen. If AMD's FidelityFX Super Resolution gets cross platform support and rolled up into Vulkan, then MAYBE we'll see an implementation for DCS.