วีดีโอ

Thank you sir, for your generous gift! I found the best current setup in DCS to be as follows: Pimax Play: Make Pimax Play OpenXR the default OpenXR runtime. Uncheck "QuadViews" in Pimax Play. Install mbucchia's QuadViews Foveated. In OpenXR Toolkit (if installed) uncheck DCS Install TallyMouse's (handsome devil, I have heard) QuadViews Companion and open it, change something and click Apply. In DCS's VR tab, check use Quadviews and "eye track use the, comrade" Ensure that lens effects and bloom are disabled in DCS. If you are still having issues, you can always revert to PimaxXR as the default OpenXR runtime to see if that fixes it. I haven't been able to get rid of the yellow warning symbol next to QuadViews in DCS since the latest update. Another thing to look at is your OpenXR Layers to ensure that there isn't an odd conflict.. please watch th-cam.com/video/K5zHRtHrOCc/w-d-xo.htmlsi=mEiOrVJUtZcR_7S0

@tallymouse THAT FIXED IT! Well sort of. At least it fixed the Foveated rendering. I can see the eye tracking is working fine but now DCS just hangs the moment I hit "fly now". DCS doesn't crash, everything thing just goes black, no matter which mission I choose. UPDATE: If I uncheck "use quadviews" in DCS the missions launch. But the foveated rendering doesn't work. Thought? Thank you very much. You videos are the but l bridge that make the Pimax products useable for the average consumer. Pimax, if you're reading this. Just save yourself a ton of effort and hire this guy full time!

@@stevenwasmer3827 Which nVidia driver are you using? Also - the latest patch for DCS caused me issues - it turned out that it required updated redistributables. I've only recently done a "nuke the site from orbit" reinstall of my OS drive, and hadn't got around to reinstalling MS Visual Studio yet. The latest DCS patch was causing a crash upon startup that wouldn't fix until I updated the latest C/C++ redistributables: aka.ms/vs/17/release/vc_redist.x64.exe (more info) steamcommunity.com/app/223750/discussions/0/6194225039799348211/ ..also, I ran a repair to find that 8 files were corrupted by the patch!

@@tallymouse I am running Driver 566.36 I tried the DCS repair and installed the redistributables. No luck. Perhaps you're right. I have to start with a ground up reinstallation and reboot of everything. That should be too hard should it? I saw Jurassic Park, I start with the circuit breakers first then try not to get eaten during the boot process. Wish me luck

@stevenwasmer3827 😂

@@wesleyjansen232 Have you tried OpenXR Mirror in OBS Studio?

@@tallymouse i did but without opening steamvr i only get black screen

@wesleyjansen232 What happens if you use PimaxXR as the runtime? Also.. check out my "Fix OpenXR Layers" vid.. that may be your problem!

DCS has added two new boxes you need to check in DCS VR tab: "Use QuadViews" and "Eye-tracking allow".. both need to be checked.

@@OldCooltronix it works with the OG Crystal too - try rebooting! Also, check out my video on OpenXR Layers!

@@tallymouse Thanks for your answer. I'll keep testing...

@@hughjardon5101 Someone else told me I should have returned to Valley and switched aircraft 😂

@@tallymouse They obviously need the hours 😂

Pimax is the only company continually pushing things forward..

@cuttheloop don't exaggerate! .. you mean a 9090 Ti 😂

Have u used quest 3?

@@mayacakil I sent a PCL back and replace it with a Q3. No regrets.

@ yes I have. The edge to edge clarity is slightly better than the crystal light but it also has glare while the crystal light provides a nice clear image

@@FemboyWeebAstolfothanks for the answer. I actually bothered with jagged lines, aliasing and mid distance visuals. I wonder if 2800x resolution solves it?

@@SolidMikeP It's the DCS.exe in the DCSWorld\bin-mt\ folder

I was hoping that would be first out.. i'm concerned that DCS's textures are NOT going to be up to the job of 57ppd

they can't. they won't. they're a defective COMPANY.

