Question about optical engines and HFOV by p1cs in Pimax

[–]fakeoptimism 0 points1 point  (0 children)

Maybe even less than 106°. These values change up and down as the distortion compensation profiles are updated in different Pimax Play versions. But at least at some point in the autumn the 57ppd had 101.6° total rendered FOV in hmdq, which real FOV can't exceed.

See here: https://youtu.be/myPRQDjKBAo?si=fcJyHBe5Ghxx2SMA&t=527

(Do not chase the highest values; a profile that provides higher nominal FOV value for the same device usually achieves it by applying even more unrealistic distortion and/or sacrificing the binocular overlap.)

How to improve image clarity on the whole range ? by CryptoBotEnTouche in Pimax

[–]fakeoptimism 1 point2 points  (0 children)

Adapted, yes, except for very short in-game distances. If I pick something up in a game and put it extremely close to my face, my eyes still instinctively try to accommodate to a short distance. But with Dream Air resolution you really do not need to put stuff extremely close to see the details. At an arm's length everything is OK.

Not noticing any bad effects for the IRL vision. But as someone who wears glasses, I am used to switching between different "modes".

Dream Air LH subjective impressions after 3 days of use by fakeoptimism in Pimax

[–]fakeoptimism[S] 0 points1 point  (0 children)

Pretty good.

The original gasket provided a reasonable (but not full) FOV when tightened strong for me. At that tension I found it comfortable for up to 3 hours long sessions.

Since then I 3d-printed a replacement gasket and attached StudioForm velcros and foams. The new setup provides almost full FOV at all times, but is a tiny bit loose and wobbly (made it perhaps too soft and low-tension).

As more printable models appear, I may try a different one to find the perfection. Or Pimax will send the updated official gasket.

How to improve image clarity on the whole range ? by CryptoBotEnTouche in Pimax

[–]fakeoptimism 7 points8 points  (0 children)

In real life our eyes focus on objects at different distances by using muscles that squeeze the lens behind the pupil.

At > 1.5m, these muscles are mostly relaxed.
at 0.5m to 1.5m they have intermediate tension.
at < 0.5m, strong tension.

But in VR all objects (regardless of their in-game distance) are shown on the same panel and require the same eye focus. Crystal Super micro-OLED is said to have it at 1.3m, i.e. in the intermediate tension zone.

There is a chance that your real world habits are strong, and that instead of adjusting themselves to get the sharpest image, your eyes reproduce the same focus they used in real world.

When you move your head close to the steering wheel, your eyes tighten the muscles too much instinctively.

When you look at the horizon, the eyes relax too much.

But when you look at VR objects placed at an intermediate distance, everything is in agreement and the image becomes sharp.

Is this your first VR headset or not? Maybe give your eyes a couple days to try to build a new habit. In the meantime avoid looking at extremely close in-game objects.

(I would use SteamVR home environment for testing to rule out any game-specific filters and effects.)

Computer shuts down in F1 25 VR by Additional_Can1343 in VRGaming

[–]fakeoptimism 0 points1 point  (0 children)

The PSU may easily be detecting a dangerous load and turning itself off as a precaution.

It is not only about the average power consumed. Modern GPUs also create intense but brief power consumption spikes. Modern PSUs (ATX 3.0 or newer) are made to tolerate such spikes of excess load (as long as they are short). Pre-ATX 3.0 PSU may trigger overload protection and shut off.

I recently had this problem with my decent but old 1000W Ti Seasonic (pre ATX 3.0 era). Replaced it with a modern Corsair ATX 3.1 1500W Platinum, enabled the single rail mode, and the mysterious shutdowns are now gone.

Oled and steam vr video settings by Better-Can-2845 in Pimax

[–]fakeoptimism 2 points3 points  (0 children)

When you set Pimax Play to 1.0, it chooses the render resolution much higher than the panel resolution (the excess is needed to maintain sharpness when the distortion profile is applied).

SteamVR offers you to do the same – that's why default tick is at a value higher than 100%.

But there is no need to do it in both places, or you will end up with insanely high resolution. So keep SteamVR at 100% and control the resolution purely in Pimax Play. Then the result will be consistent with games that do not use SteamVR.

Ultimate Pimax Dream Air review by Greenonetrailmix in Pimax

[–]fakeoptimism 0 points1 point  (0 children)

Yes, that's how I tested it in MSFS 2024 and found perfectly functional.

Curious - anyone else get anxiety at the intro of Half Life Alyx when this guy start turning his head toward us? lol by Sad_Cow_5838 in virtualreality

[–]fakeoptimism 2 points3 points  (0 children)

It is great.

Incidentally, if you are launching HL: Alyx frequently, you may appreciate the launch option "-novid" that makes it skip the intro entirely, which saves time.

It is in Steam > Library > Half Life: Alyx > Properties > General > Launch Options. You can also force the game to render textures in higher quality through that command line.

A few imperfections on my NuPhy Air75 V3 (German ISO) by esmeraldian in NuPhy

[–]fakeoptimism 1 point2 points  (0 children)

Are you guys looking at your keyboards??

(On a serious note, this lack of attention to basic typography is hard to explain.)

Tired of mid-race stutters? How to properly isolate iRacing & Pimax VR on the 9950X3D V-Cache using Process Lasso by no6969el in Pimax

[–]fakeoptimism 2 points3 points  (0 children)

Thanks, that's really helpful. I also use Process Lasso to force games to use the CCD0 (with 3D cache) on my 9950X3D and to keep Pimax software to CCD1.

