The argument doesn’t need strengthening, there 100% is a problem and it is 100% is due to a change in the way the 4090 handles compression / DSC and Pimax 100% knows about it, irrespective of what Heliosurge is stating, and is dragging their feet on it JUST LIKE THEY DID FOR 6 MONTHS WITH THE TUNDRA TRACKER ASSIGNMENT PROBLEM.
https://forum.tundra-labs.com/t/known-issue-1-incompatibility-issue-with-pimax-pitool/28
Are you using the optical cable? I am, maybe this is another variable that we overlooked.
Other potential variables:
Unit Build number (first 4 digits of the serial number, under the HMD):
2075 here.
Refresh rate: 90 Hz here
FOV: Doesn’t matter, problem happens at large and normal FOV as per both your and my troubleshooting.
Many of us notice the latency, did you relay to them that the problem is latency / lag and not frame-skipping? Turning off monitoring software only reduces the frequency of the random frame-skipping from once every 5-10 seconds to once every 30 seconds or so. The frame-skipping does NOT appear as a frame-time spike in fpsVR and it is NOT related to GPU load (happens at 35% load in SteamVR home) nor CPU load or anything else.
The issue exhibited by the 8KX is identical to that exhibited by my VP2 at 120 Hz. If I reduce the refresh rate of the VP2 to 90 Hz the problem completely disappears, I can even run MSI AB and there is no frame-skipping whatsoever.
Again, THE PROBLEM IS THE LATENCY / LAG THAT DOES NOT REFLECT IN MONITORING SOFTWARE.
That the problem lifts @ 90 Hz and that Varjo owners have stated that Varjo ACKNOWLEDGED that there was a change in the way the 4090 handles compression / DSC tells me that this is a compression / DSC problem and that it is up to the HMD manufacturer to rectify it via a firmware update:
My varjo aero had similar problems with 4090 untill varjo updated their drivers. It works great now and had something to do with the way compression is handles in the new cards. I suppose it’s up to htc and pimax to fix their stuff
And:
> So Pimax also stutters at max FOV? What’s the common denominator here, NVIDIA software?
I think the current line of thought is it’s a driver issue at high throughput…possibly DSC related. Which likely means an Nvidia fix 
I’ve stated this, I don’t know 5 times now but I will re-emphasis here in all caps:
THE PRIMARY PROBLEM IS LATENCY / LAG THAT CANNOT BE MEASURED IN MONITORING SOFTWARE, I.E. FPSVR, ARE NOT RELATED TO GPU OR CPU FRAME-TIME SPIKES WHATSOEVER AND I SUSPECT THAT MANY, MOST, LIKELY ALL WHO SAY THEY HAVE NO PROBLEM ACTUALLY DO HAVE THIS PROBELM AND SIMPLY ARE NOT SENSITIVE TO IT BUT I DON’T KNOW HOW YOU COULD NOT SEE / FEEL IT BECAUSE IT’S REALLY F’ING BAD.
I understand your frustration, but careful making assumptions and that everyone is just not seeing it while jumping to conclusions, m’kay. There’s obviously a problem in some cases, but it does not appear to be universal.
Hell, there was an issue that nvidia officially acknowledged where the 3090 TI was having issues with certain VR headsets and would not work with them without a DP Extender, Pimax and HP also acknowledged it. it was a decently common problem. HOWEVER, there were still people who could have their HMDs work perfectly fine without any DP extender and I know at least two people who did not have the problem, despite many others having it, myself included.
It very well could be the same thing here.
Fyi I am using the optical cable with the 8K X, to rule that out.
And much as it is painful to see the frustration coming out in other people, it is actually a little comforting for me as it means I am not suffering this all on my own.
What is more likely, a percentage, a majority even, of users who CANNOT DISCERN THE LATENCY / LAG ISSUE or there being some variation in the DP cable, DP cable quality, or some other hardware level “gremlin”?
Because that’s basically what you’re stating here, that the issue only affected “some” DP cables.
Do you even understand what you’re trying to explain from a technical perspective?
There is next-to-no variance in DP cables, GPU’s, Displayports, etc etc. and etc. but there sure as hell a variance in PEOPLE’S ABILITY TO DISCERN SAID PHENOMENON.
I am MOST certain this problem plagues ALL 8KX’s and that those who CLAIM they have no problem simply CANNOT DISCERN SAID PROBLEM.
Otherwise, what is the variable?
Some heretofore variation in DP cable transmission strength? Manufacturing defects creating variation in DP ports?
The industry has become so standardized, variation of this sort is incredibly minuscule.
If I disable MSI AB I could potentially live with the latency lag and if it was my first time donning the HMD and I had no reference port I may even consider it just how VR looks and feels and maladapt to it.
In regards to potential hardware variation, Pimax DID make a hardware change with the 8KX (2075 and 2076) I have the older model, there are also TWO separate cables to rule out. So this problem MAY only affect the older 2075 unit with the optical cable on the 90 Hz firmware for all we know and thus, “I don’t have the problem” is coming from people who legitimately do not have the latency problem because they have the newer 2076 unit, or they are only at 75 Hz with the older unit and / or are not using the optical cable.
But to suggest that there is a variance from the DP 1.4a port or Displayport cable itself, I mean how? Does one cable have more copper winding? Were some 1.4a ports damaged somehow? Or is it not hardware variance but the end user’s inability to discern the lag / latency?
Potential variables:
Unlikely variables:
Known variable:
RTX 4090
Remember, Varjo acknowledged the problem even though some Aero owners were completely oblivious to it and the problem 100% AFFECTED ALL UNITS BECAUSE THE PROBLEM STEMS FROM THE WAY THE 4090 HANDLES COMPRESSION / DSC AND ONE 4090 IS NOT GOING TO MAGICALLY HANDLE COMPRESSION / DSC DIFFERENTLY FROM THE OTHERS AS THE ISSUE UNIVERSALLY AFFECTS ALL 4090’s AND AT PRESENT CAN ONLY BE RESOLVED ON THE HMD FIRMWARE SIDE, I.E. VARJO AERO RESOLVING SAID PROBLEM IN ONLY MATTER OF DAYS.
What is more plausible here, the end-users inability to discern the phenomenon or some heretofore undiscovered Displayport hardware variation causing the problem?
Here’s what Pimax can do, they can set up one test machine with an RTX 4090 and one with a 3090 and they can start SteamVR Home and put one HMD on and then take it off and try the other and note the lag / latency with the 4090 or absence of it with the 3090. Why am I suggestion how Pimax investigate the issue? Oh that’s right, they are inept and incompetent and it took their janitor whose side job is their lead sole engineer 6 months to fix their Tundra Tracking Problem.
I have the older 2075 model. And yes I see the issue in 90, 75 & 60hz.
But interestingly I also have exactly the same issue on my 5K XR.
Optical or standard cable?
It’s possible that only the 2075 unit is affected, the 2076 is capable of 120 Hz which could mean that it handles compression / DSC better (axiomatic but must be stated) and therefore does not have the problem.
If we can get a poll going and narrow this down to the 2075 unit then we may get somewhere, unfortunately, 2075 owners who do have the problem but cannot tell will say they don’t have said issue but that you and I both have the 2075 unit is pointing somewhere.
Optical cable.
FYI I got an update from Pimax Support on my ticket last week that they have learned a bit from other users and are testing different scenarios, with a special team investigating the issue.
So that is acknowledgement at least, even if it is not publicly stated. On that basis I have accepted it will take a little time and am hopeful that we will see a fix in a reasonable timeframe.
Apologies I should have shared this sooner.
There’s no need to angrily CAPS LOCK everything and talk like we don’t know what we’re talking about dude. The example I just gave you kind of refutes your whole point, your DP port and saying how the industry is so standardized works against you here because the problem still happened. There can be any number of reasons with how many moving parts PCs have. It was common enough that multiple companies acknowledged it and it was an almost universal problem. Emphasis ALMOST.
I have a 2075 HMD. I’ve used multiple cards on my 8k X. It is simply not there for me.
I am not saying that it’s not occurring for you or anything, there’s obviously some kind of problem here effecting users. But jumping to conclusions does not help and may lead to wasted time spent chasing down the wrong answers.
He doesn’t want help at all, he just wants validation. xD
I suspect some SuperDooperFunction of the Gen11-13 boards slows something down somewhere.
You have a 4090?
Sure thing buddy, I’m just seeking attention, meanwhile not only have you not been helpful whatsoever but now you’re borderline seeking conflict here. F off?
FYI Nvidia have come back to me confirming they DO NOT recognise there is an issue with 4090 & VR so they are not working in a solution.
They consider mine a single user issue only.
I’m sorry for you. Hope it clears up quickly. 
Just downloaded the latest Nvidia driver. Now I also have small lags, but only in FS2020. The rest still runs like butter.
(Turned laps in Project Cars and Squadrons.)
Ahh, and DCS is still disaster But that’s due to 2.8 and ED is working on it.
Throw the 8KX in the trash where it belongs. I don’t think this is an Nvidia problem, it’s an HMD manufacturer problem. Having returned to the VP2 I can finally play Starwars: Squadrons without issues / needing to run Parallel Projections. With PP enabled there is some weird shader bug running down the middle of the image in the 8KX.
Seriously, get another headset, this issue will never be fixed, Pimax haven’t even acknowledged the problem.
I’m totally over any excitement I had for the 12KX, if Pimax can’t acknowledge this problem and fix it, why would I drop $2k on their newest headset that will suffer from the same problem?
I’m not gonna do that. Honestly there isn’t another product that works for me as far as the combination of FoV and resolution.
To be clear, Pimax have acknowledged the problem to me in Support an say they have a team set up to investigate this.
Don’t hold your breath, it took Pimax 6 months to fix an issue that entailed 30 minutes of work relinquishing tracker assignment from Pitool back to SteamVR after I and others brought it to their attention and them acknowledging said problem and stating they would fix it.
I’m really glad I didn’t sell my Vive Pro 2, it has superior colors and contrast compared to the 8KX, a sharper imager, and still is about 115 HFOV and I have no issues with Star Wars: Squadrons whereas this title is unplayable in the 8KX, even with PP enabled.
There is a 120 Hz mode as well, and the race is on as to who can fix this problem first as it’s identical in the VP2 at 120 Hz.
My money is on HTC.
Don’t get me wrong, I love the FOV, I truly want to love Pimax, but the speed at which they address issues that are brought to their attention is horrendous, unacceptable actually, they also overstate new products and delay them quite a bit and when they are released they are half-baked and riddled with problems. That 155 HFOV, nothing beats that however.