DayGlow

From reviews on different sites and some YouTube ones I've heard both ways. Kind of why I'm waiting until fall/winter to pull the trigger to see if it's just a QA issue with first run headsets. It's the Pimax way. I'm familiar with Quadviews, I run it on the QPro add it had eye tracking as well. I've seen mixed reviews on edge to edge clarity of the lens itself. Meta has some of the best lenses out there.

I currently have a QPro and thinking about the Super. I have a 8kx shelved so I can use $400 of its supposed trade-in for the vaporware 12k on the Suoer. Personally from my 8kx experience I'm waiting until late fall/early '26 to pull the trigger so the first run bugs are worked on with Pimax. The only worry I have is the edge to edge clarity with the Super. I originally got the QPro for roomscale wireless VR and planned on using the 8kx for simming with the FOV. But in the end I can't go back from the QPro lense clarity. Much more natural being able to glance around without moving my head. With every VR headset before you have to look directly at what you want to view because of narrow sweetspots. I've seen mixed reviews on the Super regarding this. Some people are saying the edge clarity is pretty good while others complain it gets blurry outside the center of the lense. So far I don't know if it's a quality control issue or an actual property of the lenses. Hopefully it fleshed out as more headsets are shipped.

This is the issue. Turbo mode will cause these crashes

Not sure for other airframes, but the A-10 you can change the slew rate for the TGP and MAV through settings in the aircraft.

You can navigate SteamVR with a gamepad so if you only use VR for sims you don't have to worry about VR controllers.

Cool, though it doesn't detect the eye tracking of my Qpro though.

Can't find any info on this, but it seems there are new options in the VR tab, but they are greyed out - use Quad View _ Track the eyes position Quad views is checked off for me since I have Quad Views on the Quest Pro. Are these options live or settings for a future update?

So turns out it is Taz1004's optimized textures for the aircraft somehow affect the radio even though it's only a texture mod. Once I removed it the radio worked as expected.

I don't know why but the optimized A-10CII textures mess up the ARC-186 radio (bottom FM radio in stack). With the mod activated the default channel is 130mhz and anything below 80mhz gives an out-of-range tone. Once I removed the optimized textures it performs as expected with the default channel of 30mhz

Long press works. A short press also works, but the mouse curser has to be centered in the jester wheel, which was causing my issue

Getting back into the A-10c II and flying some missions. Trying to figure out what is going on. Trying to communicate with JTAC, but I found if I use the ARC-186 at either 30 or 40mhz I just get a continuous tone. If I tune the ARC-210 to 30 or 40mhz I can communicate just fine. Write rather use the ARC-186 for JTAC as summer missions need the ARC-210 for other mission comms

I found that it's difficult to use the Jester UI with VR and head tracking to issue commands as to close the menu afterward the mouse cursor has to be centered into the UI wheel to close it. Kinda defeats the purpose of using head tracking for commands

The tacan for the ship in the instructions is set to 44x, which is the same for Kutaisi Airbase, so when you go to TACAN to land at the boat you aren't heading anywhere near it.

I was running into the same issue. I have v63 on my Quest Pro and couldn't get link to start. I switched over to IL2 and found OpenComposite was crashing. To fix that I took the Oculus App on the desktop out of PTC in the Beta tab of settings. That fixed the link issue for DCS as well.

If you want 64gb one thing to consider is using a program like Primocache. I used it create a ramdisk cache of your SSD(s). I find it makes a noticeable difference in performance loading commonly used programs