Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
It only disconnects making you have to pair it again when YOU turn it off. So don't turn it off. Just set it down and let it turn it self off. Then you won't have to re-pair and reconfigure it all of the time.
And there are several modes that work. So just use those.
No, you are completely wrong, but may be I was not clear enough : I have to pair it again even if I don't turn it off MYSELF, but everytime I turn it on, whatever the reason the controller has been turned off.
Please, don't tell me what mode to use or not : it's annoying. If you're familiar with controllers, you know the differences between Dinput and Xinput, so you know why I want Xinput to work with a controller wich is SUPPOSED to use it. If you're not, then...why do you even "answer" ?
Again, feel free not to answer if you don't have any real knowledge or technical help to bring, we will both save time.
thanks
THIS IS NOT WHAT JOSIAH BLUETOOTH INTENDED!
Only once. I accidentally triggered the button combo to change between dinput and xinput midgame and it crashed the controller couldn't remove or reconnect. I purged the driver with driver store explorer and rebooted and it started working again. Though just doing a full reboot instead of ACPI soft restart and letting the driver reload on it's own probably would have worked without going the extra mile to wipe and restore it.
But still, 8bitdo, Logitech F710 and SteelSeries Stratus Duo are probably the best PC controllers since the original Gravis Gamepad.
Xbox abominations have no place with self-respecting PC gamers.
https://www.youtube.com/watch?v=K8gvt-ubZiQ
Support are at the other end of the ticket system, This is a USERS forum.
If you're not getting responses from other users, we don't have answers for you.
As far as getting the best chance of answers, I'd personally be emailing 8bitdo as they're going to be more au fait with their hardware. Failing that, if they have forums, try there.
I have no experience with Switch controller or its emulation, but I know there have been a number of people with various issues using this controller or third party versions. So bear that in mind too.
So you know how ticketing works then?
The point is you shouting HERE for support isn't going to work because support ARE NOT HERE. This is a USERS'S forum.
So:
(1) Don't shout expecting a response. We're the same as you.
(2) Don't expect an snwer if people don't have one.
Be sure I don't. And I did not shout, I pointed out. So don't tell me "don't", I don't like your tone and I think that I don't like you. You may go. And close the door behind you. Thanks.
Switch Pro mode works perfectly in wireless mode, but it craps out completely when going wired just as described.
I hope this is something that can be fixed in Steam itself, and I suspect it is.
What I do know is that when 1 LED is blinking, the controller connects in D-input mode, and with 2 LEDs flashing it connects in xinput mode. My roommate's controller had 2 LEDs flashing and worked fine, my controller had only 1 LED flashing and had issues. Idk anything about the differences between xinput and dinput, but any insight is helpful. Does anyone think this could be what caused my issue of the Y button not working when connected in dinput?