Hey, Recently bought 2 new PS5 controllers to play on PC(BazziteOS), that’s connected to a TV. I have the controllers connected to my network card (TP-Link Archer TX50E), that supports Bluetooth 5.0. However, while the PC is only 3 meters away from the TV and the couch, the controllers keep falling out due to bad connectivity. The PC is hardwired to Ethernet, and so are all other devices around, so struggling to think there can be wireless connections interrupting it.

Would really like to be able to play games on the TV. I also have an Nvidia Pro Shield connected to the TV(when the PC is not connected), but not able to think of a method I can have the controllers connected to the Shield instead, while still playing via the PC. Do I need to buy another, stronger Bluetooth adapter?

Anyone got any tips for the situation? Please share your setups/experiences regarding this, if you have.

Have a nice day 🌻

  • Telorand@reddthat.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    7 months ago

    Which version of Bazzite are you on? Bluetooth has been having connectivity problems in the latest versions (a regression from the Bluez driver upstream, I believe).

    I rebased my Steam Deck to 39-20240328, and everything seems to be working as expected. 39-20240414 might also be okay, but I haven’t tested it myself.

    ETA: I haven’t been able to connect my primary BT headphones to my Deck, but my Steam Controller and a different pair of BT headphones are fine. Might be a similar case with you; I don’t know why one works but the other doesn’t.

  • breakcore@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    0
    ·
    7 months ago

    I have had a bunch of problems with PS5 controllers recently.

    I am noy sure you are experiencing drop outs due to physical limitations, rather due to (as I recall) recent restructuring of the kernel code handling connections to the controller and regressions introduced herein.

    One way to rule out physical limitations, would be to stand next to the PC and see how it fares. What is your experience like then?

    • Sunny' 🌻@slrpnk.netOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      7 months ago

      Works completely fine when I sit next to the computer and play on my monitor instead of the TV. It only occurs when I sit away from the PC, by 3 meters, roughly. I also have a Bluetooth headset I use from time to time, and that works flawlessly connected to the PC, even if I go to other rooms in the house. So pretty sure the network card itself works fine…

  • Lomkey@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    7 months ago

    I had this problem with fedora base system is due to the bluetooth software with controllers like PS5 they use, if I remember I never got it to work right, I am sure there is a fix somewhere but I have not found.

  • 🇰 🌀 🇱 🇦 🇳 🇦 🇰 ℹ️@yiffit.net
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    7 months ago

    Is your Bluetooth adapter in a USB 3.0 port? That can interfere with the signal. Move it to a non 3.0 port, preferably on a front panel port to limit interference from the motherboard. An extension cable can even be helpful (this solved much of my BT connection issues personally).

  • cacheson@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    Are there any physical obstructions between the controller and the antenna? That’d reduce the effective range.

  • zelmon64@compuverse.uk
    link
    fedilink
    English
    arrow-up
    0
    ·
    7 months ago

    The Shield was made for game streaming which would precisely enable you to connect the controllers to it and run the games on your PC. Nvidia has since stopped supporting that software but luckily there are alternatives. The Moonlight client and Sunshine host are direct implementations of what Nvidia used to provide or there’s Steam Link if you’re using Steam.

    I know the DS4 controllers had similar connectivity issues on Windows which could be solved by changing power management settings. I’m not sure if this issue still applies to using DualSense on Linux.