Jaw_B

Any comment on this @C.T. ?

Is this firmware out of beta yet? Been a very long time since we saw a firmware update. 1 year ago since the last public release. Has the vive pro 2 reached end of life/support?

Barely use my Vive Pro 2 anymore.. but I tried this beta and it seemed like going back to pre-2.0.24.x as I got zero tearing, and 20-25% reprojection in Extreme-120hz on a 4090.

Thank you for letting me test. Unfortunately(?) you were right. The issue existed in 2.1.24.1 as well 😞 Guess I had not tested BigScreen in 120hz that much. When moving, especially your hands, you get reprojection 20%-ish giving "double vision" and slight stutter. However in 90hz there is no such issue. Oh well. At least I tried 🙂

I had the same(?) issue with my Samsung Neo G9 (49" monitor). Either computer would restart, or the image on the screen would become corrupt whenever I started SteamVR. At the time I had a rtx3090 gpu. To be honest I do not completely know what resolved the issue in the end. Might have been one of the firmware updates from Samsung for the monitor. Funny thing is that I also have a LG CX in the same room, so that was my workaround too 🙂 Try to run the Samsung monitor connected through HDMI to the PC (and not displayport) and the vive pro in a lower resolution. I believe DisplayStreamCompression (or some kind of conflict related to DSC) can be the issue causing it.

I didnt realize there were 2 parallell versions. I'm on 2.1.24.2 installed through Steam.

Well, I would be more than happy to give it a try. Should be very quick to test.

New beta and not a single comment? 😕 Anyways, I tried it for a couple of days on my RTX4090. The screentearing is still an issue. Slightly worse than 2.0.24.1 I belive, but it could also just be random luck. However (BIG however) the reprojection issue is now back in 120hz. Tried Bigscreen and got a constant ~25% reprojection, but not a single framedrop. Switched to 90hz, and the framedrop is gone again. Just like pre 2.0.24.1. Could I PLEASE please have access to install 2.0.24.1 again @C.T. ? That beta worked much much better on RTX4090.

Just so I understand. What did you uninstall, and what is your complete setup now? (vive console vetr, steamVR ver, nvidia drivers ver)

2448x2448 is the panel resolution. Usually(?) you need to supersample a bit to compensate for the lens barrel distortion. Not sure how much is recommended though 🙂 But +25% probably isnt bad.

Can someone else try beatsaber in 120hz and see if you get massive reprojection when running at your standard resolution (3000x3000 or so). And also, does it default to steamVR lowest resolution(1200x1200 or so) when you start it? Very strange.

No tearing at 90hz. Its only in 120hz. Its an "artifact" that was introduced on the beta of vive console in november. It looks a bit like a fat horizontal line that moves up and down in the top half of your view. And it comes and goes. But in this beta its better than before. So its not something that has to do with high gpu-load, and that type of tearing. (You can read about it in the longer thread about the 4090 issues) And Im setting the resolution manually in SteamVR to around 3000x3000. (a little higher for 90hz, and a little lower for 120hz). More than that is very heavy on the GPU, and I want to avoid reprojection due to the GPU not beeing strong enough. (4200x4200 pixels is an insane amount of pixels to push. Thats more than 2 times 4k resolution PER EYE. and 120hz at that)

What do you use for monitoring then that works better?

Also tried. Running a 4090 with latest nvidia drivers 531.29. SteamVR latest beta. HAGS off (and RGB turned off). Using fpsVR for monitoring. SteamVR resolution at ~2800x2800 per eye. At 120hz Im getting much less screentearing than before, but it is still there. Usually in the upper half of the screen. But now I can play for minutes without seeing it, so its an improvement at least! (but not quite there yet). Also, when runnig beatsaber (which for some reason always defaults to the SteamVR minimum resolution. ~1200x1200 per eye) it works fine at that resolution, but very blurry. When increasing the resolution in SteamVR to ~2800x2800 for beatsaber I get 100% gpu usage and massive reprojection. A little strange for a game that (shouldnt be) demanding at all. (but that could be from other reasons than this vive console update).

I usually aim for ~3000x3000 per eye when running 90hz and slightly lower when running 120hz. This in in steamVR and on a 4090. You really shouldnt be running 150% (which is like 6000x6000 per eye). That is waaaay too demanding for any existing gpu.

Think this thread contains multiple issues at the same time now 😕 Some have issues with their 3000-series cards on vive pro 2, some are talking about vive pro 1.... Think their issues are "fixed" now. But the 4000-series gpu and vive pro2@120hz is still as broken as when this thread was started. (which is what this was about in the first place?). Would be nice if HTC could comment the situation/status. @C.T.?

Does it fix it for you in 120hz as well? 😕

Find it intresting that some have huge lag/latency/stuttering issues even in 90hz. Cant say its something I notice myself(?). Is it possible to measure? I do get the occational "pink line" but nothing dealbreaking. I have resolution set to ~3x3k per eye, and HAGS off. (that removed alot the the stuttering for me) 120hz however Is something else completely. I get bad tearing (that comes and goes) What settings/drivers do you use? Im on a Strix4090 and latest (non-beta) nvidia and viveconsole (from steam).

Wow. That gives hope that they are actually working on it 🙂 Would be happy to test it out too if needed.

On the topic of performance, I agree. I also wonder if VR (using the pro2 headset) is getting more demanding. I dont remember any issues on my 3090, as I always ran it on Ultra/120hz. But even in SteamVR home@90hz@3k/eye Im getting 70% GPU usage now. Considering I now have a 4090 vs 3090, and how much faster it is, it would mean that I could not even run SteamVR home with my current settings on my old GPU. But I did. With higher settings. So something is going on? I also informed Inet.se which is one of the biggest hw retailers in sweden that they need to notify potiential customers that the vive pro 2 is not compatible with the RTX4xxx series.

Yes, the vive pro 2 works much better in 90hz than 120hz (which is broken) on a 4090. That said, Im not really sure if/what issues exist in 90hz still.

@C.T. Its now been almost 4 months since the RTX4xxx series was released with the 4090 (Oct 12th). If we are beeing honest here, should we expect this to ever be fixed, or should we return our Vive Pro2? The 4xxx series is the latest generation gpus from the biggest gpu company. This shouldnt be an issue.

Just tried 2.0.22.6a on NV 528.24 and the headset at Ultra/120hz on a 4090. SteamVR set to 50% resolution (~3x3k) Behaving very similar to the forum-beta we had a while back. Getting screentearing that comes and goes. (Possibly a little less than the forum-beta, but not really usable).

Tried the Beta-update of Vive Console (I think. It was hard to tell as it had the same version-number as the "normal" beta?). The good, I got almost ZERO reprojection (0.1%) in 120hz (at 52% resolution. 3300x3300-ish) when trying SteamVR Home. Before I got at least 30-40%. The bad is that it introduced a strange graphical artifact. Looks a little like screentearing that "floats" up and down. It comes and goes, so its not present all the time. I tried with HAGS on and off but made no differance. At 90hz I didnt see the screen-tearing artifact, although i did not try that long. Whats also interesting is that having AURA-RGB enabled no longer seemed to cause any dropped frames. (tried with both on and off, and really saw no difference)

@C.T.Would also be happy to try out the new version for 4090. Btw, anyone tried the new win11 update that came out today(?) that is supposed to help out 22H2 stuttering issues? (KB5020044 I belive)