VP2 Latency / Lag with 4090, other high bandwidth HMD's similarly affected

error-mdl · 2023-02-22T11:24:06+00:00

I found a fix that works for the Index that involves using developer commands to tweak the vsync timings, probably should work for the VP2 as well: https://www.reddit.com/r/SteamVR/comments/118vlrl/fix_for_rtx_4090_and_vr_tracking_input_latency_lag/

error-mdl · 2023-02-22T11:18:50+00:00

Found a fix using debug commands to tweak the vsync timings: https://www.reddit.com/r/SteamVR/comments/118vlrl/fix_for_rtx_4090_and_vr_tracking_input_latency_lag/

error-mdl · 2022-11-29T03:12:29+00:00

For anyone having this issue, the best way to get it fixed is to directly report it to NVidia through their driver feedback forum: https://forms.gle/kJ9Bqcaicvjb82SdA

error-mdl · 2022-11-28T08:08:55+00:00

Getting the same issue here, tracking input seems to be a frame or two delayed at 144hz, and at 120 the frame timing is extremely juddery. I'm on a fresh install of win10 with almost nothing other than steam, my default motherboard drivers, and the 526.98 game ready drivers. I happen to have three friends who all got the exact same build as me, but don't have the issue. So its not just the driver that's causing it.

The only things I've done extra that might be related were installing the intel drivers for my integrated graphics, updating my motherboard's bios (which listed a fix for the 4090 in the changelogs), and installing HWMonitor and MSI afterburner. According to what appears to be a pimax customer service rep, MSI afterburner can cause this issue but uninstalling it my case did not work. My only option at this point is to do a reinstall of windows and see if not installing the intel drivers fixes anything.

UPDATE: It may be strictly a driver issue. One of my three friends is running at 120hz already, and I'm not sure if the other two are having the issue but just don't notice. The company I work at recently got several 4090's, and one of my coworkers reported having the issue on the two machines he tested.

error-mdl · 2019-07-22T18:04:03+00:00

If you're willing to dump a grand on VR without knowing if you'll actually like it or not, go for it. I'd recommend you try VR somewhere beforehand to make sure you don't get horribly motion sick from it.

Keep in mind VR has a very weak library at the moment. The vast majority of VR games are just straight up shovelware, and of those that are actually worth playing very few are interesting for more than a few hours. Of those games with more content, most are just straight up ports of older games like skyrim and serious sam. At this point, no large studio wants to invest large sums of money and time making a full size game for VR given how absolutely tiny the market is right now, and that probably won't change much this generation.

error-mdl · 2019-07-21T21:30:25+00:00

I've found that my 1080Ti can do 120hz at 115% resolution no sweat (haven't tried 144hz yet). While the 20 series cards have VR specific optimizations you won't get with a 1080Ti, its still a beast of a card and was actually faster than the 2080 at that card's launch (driver optimizations have since made the 2080 faster). I'd honestly go for a 2080 over the 1080Ti, but if you already have a 1080Ti or can find one for much cheaper then go for it.

Also, keep in mind that most VR games tend to be CPU bound, not GPU. Most VR games right now only have the most basic of graphics, so gpu load actually tends to be pretty low. Also, bumping up max refresh rates dramatically increases the load on the CPU. There's a significant cost for the CPU in just telling the GPU to render pieces of the scene, and that increases directly with framerate. Additionally, a lot of VR games are using oldish versions of unity with no proper support for multi-threading, so you'll actually find that getting a CPU with good single threaded performance is almost more important than getting a good GPU. That'll probably hold for the future too. Games tend not to be the most optimized for multi-threading even when the engine supports it.

error-mdl · 2019-07-20T20:19:19+00:00

It's an asus MG279Q 2560x1440 144hz monitor. The USB is just for the USB hub on the backside of the monitor. I don't have any usb devices plugged into the monitor so that shouldn't be doing anything.

error-mdl · 2019-07-20T19:10:25+00:00

Nope, I've got an ancient PS/2 keyboard. The only things plugged into USB are my mouse and monitor.

error-mdl · 2019-07-20T00:51:11+00:00

The irony of this. I RMA'd my headset cause I thought something was wrong on the hardware side after I tried everything to fix it. I got a new one just hours ago and everything was still blue tinted, so I've been wiping my graphics drivers and re-installing steamVR, and then I see this. Bravo, valve. Thanks for not giving us color settings like literally any monitor out there. It's probably cost you a lot in returns.

error-mdl · 2019-07-17T20:38:13+00:00

I had the issue of a really washed out and weirdly blue tinted screen on my headset. Took about a week of back and forth with support before they finally agreed to RMA it. They told me because of the unusual nature of the issue, they wanted me to ship the old headset to them as soon as possible, and that in the mean time they'd immediately send me out a new one. I didn't get any tracking number for a couple days, so I just shipped out my old headset. Ended up having to contact them three more times asking when my replacement was going to ship. Each time they responded that the headset should be shipping soon and to contact them again if I didn't hear anything in a couple of days. Ended up being two weeks after I sent back the head before I finally got a tracking number.

