Johnny Dioxin

Same here. Lenses were iffy - like many others - replacements received within a month and it's now the only one of my headsets that I use - every day. I'm constantly amazed by how great everything looks in it. My only dislike - being picky - of the hardware is the heavy cable. If it's not in just the right place I really notice it's weight. Used together with Point Control it's easily the best flight simming experience I've had. In fact, after being very on/off with DCS and other sims for the last few years, the Crystal Light has got me wanting to fly every day again. Having said all that, their support could be better, especially with comms, and I think they exaggerate too much in their product descriptions. Most manufacturers or dealers do to some extent, but I think Pimax don't do themselves any favours with some of their claims - just feeds the fire. I think their enthusiasm also often gets the better of them. TBH though, if they hadn't released this headset I'd still be waiting for Deckard - if it ever shows up.

Don't be disheartened - in my experience support have been on the ball - and I contacted them quite a bit in the first few weeks. Sometimes they do need a little nudge (as our friend Calvin is very good at doing) but that's usually because they have a lot on their hands, I am led to believe. My issues were resolved and usually pretty quickly in comparison to other VR outfits.

Aaah, my dream...

Don't forget that, a few years back when interviewed one of the dev's responsible for the Falcon 4 dynamic campaign said that they would never do it again and if they had known how hard it was going to be, they wouldn't have started doing it in the first place. Think it may have been in PC Pilot magazine. People like to not recognise that, ignore it or just spew their usual bull. To put it bluntly.

Maybe that means OpenXR in SteamVR, not separate, standalone OpenXR as I would use with, say, my Pico 4 and Virtual Desktop? Do you have OpenXR set to SteamVR in your settings?

No - I've been having a problem - highly likely a Pimax one - where OpenXR will not work and the result is that DCS World always starts up SteamVR. So no, it hasn't been dropped Also, my SteamVR performance has been very nice, except in the Chinook. *edit: using sim installation, not Steam version of it.

I thought it was simply overloading the graphics card, but it turns out it's something to do with my headset and the freeze was caused by a SteamVR crash. SteamVR is currently unable to find my headset (but the Pimax software is finding it - so it's a SteamVR or Pimax software issue). I tried to run in OpenXR/PimaxXR, but for some reason SteamVR is still starting up, and that stops everything. Hopefully find a fix to get it at least working in OpenXR while Pimax support get their backsides in gear and look at my issue, which they currently aren't doing as they fobbed me off to their support FAQ. Anyway, OT but explains the freeze up in MT.

Just an additional note - the above posted results were in ST. Today I tried it in MT and it was a whole lot worse. My mistake on the res posted before - I'm actually at 100% in DCS World. The cockpit textures took several minutes to load in - long after the 'instructor' had finished his intro spiel. The framerate started at 45 and as each section of the cockpit textures loaded in, the framerate dropped until it was in the mid-teens. The frametime for GPU was in the mid 40's and for the CPU the mid 20's. The graphs in fpsVR were all a solid wall of red. The VRAM was at 15.3GB out of the available 15.7 which I thought would be a good thing, but seems not. Anyway, when I exited the Chinook mission because it would be hopeless to continue, the sim froze and VR crashed. This is actually a good example of why I stay on ST at the moment. So definitely a "Wait, out" for now.

I just tried it for the first time. I just did a clean, fresh install of DCS World and there have been no updates (cos I just did it, so...). No mods at all and while I was so happy with an average 67fps in my F-16C on a busy Persian Gulf mission with my new Crystal Light (at 70% res and 90Hz), the fps in a cold & dark Chinook, in the start-up training mission, is 22-23. On external view it rises to average 46fps, as soon as I got back into the VC it drops to 22-23 again. There was obvious stuttering as the Hummer drives past. I was too concerned to do more than the first few steps of the start-up, after what I experienced when the Apache was released (which was waaay worse) and which is now performing very well. I think this one just needs some time, like those before it. I'll revisit next year - still have a Kiowa to learn.

Me too!

Surely if it was ordered on 2nd October, you missed the boat? Offer is from 4th October. Just the way the cookie crumbles -same as for everyone else who got theirs recently but before that date. Just like a sale - can't say "I bought mine 2 days ago, why can't I have the sale price?". Well, you can say it, but we all know what the answer would be...

Standard Windows SAPI

This sort of issue usually happens when an axis or button is assigned (intentionally or not) to a view movement function. I strongly suggest checking through all the assignments - including axes, to see if that has happened. Just cos you didn't assign it, does not necessarily mean it isn't happening! (has happened to me before, too).

I am - and performance is good and stable. Average framerate is 67fps. When the latest Pimax Play is stable I'll go to OpenXR direct, but in the meantime, SteamVR is doing a good job in busy SP missions and if it ain't broke...

Umm, I use two! PCL for serious, long missions or Pico 4 for quick stuff or training missions and the like. Actual time spent in each is probably about equal, but if I had to stick with one, it would be the PCL, so that's what I've chosen. The PCL is a weird one - it can seem a bit strange to start with and make you feel a bit cross-eyed, but stick with it cos you do get used to it and it's a fantastic headset. Had mine 3 weeks before I got used to the 'view'.