Moxica

Absolutely. The ball is in ED's court. There is no more I can do.

Many similarities to my situation, and I wanted to mention that the F-18 sidepanels allways have been blurry/low-rez looking for me. That has been through all of my VR sets: Pimax crystal light - HP Reverb g2 and Oculus Quest 2. That said, I've had the weirdest experience with PCL regarding sharpness. Without 1.5 correction, center is blurry and sides/top/bottom is sharp. Almost as if FFR is reversed/inverted. I bought the VR-wave prescription lenses, and now it is pretty good. I do have some sharpness issues here and there/now and then. I have ended up on a few "bankers" settings that I will not change: Most important for sharpness: NO DLSS, and no AA! (On PCL) Visibility range on ULTRA in DCS. -Not using OpenXR toolkit. -Not using Pimax play ffr. (Mbuccia Quadviews made the biggest improvement for me.) I repeat Pimax play ffr to off. -Here is my Quadviews setting fwiw: null

Happened to me also. Restart or "shake" (change a setting and press apply, restart DCS)the Quadviews companion. It was not active after update..

Also, there IS a tracking issue. Pimax need good light to track properly. Due to the lack of daylight outside today I learned that the (40W) light in my roof was insufficient, and resulted in "out-of cockpit" experience, but most of all, stutter was extreme. So I set up some very bright photo/studiolights behind my seat, and stutter in menus appeared to be (much better) gone. But then again, with DCS one can never be quite sure.

I don't think so. Maybe I dont recognize/identify the API name correctly, but you want Mbuccia.s api over Pimax. Because its better. Pimax should hire Mbuccia.

I use mbuccia's Quadviews. And I could read the following: "support for Pimax OpenXR runtime (requires Pimax Play QuadViews to be unchecked, mbucchia's QuadViews Foveated to be installed)." null

No AA for me. But there are two kinds of stutter. One performance/setting dependent that is affected by settings. Then there is that micro-stutter visible in cockpit when moving head horisontally,or looking out to the sides. So fast at times that it turn into a tiny blur. Last one was gone for a while. But now it is back and annoying as frack!

I had my best "Pimax" day yesterday, after update, and maxing out Hz and FPS slider: 120Hz on pimax and FPS slider to max. Textures to medium. FPS over 100, and brilliant graphics. I was, however conservative (aka coward) in my choice of test environment. A-10 in barren, but target rich area in Iraq, and an F4 Quick mission. Enjoyng while it last kinda.. Excited to test more after work today.

Crystal lights got the following: "Tracking Calculation: Reduced tracking algorithm calculation time, decreasing abnormal latency."

Ye. That's how it works.

It is not available through the app yet. Firmware on my Crystal lights:: V1.0.14 Pimax support sent me this link: https://pimax.com/pages/downloads-manuals And also this one: Hi Try below link. https://dlappstore.pimax.com/release/play/PimaxPlaySetup_Release_toC_V1.36.01.01.02_202412272021.exe Note:

Did you get the firmware update? Because today I had some significant progress: Changed from 90Hz to 120Hz, and moved FPS slider to max. Smooth gameplay with 100-120 fps on "best scenario" Overall smooth, and the best I've had since I got the Pimax. My former "big success" setting was updating Quadviews, and adjusting default foveated res (was150%) to 100% Not sure if significant, but the other dayI took Mr Sukebe's tip and set Textures to medium. They still are, and I don't see much difference in image quality.

New firmware and software today. Had a decent flight with 90 fps average. Until I got closer to the FARP, and it dropped to 29 FPS. So I alt tabbed to find out what was going on. CPU nwas fine, but ethernet went wild. null

No. OpenXR toolkit does not support Quadview. Mbucchia has called it obsolete..

Will try immediately. (Mine is 90 atm)

I got an email from Pimax support today. This one is not available from app yet. Program and firmware update: https://pimax.com/pages/downloads-manuals

Oh! I just made another thread/topic about this. Could it be some old weather setting in older missions and editors? I seem to have flown straight into the center of it:

I've seen traces of them on several occations. In Ah64. But today in A10 at 11900ft I kinda went into the "eye of the storm" In "Operation fury" Mission 9 or 10. (The one with the low pass fly-by for ground troops morale) OPF_09.miz OPF_10.miz dcs.log DxDiag.txt

I was good with my HP Reverb G2's. Got rid of all stutter.

Sadly, no. Wrong socket. (AM4 vs AM5) Could try a Ryzen 7 5800X3D though..

Same here. No DCS setting change the micro stutters, which is there regardless of FPS. I suspect Pimax Play (including the eight to ten other PI processes running) to be not-quite-right. Stutters kinda remind me of tracking problems. I have this microstutter even in DCS menus.

Suddenly keybind does not work. AH64 has forgotten, and I have to remind it by opening controls menu, press forgotten button, and "OK". No re-assign. -Now it works again. (Mostly "Slave" and "lase" it appears)

Does this setting apply when starting from DCS shortcut, or do one have to start from Pimax app?

Should not be that complicated: null

Right or wrong, I just want to commend the langauge, and writing skill in this piece.