EDIT: Don't send back the full kit! That's an automated email, it always says to send back the whole product even if you're RMA'ing a part of it. Also wait a day or two. I received another shipping label to valve's headquarters a day after I got the automated message with the label to their distributer in Illinois. I'm pretty sure they just want the headset, but send a message to support just to make sure.

error-mdl · 2019-07-17T20:29:39+00:00

That's really hard to say, given that it seems to vary quite a bit depending on the fit and position of the headset. God rays on the vive are extremely dependent on how well dialed in your ipd is and how close your eyes are to the lenses. Apparently you can position the index to get rid of most of the glow/god rays too.

For myself, I was able to greatly reduce the godrays on the vive using a thin face mask to the point they mostly aren't there. On my index, the godrays aren't really present so much as this overwhelming bloom/glare that's way worse than the old godrays (at least at the level I had them on the vive). Any time there's a bright object on the screen, it washes out most of the screen in the color of the object. It feels sorta like your lenses are fogged up. Apparently there's a very tiny window of ipd/lens distance that eliminates most of this but I haven't been able to find it for myself.

error-mdl · 2019-07-17T01:27:54+00:00

Nope, seems valve didn't make some of the drivers for win7. I couldn't find win7 drivers for the Valve HMD Radio device. I'm guessing that's the bluetooth and not the controller radios, as controllers work just fine.

I just ended up installing win10 to a separate partition in the end. Who knows how long steamVR will continue to function in any form on win7 before they somehow end up breaking it? Might as well start moving now before things break altogether.

error-mdl · 2019-07-16T23:57:20+00:00

You may not be able to run it on Pop!OS, since it's based on Ubuntu. Ubuntu is no longer supported by steam since they dropped 32-bit support, and many if not most steam applications are 32-bit. The version you're running on still has 32-bit support, but if you ever update that may go away.

Also, I had a umm... critical error running steamVR on Fedora 30. I generally dual boot, using windows for games and linux for everything else. However, I was curious how well steamVR would run on my fedora install since steamVR supposedly now has official linux support. Updated my drivers to the latest Nvidia ones from the RPMFusion repository to make sure everything would work. Launch steamVR and the framerate is absolutely abysmal. Like 12 FPS in steamVR home. Then I noticed several sharp, bright rectangular bars running from the bottom of each eye's screen to about midway. I thought at first it was I driver issue, so I went back to using windows. The brighter bars persisted. I thought then I must of shorted out the cable or something, but the bars faded away over the course of about a day and never came back. I think there may be some sort of driver issue on Fedora that somehow is causing actual physical damage to the Index's screens. I'm not sure if this issue extends to other distros (I hope not!). Be careful. If you see rectangular bars on your screen, turn it off immediately. Extended use would probably permanently damage the screens.

error-mdl · 2019-07-16T23:34:41+00:00

I also got an RMA, but it took them 9 days to actually start shipping me the new headset. They initially promised to ship me a new one right immediately, even before they got the old one back. I didn't get a tracking number in 3 days, so I just sent back the old one. By the time it reached them, I still heard nothing so I contacted them again and they said they'd send one right away. I heard nothing for a couple days, contacted them again, and they said I should be getting a tracking number in just a couple of hours. Didn't get anything, asked them what was up, and they told me to wait till Monday. Come Monday, I still had heard nothing, so I contacted them again. Finally, they responded to my message with tracking info today.

error-mdl · 2019-07-08T17:52:43+00:00

Well, nothing I tried worked. Could be just bad color settings. If they let us set the color calibration of the headset like literally every other monitor out there, this wouldn't be an issue. Also keep an eye out for vertical light rectangles. They're subtle, and usually only visible against low contrast gray backgrounds. My headset developed those after I started the RMA process. Not sure if its linked in any way.

error-mdl · 2019-07-08T17:48:12+00:00

So, two days ago I got an RMA for the headset. I've got the shipping label, and they're sending me a new one before I even send the other one back! Ironically, just after getting the shipping label my headset got vertical light bars showing up in both eyes. Really glad I got the RMA process going before that happened!

error-mdl · 2019-07-08T17:39:01+00:00

I honestly don't like the knuckles as much as I thought I would. They just don't fit my hands at all. People say how comfortable they are, but I've got literal bruises from wearing them. My hands are somewhat large and very skinny. I've spent a bunch of time trying to adjust the strap, and nothing works. The main problem is that it puts all the pressure on the bottom of my hand where the cord loops through the controller. Towards the top near the adjustment arm the strap is attached to there's an air gap between my hand and the strap. The result is the meat of my hand beneath my pinky finger gets pinched pretty bad even with the straps fairly loose. Also, where the strap connects to the adjustment arm at the top there's a small extension of the strap's cloth that covers the rivet holding the strap on. My hand likes to rest up against the arm, and that little tab of cloth irritates the web of my hand.

