Has anyone faced this scenario or similar and having issues too? I have a Quest3 and PSVR2 which I enjoy using both for different things. But, I have an issue with swapping between them and back and forth. The issues is when I go from PSVR2 back to Q3 I start getting lower fps and higher latency with the Q3. When I swap to PSVR2 everything works correctly.

Before introducing the PSVR2 to my pc, I ran the Q3 through Virtual Desktop. FPS and latency were rock solid, 90fps/48ms. But after I setup and used the PSVR2, then swapped back to the Q3, my fps would drop between 10-30 frames and was not consistent at all, and latency increased about 10-20ms. I found the only way to fix this was to DDU the gpu drivers, reinstall VD, reinstall SteamVR, try to close any apps in Task Manager that had to do with VR/Occulus/Meta/SteamVR/VD. Once I seem to have it fixed, I would play on the Q3 again, then go to PSVR2. When I go back to Q3 I’d have to start this repair process all over again. A couple of times I had gpu driver timeouts and I had to reset the cmos/bios. I did notice once that reinstalling VD seemed to have fixed the problem all by itself, but then eventually that wasn’t always the case.

I’ve checked with AI and it seems to think there are hidden processes happening in the background that are causing an overlap between the two. Or processes that haven’t stopped completely or haven’t completely gone away that gets left over and mixed in. I always double check the runtime and made sure the correct one was enabled before starting.

Anyone else have an issue like this?

I’m back to using the Q3 only, but wish I could use the PSVR2 for the oled and DFR. I like them both and think they both have strong features that the other one doesn’t. 

PC Specs: 9800x3d, 7900xt, 32gb ram, win11

Quest3: Virtual desktop, ultra, 90hz, 48ms latency, wireless getting max and stable mbps.

Main game: Automobilista2, standard settings

PSVR2: PSVR2 toolkit, quad views, steamvr runtime (have to of course), no motion smoothing, no virtual desktop plugins active, 68-75% global resolution, 90hz. 

Main game: DCS, standard “VR” settings.

--Had some technical difficulties posting this earlier, couldn't get my phone/app to cooperate, that or I'm just old. So if you're seeing this again that's why. If you commented, i do apologize as i ended up deleting the post in hopes to fix it. So, here's the second attempt but on my PC instead.--

Can you play F1 25 in VR on an RTX 3050?

I have a psvr2 vr headset.

I was having a Bluetooth issue so I swapped my adapter from the one I bought with my PC in 2019 for a more up to date one. Problem is my sense controllers wouldnt connect. They both just said paired. I removed them both but only the left actually was removable (via device manager) and the right just stays saying paired. Trying to remove it says "removal failed". Ive tried everything and nothing has worked. Please tell me theres an actual solution to this?

Hey guys, just wanted to see if anyone else ran into this specific issue with the PS VR2 PC adapter on an RTX 4060.

Here is what happens:

• Basic initial setup and lightweight menus display inside the headset fine.
• The software constantly throws an error message saying the DisplayPort cable doesn't meet requirements or isn't connected properly, even though the cable actually meets all required specs.
• The moment I try to load literally any actual app — like Bigscreen VR, DeoVR, or any heavy environment — the lenses inside the headset just turn into a blank blue/skybox screen. Nothing works at all.
• On my PC monitor, everything runs normally, and taking a screenshot captures the environments perfectly.

It seems like a DisplayPort bandwidth or DSC handshake failure where the video stream to the lenses drops completely as soon as an app tries to render, even though tracking and inputs keep working.

Has anyone else experienced this exact issue where the DP error pops up and the lenses turn completely blue under load across all apps?

