j9murphy

I thought I heard it was more than that, but in looking at their web page to make an apples to apples comparison you would have to add eye tracking to the Somnium - which I don't see a price for, although it is listed on their site - so $1899 + $eye tracking would be the comparison. ... and of course the super doesnt exist yet:)

given that it's twice the price of the new crystal pro, seems like it would have to be better in every conceivable way to be worth the cost. Not sure that's the case...

so this is a lousy picture through the lens, but I clearly dont have the issue that you are having. Mine looks really good at night. maybe take a look at your profile.jspon? mine is attached. this line helped me: "local_dimming_black_level" : 0.005 profile.json

I'll take a look at mine later this week and see if I have some ideas. I don't night fly much in dcs, but I don't remember it looking like that and it definitely doesn't look like that in my civilian sims at night.

you have to adjust the local dimming. The default creates a glow/fog/halo effect around the backlights especially. Once you adjust local dimming and turn the brightness knobs down, it will look better. Not OLED quality, but much better than you see now. Note that you can turn down the local dimming further in the config file below than you can in pimax play. Look for C:\Users\"your username"\AppData\Local\Pimax\runtime\profile.json Change local_dimming_black_level to .005 (or something else that's suitable for you.)

I find that I dont need to oversample my crystal. Can I make it look sharper by oversampling? Sure, but for me, rendering at native resolution is way sharper than the G2 ever was, performs better, more FOV than the G2, and in most cases I can run with no AA. The only places I see shimmering in DCS are things like fences on the ground, I can tolerate that while I taxi and then its a non issue after take off. These things give me more overhead to turn on more eye candy:)

I said this in another thread a while back, but I think it's a mistake to think that Vulcan is going to give some huge improvement in FPS. 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 rates more consistent, but you're not going see a huge performance jump. Over time, because of Vulcan, the devs will have a much better basis for tuning and we will therefore get improvement (over time) unless they they decide to use the new headroom for new features:)

I have not had a great experience with repro on the crustal, although I havnt tried it with the latest update. Wasnt smooth and had motion artifacts here and there. The best repro I had was with my G2 and the openxr toolkit, that worked exceptionally well. guess I need to give it a go again with the crystal and see if it has improved.

@=Andre= I've built a motion seat which has movable flaps in the seat and seat back to replicate g-forces. Right now I have my JetPad just resting in the seat, however I would like to create custom padding for the seat. My question is this.... Would it be pretty straight forward for me to remove the transducers and electronics from the JetPad and install them into the custom padding for the movable seat? It looks like everything could be removed and re-installed without too much of a bother, however I wanted to see if there were any "special instructions" you might have for doing so.

how does one use DSR in VR? does it even apply to VR?

...and the waiting for the rest of us begins:)

If you controllers get new id's just rename your old config files to the new ID.. all your settings will be back.

for me the magic formula for the crystal with the latest DCS update is: Crystal Resolution = Max Set Crystal refresh rate to preference (for me that's 90hz) PimaxXR - Prefer framerate over latency Quadviews = set resolution of center to 100% OXRTK - all options to default (I'm evaluating the relative benefit of continuing to use this at all) DCS - Pixel Density = 1, set max DCS fps equal to HMD refresh rate, no DLSS/MSAA/DLAA For me, this creates the ability to turn up the graphics in DCS so that almost everything is on/max with steady framerates and no ghosting or stuttering. (4090 / 13900k)

+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.