@@alistairmulhall2728 I don't think so. My guess is that they got bogged down with lens manufacturing issues with the PCL, but they appear to be using new manufacturers now, so there's hope for the BIG FOV lenses

Yeah, I read the first iteration sucked.

@tonye2458 I'm happy with mine.. maybe I lucked out..

@@georgetazberik6834 I think you can trade in an 8kx for the 12k

This would mean that the panel has an effective resolution of 11.4MP. There is no way they could have 87.3% utilization of the rated square resolution.

@Nobody-Nowhere it's similar to Car manufacturers quoting cubic inches or cubic centimeters.. the displacement isn't truly linear with power output..

@@tallymouse industry numbers, in bicycle industry 27" wheel is bigger than the 28" wheel

It's because for wireless to work, they need the Crystal's Snapdragon XR2, which is something that the Super won't have because people didn't like all the disadvantages that brought.

@@georgetazberik6834 I would think there are asics that could do the decoding also, its not like the XR2 is the only chip thats capable of decoding the stream.

I have 5000 to spend and want the Super 50PPD :)

@montrose699 i know.. me too

Pimax Crystal Super 57 or 50Ppd Fov 135 👍🏻👍🏻 Aplushhss 🇫🇷🇫🇷

@@MrLolof1 I'm a bit gutted that 57ppd is coming out first.. would have liked the 135degHFOV too, but 125HFOV will be a major improvement.

@ Hi Tally !👍🏻 But the problem is the delivery date of the module -50ppd-Fov 135h? Because Pimax in delivery promise I have often suffered from their delivery delay! And even their finalisation of this 135h-50ppd q-led module? Me too I prefer now the 50ppd-135h but now We will already enjoy the Crystal super 57ppd-120fov. And also check this time if the horizontal Fov is 120 degrees and not a false value like Crystal. We were promised 120 degrees and we only had 103 hours! Aplushhss /Laurent 🇫🇷🇫🇷

I'm really excited about it!

I pre ordered the pimax super bundje months ago. I wonder how that goes if I want to buy this version

Thank you, sir, for your kind words!

@@markdeckard7651 I had no idea this channel existed until yesterday and have know about Tallymouse for some time. Agree an amazing asset to the community

I almost wanted to jump out of my chair and bounce while dabbing!

@@johnraahauge4552 for MSFS, yes.

@@tallymouse Thank you. Any chance you will cover MSFS 2024? Right now I have it set to the same as your MSFS 2020 recommendations and getting around 40-43 FPS compared to 55-60 FPS for MSFS 2020. I’m guessing because of lack of QuadViews and better graphics in 2024. Mainly interested in what my OpenXR settings should be.

@johnraahauge4552 Yes - I am planning to make a 2024 optimization guide

@@tallymouse Love it! You deserve much more followers. You helped me out with so many issues (from USB, Loading Issues, OPEN XR and so on) - keep it up.

Hi Didier, If you want to continue to use the QuadViews Companion app, then you'll need to reinstall QuadViews Foveated AFTER you select QuadViews in Pimax Play. Pimax only put a very cut-down implementation of QuadViews into Pimax Play, so it's not as controllable and configurable as the prior QV/QVC

@@johnraahauge4552 OBS Studio along with OBS OpenXR Mirror.

Are you using the original Pimax USB hub? Also, double check your "allow selective suspend" option in Windows Power settings - should be disabled.

@@tallymouseyes to both. Pretty sure it’s an actual issue with the plug itself since reseating the “big” headset plug doesn’t make a difference, but reseating the usb C connector works.

@@tallymouseremoving the serial number sticker that’s attached to the hand tracking module seems to have fixed the problem. Apparently it was thick enough to cause the USB C connector to not get a good connection.

Actually removing the sticker didn’t completely eliminate the problem, but instead I’ve discovered that the two tabs on the module that helps fixate the hand tracking module are too big. They measure 2mm in height and the indention they are supposed to sit in are only 1.5mm deep. This prevents the hand tracking module from sitting flush with the headset and hence prevents a good USB connection.

@@johnraahauge4552 A possible fix with sandpaper?