j9murphy

+1 for me too, 120hz disappears, I restart the headset 120hz comes back, but pass through is still a no go.

I did some "tuning" with my crystal last night and had the following observations... - ghosting (I'm defining ghosting as the smearing or the elongating of ground objects when looking at them during a roll or high speed turn) - in my case this was 100% related to frame rate. if frame rate equals hmd refresh rate then no ghosting, the farther these things get apart then the worse it is. This lead me to conclude that if I want to eliminate ghosting then I need to make other trade offs. For me this was dialing back the center for quadviews to 100%, turning off all anti aliasing (no MSAA, DLSS, DLAA ) - for the crystal, I dont see much shimmering or need for AA anyway This gave me the headroom to get right around 90fps in most scenarios with clear crisp images. How far that drops in complicated missions and in multiplayer is yet to be seen, but so far i'm happy with the results.

unless you are creating your own missions, take a look at the missions and campaigns (free and paid) that you would like to leverage, and then pick the map with the most that you are interested in. Let your interest in the missions and campaigns drive the map, not the other way around. If you just want to look out the window, choose the other sim:)

I think I read somewhere that it was a holo lens update only, nothing in WMR changed

For those of you hoping for an open source solution or replacement to WMR, it sounds like that is unlikely to happen. For reference, see the 2 posts below by mbucchia on the subject... https://forums.flightsimulator.com/t/microsoft-is-discontinuing-windows-mixed-reality-wmr/622334/191 https://forums.flightsimulator.com/t/microsoft-is-discontinuing-windows-mixed-reality-wmr/622334/185

Honestly, the best thing you could do at this point for flight simming (since you posted in a flightsim forum) would be to get motion smoothing improved. Currently, it doesn't work very well in 72hz, and could benefit from some improvements in smoothness and clarity (less artifacting) in the other modes. Other than that, if any improvements are possible in local dimming for night flying that would also be beneficial! Great headset though, overall I love the clarity.

does this mean all WMR headsets will no longer function when windows drops support, or will openxr and/or steamvr still allow them to work in some fashion? maybe @mbucchia could clarify what the implication of this is? In the past microsoft had already said they would no longer develop/support the AR part WMR.

There's also this post... https://forum.dcs.world/topic/337815-vr-pov-not-centered/#comment-5329392

I *hope* you're right, but my guess is that we will get more consistent framerates over a much broader range of scenarios instead (MP and huge missions fps will be more like what we see in single payer mode today vs. a large single player fps increase).

Vulcan will enable the developers to manage graphics calls more efficiently. It's multicore friendly and separates object creation from object usage meaning you can create objects on a different thread and use them without additional overhead. This gives you a lot more ability to tune the app. However, tuning will be a long process. My guess and it's only a guess.. the first release of Vulcan in dcs will not provide huge performance benefits. It will probably make frame more consistent but you're not going see a huge performance jump immediately. Over time though, because we are now on Vulcan the devs will have a much better basis for tuning and we will therefore get improvement (over time), or not if they decide to use the new headroom for new features:)

I've used them together. I had to enable openxr in the ultraleap control panel and copy the leap dll into the dcs bin directories. That made everything work. There is also an app that verifies your openxr api stack is correct. I'm not at my computer, but if you need the link for that let me know.

It's unfortunate that so many people have trouble with their crystal. Mine just works, never had a problem, never had to contact support. There are a couple of things that don't work as well as they should yet, and I had to add prescription lenses and an apache headstrap to make the comfort tolerable, but other than that, I'm really happy with it.

Based on what happened when Xplane adopted Vulcan (maybe not a good comparison) but it only did the following... - brought more consistency to framerates (not necessarily more fps, but smoother fps - at least until xp12 came out lol) - created the basis for making further performance optimizations (this is a long road and one that only STARTS with implementing vulcan.) I would expect Vulcan to (at best) allow DCS to maintain current performance as they pursue more features (better flight models, better weather, more units active, more realism, etc...) Until then, at least we have Matt's great work to bridge the gap while hopefully ED decides to adopt at least some of the functionality natively.

It's really too bad that VR is so fragmented from a tech perspective. It creates opportunity from an innovation perspective (from the HMD developer POV), but also means a PITA from the game developer POV because there are too many thing to support and optimize for. Matt was a one man unifying force in VR for us all, and unfortunately this means it's up to the game developers and HMD developers to come together and solve the problem (highly doubtful since VR is still a niche group for high end sim games). Thank you @mbucchia for all that you managed to accomplish. Your efforts were much appreciated and I hope that your vision of a community of developers to carry on this work will come to fruition. We are all better off in VR given what you accomplished.

Is anyone using an ultraleap with the latest beta (48335)? When I turn on openxr in the ultraleap control panel I cannot get DCS to start in VR. I can get it to work in the stable version, but only by using the Special tab. Nothing works if I try and enable it in the VR tab instead.

Clicking the middle mouse button does it for me, although I think I may have that reassigned. I'll have to look at what I might have assigned it to when I'm back at the computer....

are you using QVFR with eyetracking or FFR?

Before -3.5/-3.25, After -2.5/-2.25 honestly, for me probably could have gone to -2.25/-2, but I have no complaints.

someone on redit posted a few weeks ago (who also didn't wear glasses), that because the crystal focus distance is so close that they went to store and picked a couple of cheap reading glasses at various low strengths. One of the low power ones made a huge difference so they ordered the honsvr lenses of the same prescription. Of course waiting for nexgen is also a good option:) cheers.

I also got HonsVR lenses. The first set I got were overcorrected for the Pimax (even though they were the correct prescription) leading to a lot of coma at the edge and bending of the image. I let them know and they sent me replacements that were dialed down a little bit - they work MUCH better. Much better clarity at the edges and much less "bowing" of the image. From what I understand this is often necessary with the Crystal because the focal distance is somewhat less than other headsets and the distance that an eyeglass prescription is meant for.

I'm probably unique, but I got HonsVR Lens inserts to replace my glasses in the Crystal, and they actually improved clarity to the edge for me a some. Don't know if that's just correcting my astigmatism or I just got lucky, but it did help.

Has anyone tried both? Is there clear winner?

Anyone know how to solve the "DSC World not installed at bin\dcs.exe" problem?

Which version of the leap controller are you using? Has anyone tried both version and version 2 with the same version of DCS? is it worthwhile to buy version 2 if you already have the orginal version?

yes, and I added that to the OP for clarity - thank you for pointing that out!