Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Use only one bluetooth at a time.
https://steamcommunity.com/app/2580190/discussions/0/4509877893257207304/
(Start here if you have problems (controllers, app, other tips).)
"Additional steps if nothing works:"
I read with understanding what you wrote.
I encourage you to look at it again, because you are not the first person to speak, that he knows about computers and it's not bluetooth.
Then once again, it started having problems. That time I figured out that rotating my PC around 180 degrees so the WiFi antenna on the back of the motherboard were closer to the controllers made it work better, but it still wasn't perfect.
Then after a week or so of ok-ish performance, I started having issues with controllers not being detected by Windows at all. I eventually managed to remove them from Windows and re-sync them, although that took numerous attempts of turning Bluetooth off and on in Windows, restarting the controllers, and restarting the PC before I eventually tried connecting them back to my PS5 then back to the PC which finally worked.
A few days after that they were connected but one of my hands in Phasmophobia just completely disappeared and ceased to exist entirely. At that point I just gave up and haven't touched it since. I haven't even bothered looking into replacement WiFi/Bluetooth adaptors because I'm still seeing mixed results even with some of the most popular options. There still doesn't seem to be any obvious rhyme or reason to why this is happening or how to fix it. Some people are lucky enough to have flawless experiences whilst others are having so end of issues when it would seem their setups are near identical.
It's so frustrating that there still isn't just a clear "This is what's causing the issue, this is why it's happening, here's how to fix it."
Also frustrating that PCVR headsets have stagnated so much since the Valve Index released. Unless you want to pay ridiculous money for a MicroOLED headset from a smaller company like BigScreen that has their own problems, you're stuck with devices like said Index that's super outdated and there's no word on if or when it'll get an update.
I know the Quest 3 is great for its price, but I don't want USB/WiFi compression to play PCVR and they're not OLED.
Reduce 2,4 interference.
If you want, you can find help in the topic with help.
The problem is that ps vr2 was created as a vr set for the console, and it uses a good quality radio in the console.
All pc vr kits have radio in glasses.
People don't have good quality radio in their PCs, because most of them don't need it.
This is a very cheap vr oled headset, if you like it, you can easily solve the problems with interference in the 2.4 band.
- Unpair the PSVR2 controllers from Windows Bluetooth settings and disable the onboard bluetooth in Device Manager.
- Connect the ASUS BT-500 adapter to a USB 2.0 port at the back of the machine using a short extension cable (that is ideally 1 meter or 3 feet long).
- View Device Manager and expand the Bluetooth section, and right click the ASUS BT500 dongle and click Uninstall. Then tick the delete driver checkbox and click the Uninstall button to confirm uninstallation.
- At this point, dont scan for hardware changes. Instead download the newest driver available from the ASUS website, which is currently 1.0.0.9.
https://www.asus.com/uk/networking-iot-servers/adapters/all-series/usb-bt500/helpdesk_download?model2Name=USB-BT500
- Unzip the driver file and right click the installer and click run as administrator and complete the installation. Then restart the computer to apply changes.
- Make sure both controller batteries are full and then add them to Windows again using the Add a device screen in Windows Bluetooth settings.
- Add each device individually. When pairing, hold the option key before holding the PlayStation button and then keep them pressed together and those will appear quicker in the Add a device screen.
- If the problems continue, try resetting the controller using the pin hole at the back of the handle, using a suitable sized pin and hold it in for 8 seconds allowing it a moment to reset. You will need to unpair the previously added controllers and add them again to Windows.
If it is still not working...
- Unpair any wireless peripherals like headphones and keyboard/mouse inputs and use a wired version instead, then try again.
- If they are added by Bluetooth, unpair them from Windows, and only keep the VR controllers connected since the Bluetooth adapters cannot connect to many devices when used with VR controllers.
That said, i had a total bug at first where my GPU would not connect signal to the HMD (err in SteamVR) which annoyed me until i ... kid you not, restarted whole PC and it magically worked again.
That said I had a lot of devices running this time (Pluse 3D headphones + full bhaptics rig) ... i assume is the issue and will test tn, but it was a pretty dramatic change that seemed more HMD tracking related than BT (when I put one controller behind the other it would lose tracking more consistently than i recall on actual PSVR, on top of sporadic the drift of the one specific controller [that restarting didn't improve]
Anyways... not sure if this is still an issue for some, any advice or updates would be appreciated!
I rather not go the "donger+extender route" if i dont have to, already a rats nest, but if thats the only option will consider trying it
EDIT/UPDATE:
I should have done these one at a time to test but...
- rolled back Intel BT driver
- ironically disabled said driver anyways, and mountes a TP-Link 500-plus (5.3 with the antenna) on a usb 2.0 extention to a usb 2.0 port -- placed on top of TV center of the room
- installed the linked BT beta drivers from TP link posted on the Playstation website with recommended adapters
- wiped the front lenses with a microfiber cloth in case fingerprints
Seems like it works now 🤣 ...Not sure which, if any of the above, helped, but it works again [be it a bit worse tracking/approximating when i have one controller directly behind the other, like holding a rifle, but still usable, and expected with thw inside-out tracking anyways, just not sure I've "noticed" it before like this]
Might test individually later if anyone curious, but just want to play again at this point lol)
... could've been a reboot, could be the driver, could be unpairing everything and re-pairing (needed to for the new BT device + drivers), dunno but it worked 🥲
La vrais solution que j'ai trouver et je n'est vraiment zéro décrochage dans tout les jeux VR a été d'acheter deux batteries externes (une pour chaque Sense)
le faite de brancher la batterie sur la Sense qui reste bloqué puis d'éteindre la Sense via le bouton PS
(maintenir le bouton PS environ 10 secondes , la lumière blanche s'éteindra puis une fois se processus fait, rallumer la Sense en question via le bouton PS )
tu verra comme par magie le contrôleur n'aura plus de blocage durant ton jeux !
Ce processus sera a faire a chaque démarrage d'un jeux VR !!
J'espère t'avoir aider ,même si tu doit faire une autre petite dépense d'environ 20 a 30$ pour une batterie externe .