davidrbarnette

@Qcumber is correct. Quad View Foveated Rendering does not require a Pimax headset, eye tracking, etc. If you have a Quest 3, for example, it works in fixed foveated mode. I used to use it on my old system that had a 3080 and it worked wonders for improving the framerate (I don’t feel I need it now with a 4090 or id still be using it).

Nice work, I'd give you about a 90% on the test, not bad for a first try! Seriously though, you've got it mostly correct. Some notes: 1) You can use Virtual Desktop, Oculus Link, or AirLink. As a general rule, Link refers to the cabled setup, while AirLink refers to Oculus's wireless option. 2) If you are using the Multithread version of DCS, OpenXR is native, and you don't need to use an argument. OpenXR Toolkit is a seperate software that gives additional options in-game. Your only other option is SteamVR. 3) With a Quest, you'll be using Oculus unless you use Virtual Desktop. OpenXR Toolkit is just additional software that adds additional features / options. 4) Correct.

Not only confusing, but I can’t say that I’ve seen a meaningful improvement in framerates since the last update. The newsletter suggests scenery rendering improvements in orders of magnitude, yet I’ve seen no real difference. What am I missing? system: Ryzen 7950x, RTX 4090, 64GB DDR 5, 1TB SSD

Not only does the Crystal have blurry edges, the chromatic abberation is pretty bad. It has taken me a few days (and aftermarket accessories) to get my Crystal dialed in to where it is usable, but I have to admit I've been a bit shocked by the number of very vocal opinions on the DCS forums who seem to be unable to admit there are any shortcomings at all with the Crystal. Reddit seems to have a much more balanced perspective, however, with many users speaking up about the abberation and low clarity near the edge of the field of view. No doubt the Crystal has the sharpest visuals in the sweet spot of any of the major VR headsets, but the term "edge-to-edge clarity" shouldn't even be used in the same sentence as the Crystal, especially coming from a Quest 3. I am starting to like the thing, but Pimax has some work to do in this area.

I’m aware. I was using the ghosting you see when using ASW to the ghosting you see using DLSS. DLSS has far less ghosting relative to ASW, which sets the standard on my system for bad ghosting. I’m comparing levels of visible artifacts, not upscaling to reprojection.

And to update my initial review: I received the Apache strap and Studioform Creative foam spacer kit today, along with the 100g counter weight. After messing around for a few minutes, I think I'm going to be able to dial this thing in. Tonight was the first time I've experienced the potential on the headset. The image is outstanding, I mean as clear as using a traditional flat screen monitor. It's incredible, and the colors really pop. The only outstanding issues now are: 1) I need to find a way to reduce some of the chromatic abberation. It is definitely there at the edge of the screen. I have prescription VR lenses coming this week, which will allow me to stop using my glasses, which I hate using with a VR headset. I think these will help with the abberation. 2) I need to dial in my DCS settings. Open to suggestions. I tried the ones posted in the Pimax subforum here, and they don't hold a steady 72 fps.

I haven't found a great way to reduce the ghosting with DLSS. It's better than using ASW, but still not perfect.

Just offering some unsolicited advice here, but knock that refresh rate down to 72hz and slide the slider all the way to the right.

I posted a similar write-up on the Pimax reddit. One of the users suggested that I go through a process to set a custom IPD offset for the left and right eyes independently, and it seems to have helped, although I don't intend to really invest time into it until the Apache strap, spacer kit, and prescription lenses come. Maybe that'll help anyone else who has similar issues.

Nope, mine looks as good as it ever has. What GPU? Also, what are your settings? I have a 4090 and run PD in the Quest App all the way to the right, PD in DCS at 1.3, pretty much everything maxed out and hold a solid 72 fps.

I finished the Hunters Over the Yalu campaign today. I scored five kills over the course with zero deaths, which feels like a major accomplishment. Overall I really enjoyed it. I didn't necessarily love the ground pounder missions in the beginning, but the MiG-hunting missions made up for it. I definitely learned to use lag-pursuit while chasing MiGs, and to be patient. Pulling and yanking on the stick bleeds way too much energy in the Sabre, leaving you a sitting duck for MiGs. Another great campaign by Reflected.

Oh trust me guys, I intend to play around with it more to try to get it dialed in... it is too pricey not to try to make it work. I don't rule out user error in any instance. After messing with it for about another hour last night, I have to say the fit is a major issue. I have a new strap coming this week. I also got prescription lenses for it, as wearing glasses with this thing doesn't seem practical, and my contacts drive me nuts when using VR. I hopeful that the new strap and the lenses improve the experience. I maintain that the edge to edge clarity (or lack thereof) is not nearly what you get with the Q3. The resolution in the center is incredible, however the edges are pretty blurry. Again, maybe prescription lenses will help. Time will tell.

Ok, so understand that this is truly an initial reaction. I’ve only used the headset for about an hour, but here is my take. First, I’m a relatively “experienced” VR user. I have had the Quest 2, Reverb G2, and Quest 3 in addition to the Crystal. The Crystal was a bit fiddly to set up, but probably no worse than figuring out any of the other headsets the first time. Once I got it connected to the computer and put the headset on, I could hardly believe how wide the actual faceplate was. It is so wide that it doesn’t touch my temples… there is probably a half centimeter or so between each temple and the side of the headset, and I have a fairly “average” head shape / width. This causes it to rest against your forehead almost like a pivot-point, and it wobbles back and forth if you make rapid movements. I was pleased that the weight isn’t as bad as I had been led to believe, but the fit is pretty awful. I have the Apache comfort strap coming this week, and hopefully it helps. This fit becomes problematic once you load into the game and realize how small the “sweet spot” is compared to the Q3. The wobbling makes focusing on the sweet spot pretty unreliable / hard. The next thing I noticed is that it has a very significant “sweet spot”, with pretty blurry images as you approach the edge of the field of view. Note that I am not using eye tracking or foveated rendering. It feels like a G2 on steroids… a great image right in the sweet spot, with the rest leaving quite a bit to be desired. The other big issue seems to be the barrel distortion. I haven’t experienced this with any other headset. It has a distinct fish-eye look to it. The image in the sweet spot is the Crystal’s best feature. It really is as clear as everyone describes. The visuals are remarkable. Not super impressed with the colors. They seem washed out and about on-par with the G2. In summary, I hate to be negative about it (especially considering the cost) but I’m kind of disappointed. If compared with the Quest 3, the Q3 has a significantly better level of edge to edge clarity, way more vivid colors, and a crazy comfortable fit in comparison. I’m hopeful that my opinion changes with more use. I do remember it took a few days to really get the Q3 dialed-in, and I’m interested to see if my experience improves over the next few days. I really do want to like it. Based on my initial reaction, the Q3 is still the undisputed king of PC VR headsets. My system, for reference: Ryzen 7950X RTX 4090 64GB DDR5

Makes sense. I have been using the Q3 but I have a Pimax Crystal coming tomorrow. Interested to see the differences.

Do you think you're GPU constrained? You may be correct for all I know, but on my system (7950X, 4090, 64GB DDR5) I can run with settings pretty well maxed-out and it still appears that I have GPU headroom. As long as it is a super-simple mission, I maintain 72 fps (Quest 3) without a problem. As soon as the number of units goes up, the FPS starts to suffer. I can easily bring my pretty high-end system to a crawl in DCS Liberation, and it seems like the number of units chokes the processor. I don't think much will change without some optimization on the software side of things.