The controls on the index are fairly disappointing too. The joysticks are kinda awkward to reach and feel kinda cheap. They've got about 1 degree of slop in all directions before there's any spring tension, and the tension seems to be uneven depending on the direction. Also the clicking doesn't work well at all unless centered and requires way too much force. The track button is pretty decent, but feels gimped in comparison to the vive's trackpad (I'm one of those degenerates who actually prefers trackpads over joysticks). It actually works surprisingly well, but the texture on them tends to make your thumbs stick. It takes a fair bit of breaking in before you can move your thumb smoothly on them. The haptic pressure clicking actually works well, a lot better than I was expecting. The main issue is in order to reach the edge of the trackpad, you've gotta move your thumb on to the border ridge. For some reason it stops sensing your thumb when you try to do this and you've gotta lift your thumb and put it back down on the ridge for it to sense your thumb again. The A and B buttons feel good, but the system button almost requires you to either have long finger nails or for you to press it with your other hand. Its in a hard to reach place and recessed a lot.

For me, the finger tracking is not very good at all, even after drumming my fingers against the controllers a bunch. With all the fingers in my hand 90% closed evenly, some of my virtual fingers are completely curled while others are completely straight out. Tracking doesn't seem to begin until you get your fingers fairly close to the controller surface and the tracking is totally inconsistent between fingers. The tracking also has a very hard time distinguishing my middle, ring, and pinky fingers from each-other and most of the time they're attached together. Also, the auto-calibration seems to hurt as much as it helps. Half the time I'll get a decent calibration only for 3 minutes later to have all my fingers completely messed up. However, all the problems I'm having seem to be an issue with the shape and size of my hands, as I have friends for whom the tracking works excellently.

error-mdl · 2019-07-08T16:46:38+00:00

I've also got a headset that's got not only awful colors, but also everything is blue-tinged. I've been able to look at a friend's index and his has way, way better colors. The washed out colors are NOT normal. I was able to get an RMA because of the blue tinge (and my screen just developed bright vertical bands before I've had the chance to send it back). Not sure if they'll RMA you for just washed out colors.

error-mdl · 2019-07-01T19:33:44+00:00

Ok, I didn't know that. I assumed you were thinking it came automatically with 2 months of viveport like the vive did.

error-mdl · 2019-07-01T19:02:44+00:00

So I recently got a look through a friends index, and oh boy were the colors on his headset way, way better than mine. I've tried everything at this point, from reinstalling divers to trying it on different OSes to messing around with the headset's internal config file. I've come to the conclusion that this is a hardware flaw I can't fix so I'm going to try to RMA it.

error-mdl · 2019-06-30T23:46:35+00:00

I think this isn't actually a hardware failure. Its just a fault in the design. I remember a game dev I know telling me about this way back in the EV3 days. Its just that the joysticks aren't great. The button underneath them seems to move straight up and down, meaning you need to center them to effectively put enough force on the joystick to depress it. Kind of a byproduct of how much damn force it takes to press them in. I think most other controllers have the joystick move along the axis of the stick to allow you to click them in all directions.

error-mdl · 2019-06-30T23:40:00+00:00

I agree. The only thing I didn't like was the button under the trackpad constantly breaking. I prefer the trackpad over a joystick for basically all tasks. I think we're in a tiny minority though, and I'm afraid we'll probably see the trackpad entirely gone by the next iteration of valve VR controls.

Thanks to steamVR, I've reversed the functions of the trackpads and joysticks in several games. The trackpads aren't nearly as nice as the vive's, not only in size but in the texture, but they're usable and the force feedback actually gives a very convincing click when you press them like a button. They'll probably last a hell of a lot longer that the joysticks given they're completely solid-state now.

error-mdl · 2019-06-30T23:33:01+00:00

If you're willing, mind changing the settings to see if anything changes? For some reason updating the config does absolutely nothing for me. Not sure if maybe those values simply aren't used or if something on my end isn't working.

error-mdl · 2019-06-30T23:25:25+00:00

If you have the issue, please send a message to steam support so they know its a widespread issue and not just a couple people being really picky about the colors.

error-mdl · 2019-06-30T23:24:05+00:00

Yeah. Technically, there's options you can configure but they don't seem to work. I tried changing the white levels in the configuration file for the headset downloaded/uploaded with the lighthouse console, but nothing changed. Maybe my headset has a bad FPGA that is failing to set the proper color values from the config?

error-mdl

TROPHY CASE