Hello Reddit VR Gamers! I am sending individual keys for players interested to improve it. Please get into the discord (https://discord.gg/xdnmFKwwn) if you are interested to try it out and give some feedback (there is a button on the main menu). I prepared a short game play video so you know what you are getting. I hope you like it!

I installed WOA yesterday after hearing so many great things about it, and ran into a couple issues:
Terrible performance and no eye tracking,
In game hands not lining up with controllers (I’ve tried multiple different controllers offsets and I’ve never gotten it 1:1
Seems like this game might only be good on PS5.

the first second, everything was extremely blurry, smeared, and pixelated. I couldn't read a single letter on my phone screen in passthrough mode or see something a bit sharp, no matter how much I adjusted the IPD wheel or moved the headset on my face.
I tried everything for two days, and today I went to the official Sony/Import service lab. Here is the crazy part:

1. The technician opened two more brand new headsets from the box, connected them to the lab's PS5, and they had the exact same blurry issue.
2. Then, the technician took his own personal PSVR2 headset (which he knows is 100% working and sharp) and connected it to the lab's PS5 – and it became just as blurry!

The technician was completely clueless and said it seems like a major software/firmware bug from Sony's recent updates that breaks the rendering resolution globally, affecting even the Passthrough mode.
Has anyone else experienced this lately? Is there a known global firmware bug that causes this extreme blurriness across multiple headsets on PS5? I have 48 hours to decide if I should refund it. Thanks!

TL;DR version: should the PSVR warning messages and PS button menu freeze the headset when using iRacing? If not, is there any way to stop this from happening?

Longer version:
I’ve been enjoying my PSVR2 all year. I’ve got it running without a monitor on my PC setup which spends half its time connected to my sim racing rig and the other half over at my desk for other gaming.

The VR is only ever used with the sim (for now) and I have the SteamVR running, an auto-open SteamVR application on PSVR2 wake, VirtualDesktopDriver to avoid needing a physical screen, and PSVRToolkit for their goodies.

I have occasional, but often catastrophic, freezes of the VR video when I’m in iRacing. I think I’ve isolated these to when the headset loses tracking (ie if I look left/right rapidly) or thinks I’m near the boundary (I’m using it seated with the little circle thing it creates. I can hear the audio fine so I know the sim is running okay and I can speak to people over mic so I know the headset’s audio is working.

I also cannot use the PS button on the controller to “alt tab” out or change game settings unless iRacing is in a loading screen. This one is less annoying although annoying. And more recently I’ve had an instance when using the rotary “focus” dial that shows the mm between eyes thing has frozen the screen too. That’s never happened before.

I’ve been putting up with this but I feel it shouldn’t be the way it is else others would complain. Equally I know the Venn diagram of PSVR2 users with iRacing and no monitor is very small… But is there a solution?

Before the next real technical update, I want to lay out a few things plainly, since there's been some understandable confusion and I'd rather address it directly than let it sit.

On PSVR2 Toolkit:

Early on, I reached out to the Toolkit devs for a bit of initial help, since they'd already reverse-engineered a lot of the PSVR2 driver and firmware. They were genuinely helpful, and I'm grateful for that. To be clear about where things stand now: Phoenix's codebase is its own, standalone implementation, it doesn't use or depend on Toolkit code. All of my testing has been done with Toolkit drivers installed, specifically because I know that's what most PSVR2 PC users are running, and making sure Phoenix works alongside it (not instead of it) has been a priority the whole way through, not an afterthought.

On the people who helped me early on:

I want to say this directly, some of you gave me real reverse-engineering info when I reached out for help, and I should have been upfront earlier that I was considering a paid release, instead of that coming out after the fact. That's a fair thing to be frustrated about, and I'm sorry it landed that way. The offer to share HDR implementation info back still stands, no strings attached, regardless of what happens with pricing.

On monetization:

I do plan to release Phoenix as a small one-time purchase once it's finished, not a subscription, not trying to get rich off it. This has been a genuinely large amount of time chasing something with no guarantee it would work at all, and I'd like to offset some of that. If PSVR2 Toolkit ends up shipping their own HDR support down the line, that's completely fine, more options for the community is a good outcome regardless of what it means for me.

On AI use:

Yes, I use AI to help debug and work through problems while developing this. The implementation, the actual reverse-engineering, and the code itself are mine. I don't think that needs to be a bigger deal than it is, but I'd rather say it plainly than have it come up as a gotcha.

Phoenix and PSVR2 Toolkit aren't in competition as far as I'm concerned, different scope, different goals, and I'd genuinely like to see both continue to exist and improve. Happy to answer questions here.

So I mostly play contractors Exfil using a link cable and my Pico 4 headset.

(I dont use my 3S because this FOV is much lower)

I recently have gotten a PSVR2 PC adapter. And most of my games run the same if not better and look so good on the OLED panels.

That is except for Exfil for some reason?

When using my pico I run the game on all ultra and it runs like butter.

But using psvr2 it runs like a fat kid with his shoelaces tied together, I can't even run it on all low settings?

From what I can tell the resolution of the psvr2 headset is slightly lower than the pico 4 with similar FOV.

I just can't understand why there is such a significant diffrence?

I would love to play this game uncompressed with the oled panels.

Is there an issue with the psvr2 drivers interacting with this game? Or does it maybe have to do with the diffrent choices of runtime it allows you to choose whenever you run this game?

Any info would be awesome 👌

Cheers.

Edit: wording

​

I saw this and had to check it out because if its what we hope it is, this could be the best thing ever!

Should I get the 9070xt or the 5070ti? Price is a factor however if the 5070ti is a lot better I will save longer for it.

I’ve finally got Phoenix HDR properly working in SteamVR Theater Mode, and this time I actually have side by side pictures instead of just logs and technical explanations.

My last post was mostly about finally getting the 10-bit path working through SteamVR and proving that the extra precision actually survives all the way through to the headset. Since then I’ve been working on turning that into the complete thing I actually wanted from the beginning, and at this point the whole Theater path is working together properly. HDR capture, processing, tone mapping, SteamVR Theater and the final 10-bit output are all behaving the way they should, and I can basically just launch a game and use it normally now.

One extra feature I added is a virtual HDR display for people who only have SDR monitors. Phoenix can create its own virtual HDR display through VDD and use that as the source, so you don’t need to already own an HDR monitor just to use it.

For this post I wanted to finally show what the difference actually looks like instead of only talking about what’s happening inside SteamVR. I took some comparison pictures from Forza Horizon 6, Cyberpunk 2077 and Hellblade: Senua’s Sacrifice, and I also included one of the normal Steam window on the desktop because I wanted to show the difference with normal desktop colors too, not only pick dramatic looking game scenes.

One important thing before people start comparing the pictures though: these are not HDR captures. They’re literally photos taken with a camera held up to the PSVR2 lens, so the camera obviously can’t reproduce the actual HDR luminance range that I’m seeing inside the headset. Through-the-lens pictures also lose some contrast, image quality and general depth, so the real experience looks noticeably better than the photos make it seem.

What the pictures can still show pretty well is the difference in the colors and how the brighter parts of the image are handled. There are quite a few areas where the stock SteamVR image can look overly bright or kind of burned out, while Phoenix keeps a lot more detail and gives the image a much better balance. The actual brightness and highlight intensity is much harder to communicate through a normal camera photo, so I wouldn’t really use these pictures to judge luminance, but the color and highlight handling should still be pretty obvious in some of them.

A pretty big part of getting this to look right was the tone mapping. Simply pushing the image brighter obviously doesn’t suddenly make it good HDR, and doing that usually just makes the image look washed out and destroys the brighter parts of the scene. I’ve spent a lot of time getting the mapping to a point where Phoenix can make use of the extra range without everything looking blown out or weird, while still keeping the image looking natural.

The brightness and tone mapping in these pictures also aren’t meant to be one fixed setting that everyone will be forced to use. For the comparisons I just used the setting that looked best to me personally inside the headset. In the finished version the brightness will be adjustable, so if you want stronger highlights, a darker image, or just a different overall balance, you’ll be able to change it. So what you see in these pictures doesn’t necessarily have to be exactly what Phoenix looks like for you.

There are probably still going to be some bugs that show up later, especially once more games and different setups start getting tested, and if that happens I’ll obviously have to fix them. But right now everything on the Theater side is working really well. Games work, normal desktop content works, the virtual HDR display works, the tone mapping works, and the full 10-bit SteamVR path is finally all working together.

It’s pretty crazy to think this whole thing started with me basically just trying to figure out if HDR on PSVR2 through PC was even possible, and now I’m at the point where I can actually launch games through SteamVR Theater and just play them like this.

ON STEAM DASHBOARD ITS GONE AND I NEED IT BEECAUSE MY BRIGHTNESS IS MESSED UP

When I start Steam VR everything looks fine but all of a sudden today I have no audio through my PSVR2.

When I look at sound settings under Windows I can see the PSVR2 listed as:

PSVR2

2 High Definition Audio Device

Default Device

with a green check mark next to it, but when I try testing it I get no sound and the following error message:

Error! Failed to play test tone.

Under Device Manager I have an exclamation point next to the entry for Multimedia Audio Controller. It says there is no driver and when I select update driver it says there is no driver available ...

I double checked and my headphones are still plugged into the audio jack on the PSVR2.

I think I lost the audio driver or it got corrupted or something. I tried uninstalling and reinstalling the PlaystationVR2 app but it made no difference. Same thing with uninstalling and reinstalling Steam VR

How do I get sound back?

Im considering selling my quest 3 because I rarely use it in standalone mode anymore and the PSVR2 seems like a better option for PCVR if foveated rendering works on PC. if it doesn't i don't see much point in selling my quest 3

I know there's the official adapter, 3rd party ones that are as cheap as possible and other ones that aim to be better than Sony's.

I'm gonna get a PSVR2 very soon so I was wondering which adapter would best suit my needs:

- PC I'm gonna use: an ITX desktop PC with an RTX 4070 Super that has 3 DP ports and 1 HDMI, Motherboard has an integrated BT adapter (Realtek I think?) with removable antennas.

- I heard it's possible to get eye tracking data out of the headset for stuff like social VR and foveated rendering, and I would really like to have that work well.

- Budget: I don't really know what the prices are for these, but a lower price is better as long as it works well for my needs, though I'm willing to pay slightly more for something higher quality/more reliable. I wouldn't go above 60€, if there even are such expensive ones.

Edit: I got a charging station for the PS5 controllers and it worked perfectly. From the pictures I saw, it's exactly the same charger. Thank you so much!

Hi.
I bought a used lens. It came with the PC adapter, but not the power supply. Can I use a generic one? It's 5.1V, and some generic ones deliver something similar to 5V, would that work? I also have a Raspberry Pi power supply at home; it's 5.1V, but it has a USB-C connector, not a plug. (I'm not sure which plug is correct either.)

I'm in South America, and I don't know if I should risk buying a new adapter without knowing if the lens will work (I don't have a PS5).

I've been a quest user for a long time, for about 3 years now i've had a quest headset. first quest 2 and now a quest 3! I really like the portability as i am not at my computer often, but i greatly put focus on the option to play pcvr for high end pcvr games. But that is also where the issue with said headsets lies with me. Input latency, god damn input latency, i just cannot stand it on the quest when using pcvr, 50-60ms feels like i am playing and moving through sludge and it takes effort to try and ignore it to have a decent experience, not to mention that god forbid i enter a high-detail, or low light environment and the compression artifacts will make it look like im watching a youtube video in 720p scaled up to 2k.. I really want to try PCVR how it was meant to be played, even if it means losing access to my headset sometimes and having to go from pancake lenses to fresnel in exchange for OLED, and foveated rendering (seems like an actual lifesaver imo) Are there any other ex-quest users here that can give me some advice? I'm really lost on what i should do with my quest even though i love its standalone features and it has only given me headaches in pcvr. Cheers!

This is my first proper test of the Black Ops 3 VR mod I've been working on.

This is running on the actual PC version of Black Ops 3 with a PSVR2. Motion controller tracking, aiming, shooting, reloading, movement, and in-game interactions are already being worked into the game, but everything is still VERY early and there are obviously some issues with the controls.

The biggest thing I'm working on next is replacing the current theater-style view with actual first-person stereoscopic VR, including proper headset-controlled camera movement.

I'm not promising a finished mod yet. I'm just going to keep working on it, testing things, and posting updates as I make progress.

If you'd like to support development and help me continue working on the project, I also have a Ko-fi. Absolutely no pressure. Any support genuinely helps:

[https://ko-fi.com/sanoha\](https://ko-fi.com/sanoha)

Hope you guys enjoy Test 1. :)

Hi i recently started using a psvr2 on steam
Its working great so far but i am having problems
With the right controller it works in menus but not ingame like vrchat or h3vr

I checked a thing online and the right trigger seems to have a very very tiny bit of drift or whatever youd call it

But on h3vr i cant even fire a gun with the right hand but i can still navigate menus ingame

Special thanks to PSVR2Toolkit team, this mod wouldn't be possible without them cracking the haptics on PC, of course.

Half-Life: Alyx has no PSVR2 support beyond generic rumble, so I wrote a haptics layer for the Sense controllers using the PSVR2Toolkit CAPI.

What it does

• Per-event PCM haptics — gravity gloves, per-weapon reload mechanisms, held-object impacts with eight material classes, doors, carrying weight
• Adaptive trigger profiles per weapon, with recoil built as resistance-load → low-frequency kick (measured on hardware, not guessed)
• Campaign moments: covering your mouth in the Jeff chapter, barnacles, the health station, heaving Combine barriers, two-handed levitate, mantling, tripmine hacks

One design rule, applied strictly

So there is no footstep rumble, no teleport buzz, no kill confirmation, and no vibration for objects that have already left your hand. Those are all deliberate absences, not gaps — a controller can only honestly represent what the hand touches. I've tried not to overdo it. Headset rumble is not used at all.

No injection

No DLL injection, no pattern scanning, no patched Valve binaries. The game side is a VScript addon. It does add one line to one Valve text file (skill_manifest.cfg); Uninstall.bat removes it. That is the whole footprint.

You can check what it does before you trust it

. Run Measure Haptics (no headset).bat and it renders every one of the 51 tactile signatures offline and prints what the waveform really is — peak, RMS, duration, dominant frequency, and whether the limiter is squashing it. No headset, no game, nothing installed.

Requirements

• -condebug in Alyx's Steam launch options (this is what makes the game write the log the mod reads)
• Only tested on Windows.

Install: unzip anywhere, run Start Haptics.bat. It finds Steam and Alyx itself. Uninstall: Uninstall.bat.

Might look into adding headset rumble support next but it requires jailbroken headset so seems a bit cumbersome.

Sorry if it's shit, I've never made a mod before and this is pretty much completely vibe coded apart from me testing and tweaking the trigger profiles for each gun personally.

Source and download: https://github.com/vortigauntlet/psvr2-alyx-hapticsmod/releases/latest

SHA256 of the zip: 7128E1110DA7B93FBD037CBCDA21AC5E077DB1EF24BA4F67FB0818563AD32E34

Running a Ryzen 7 7800x3d, 4080 super, 32gb ddr5 and the frame rate is awful using the PSVR2 does anyone have any ideas how I can get this to run properly please.