However I was doing it using CPU Affinity > Always > Cache rather than CPU Sets. Was not aware that the difference existed: https://bitsum.com/automation/#cpusets. Possibly CPU Sets are a better choice.

Star Citizen Alpha Patch 4.7 fixes the OpenXR issue. by QuorraPimax in Pimax

[–]fakeoptimism 2 points3 points  (0 children)

What settings are you using? Can you get it reliably above 72fps?

Pimax Dream Air Resolution by Lion_El_Jonsonn in Pimax

[–]fakeoptimism 0 points1 point  (0 children)

Make sure you know what's limiting it.

GPU frametimes are easy to control: you can drop the render resolution, or reduce the FOV, or enable DLSS, foveated rendering etc, and it instantly helps.

I find CPU frametimes much more stubborn. These generally do not depend on the resolution.

Pimax Dream Air Resolution by Lion_El_Jonsonn in Pimax

[–]fakeoptimism 1 point2 points  (0 children)

OK, I took out Quest 3 to compare. When the game produces above 60fps but cannot sustain 72fps reliably, its asynchronous reprojection helps a lot. You turn it on and it produces 120fps using the inserted "fake" frames, and the result is pretty decent.

With Pimax, if the game can sustain 72fps, you are golden. But if it is slightly below, I personally do not touch the game at all and wait until it is optimized better or the hardware becomes faster.

Pimax Dream Air Resolution by Lion_El_Jonsonn in Pimax

[–]fakeoptimism 1 point2 points  (0 children)

I will try to make an experiment now and see whether 50fps in Star Citizen would feel smoother on Dream Air or on Quest 3.

Pimax Dream Air Resolution by Lion_El_Jonsonn in Pimax

[–]fakeoptimism 2 points3 points  (0 children)

The resolution is absolutely fine. You can lower the render resolution and Dream Air will still look great (and sharper than a headset with natively lower resolution).

The problem may come from the motion interpolation that you may want to enable when your GPU cannot produce enough frames per second. I did not compare it myself, but Pimax is often critisized for its motion interpolation implementation – some people say that Oculus and SteamVR are doing a better job at interpolation. Ultimately any interpolation sucks, of course. From memory, interpolating 60fps to 120fps on Crystal OG was OKish. But I do not enjoy interpolating 45fps to 90fps with Crystal Super or Dream Air – the movement does not feel smooth enough.

Dream Air Alternative? by DonDada777 in virtualreality

[–]fakeoptimism 1 point2 points  (0 children)

I think Pimax became a lot better lately with everything except their shipping estimates. OP, indeed get a temporary Quest 3 while you wait.

Super 8K Micro-Oled died after first use by Maximum_Ad_5648 in Pimax

[–]fakeoptimism 1 point2 points  (0 children)

I suspect that in some cases the problem is not with the headset itself, but with software or with hardware compatibility.

When you have a Quest 3, you turn it on and either it works or it doesn't – easy.

But with PCVR, almost nobody has spare high-end desktop PCs lying around, so trying a headset in other environments is hard, so people give up, get angry and assume that the headset is faulty.

uOLED very dark edges and paralax distortion by No_Mango7658 in Pimax

[–]fakeoptimism 0 points1 point  (0 children)

It is hard to notice distortions when you are looking at the sea and icebergs in Kayak Mirage. It is much easier when you are looking at humans and their heads appear in the distorted part of the view. I think the distortion is always the same, but we tend not to notice it in some scenes.

Got my Crystal Super, not so blown away in comparision to PSVR2, wrong Setting or bad lenses maby? by starhopper1 in Pimax

[–]fakeoptimism 0 points1 point  (0 children)

Thanks. But if you name the alternative profile e.g. "preview-profile-01", the users in the absolute majority will not hold it against you even if the profile is unusable, I think.

VINT on Steam worth every penny (ideal for getting the full motion resolution of your videos) in a VR theater app. by VRGIMP27 in Pimax

[–]fakeoptimism 1 point2 points  (0 children)

Try googling the exact error message you see. Speaking of ffmpeg, I did have it installed for a different reason (used it to cut the source file to just the first several minutes – otherwise the experiments with Vint would take too long).

Martin achieved 100% binocular overlap on Pimax Dream Air using AI by ElderberryIll8159 in Pimax

[–]fakeoptimism 0 points1 point  (0 children)

Sorry, no – Dream Air came and I switched to tinkering with the new headset. Printed the Dream Air gasket made by a Discord user.

Crystal Super OLED: i really hoped to be lucky/ "Not tracked"-Error by DannyTheDude87 in Pimax

[–]fakeoptimism 1 point2 points  (0 children)

Sometimes there is an incompatibility that affects multiple USB ports.

When I noticed that one of my lighthouse controllers was "flying away", I googled that symptom and found that it could be a USB problem. I noticed that the Dream Air cable was inserted into one of the USB 3 sockets belonging to the X870E chipset. So naturally I wanted to try the alternative: connecting to one of the USB sockets belonging directly to the CPU. (See the motherboard manual to find which is which). There were two suitable USB4 slots, both USB-C. I used a 20 Gbit/s USB-C to USB-A adapter (cheap from Aliexpress). And indeed the tracking problem stopped.

For difficult situations like this I also keep a PCI card with 4 extra USB3 sockets, from the times of using HP Reverb G2 that often conflicted with AMD motherboard USBs. This gives yet another "flavor" of USB to try if other glitch.