Difference between revisions of "Talk:Bluetooth Passthrough"

From Dolphin Emulator Wiki
Jump to: navigation, search
(Simplifying the result table: new section)
 
(28 intermediate revisions by 7 users not shown)
Line 1: Line 1:
== Adding this as guide on the main website / BT Adapters compatibility list? ==
+
== Adapter Test Results refactoring ==
 +
So, apart from small additions here and there, the adapter test results haven't received any meaningful update for some years. I have plans to at least partially address that, but before continuing, I really think we should completely drop the range column: it didn't turn out how we planned and I strongly think it has no meaningful significance for the reader (e.g. how far "Long" or "Very Long" actually is? Does it account for obstacles or other interferences?).
  
Well, firstly we should add this as guide on the main website ASAP as I noticed some threads about the passthrough mode popping in the forums, and most already are answered here. I'm not sure but I think [[User:MaJoR|MaJoR]] has the great powers needed to do that! And secondly, I think we should also have a list of compatible BT Adapters somewhere (and given the nature of the wiki, it's the perfect place). However, I think we should go slow with this and think of all details very carefully to avoid headaches in future since the first thing that comes to my mind is a "rating" for the BT Adapters, and, well, we already have enough issues with the current rating system from the game lists. Maybe using a more simple, 3 step, approach? Like 0 for unknown, 1 for not working at all, 2 for working with issues (e.g. works but doesn't remember paired controllers, has trouble connecting multiple wiimotes, works fine but randomly stops working, etc) and 3 for perfect (e.g. the Wii BT Module -- no issues). What do you guys think? Please point any flaws or things to take in consideration when designing this - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]]) 22:21, 6 October 2016 (CEST)
+
The audio column, on the other hand, still is relevant, but I think we should limit the allowed values to either ? (not tested), No (doesn't work or has major issues), Limited (works but has small issues on specific conditions -- e.g. multiple Wiimotes playing audio simultaneously) or Yes (works the same or better than the Wii Bluetooth module), just like the existing columns.
  
For the list of compatible adapters, I agree that the wiki is a good place for it. IMO, it may be better to have a compatibility table with specific test points (detected and boots, reliability, pairing, whether 4 Wiimotes can be handled, range). The issue with a 3 star system is that probably only the Wii BT module will get a perfect score, and all others will be either 0, 1 or 2. Also, while 2-star adapters all have at least one issue (of course), some of them are much larger problems, such as randomly stopping working or not being able to remember Wiimotes pairings, whereas not being able to or simply struggling a little bit to connect 4 Wiimotes is not as important. --[[User:Léo|Léo (leoetlino)]] ([[User talk:Léo|talk]]) 00:37, 7 October 2016 (CEST)
+
And finally, I would like to add a new column telling if the adapter in question is a standalone USB adapter or if it's the Bluetooth portion of a WiFi Card. Could be as simple as a "Type" column where the two allowed options are USB or PCIe. Thoughts? [[User:mbc07|mbc07]] ([[User talk:mbc07|talk]]) 00:09, 14 December 2019 (CET)
  
Regarding the "Perfect" compatibility, I really hope there's more adapters on that rating (if at the end we adopt that), as the link key backup/restore you implemented greatly helps with that. For example, the only issue the internal Atheros AR3012 I have is that it stops working after some HCI resets (e.g. ES_Launch events or booting another game) if they occur while there are wiimotes connected, otherwise it would be another "Perfect" adapter. TL;DR there's probably more adapters which works fine, maybe we even find a compatible model to recommend at the Recommended Accessories page, like we did at the time Toshiba BT Stack was the only option to connect -TR Wiimotes... - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]]) 02:43, 7 October 2016 (CEST)
+
:I think those all sound like good ideas. I don't see a problem with any of that. My only idea is to label the rest of the columns with hover-over descriptions like the VID/PID have so it's obvious what the possible answers should be, to keep everything tidy. (Or a little clickable question mark/number instead, so that the hover-over descriptions can be read on mobile.) - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 21:15, 15 December 2019 (CET)
  
After thinking about this a bit more, maybe a 3 star rating system would be enough. 0 for untested adapters, 1 for broken (either not detected, or with major issues), 2 for working with small issues (difficulty connecting 4 Wiimotes) and 3 for perfect adapters. (By the way, now that Dolphin can shut down games gracefully, Wiimote connections should be terminated properly before a HCI reset, so hopefully it should work better.) --[[User:Léo|Léo (leoetlino)]] ([[User talk:Léo|talk]]) 19:12, 7 October 2016 (CEST)
+
:: It's somewhat half-way done, ended having more columns than I expected. I was considering making another column for the chipset used and decouple that from the adapter name (currently listed under [] on the adapter name) but I think I'm crossing the line and going way too technical. Any thoughts before continuing? Any feedback on the added columns? [[User:mbc07|mbc07]] ([[User talk:mbc07|talk]]) 21:51, 18 December 2019 (CET)
  
== Compatibility list ==
+
:::Another column isn't a big deal to add in my opinion since removing the range column and adding in the type and BT columns added up to the same width, and adding another chipset column would still be just as wide afterwards anyways. But it looks good the way it is too with the chipset in brackets, so it's really whatever you want. I think it looks really good so far. - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 00:28, 19 December 2019 (CET)
 
 
What exactly is revision column? Dolphin revision (e.g. 5.0-1024) or hardware revision? I'm assuming it's hardware revision and, is it really needed? It doesn't seem to change behavior, and some vendors actually wrong uses the revision field to differentiate different manufacturers (for example, the Atheros AR5B22 has models from Samsung, Dell, Killer Networks and all of them share exactly the same hardware design and FCC certification, even the drivers can be swapped between them, the only difference being the hardware revision field)... - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]]) 20:41, 11 October 2016 (CEST)
 
 
 
: It's the hardware revision reported by the adapter. It's needed as an additional identifier (since the VID/PID can be the same pretty often). --[[User:Léo|Léo (leoetlino)]] ([[User talk:Léo|talk]]) 21:02, 11 October 2016 (CEST)
 
 
 
Also, what exactly is a perfect range? 15m? 20m? Maybe we should document that after the table, same for HCI Reset which I used in one of the entries - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]]) 20:48, 11 October 2016 (CEST)
 
 
 
: This was a test result by JMC47; it probably means "range is nearly/about as good as with a real Wii". --[[User:Léo|Léo (leoetlino)]] ([[User talk:Léo|talk]]) 21:02, 11 October 2016 (CEST)
 
 
 
== Simplifying the result table ==
 
 
 
I've noticed that the audio quality and range can be hard to judge, and that there have been loads of different values in these two columns. What do you think of simplifying this, by having "Good" for the Wii Bluetooth module (which is the reference) ''and'' anything that's good enough to be indistinguishable from console? And same for range.
 
 
 
Also, while the table is very detailed, I fear that it may become harder to read and compare adapters as more results get added. Could we add some sort of rating system as the last column, as some sort of summary? As discussed previously, it'd be star based. 0 for untested adapters; 1 for non-working adapters or broken pairing; 2 for anything that's near perfect but has some flaws; and 3 for everything that's ''as good as'' or ''better than'' the reference adapter.
 

Latest revision as of 01:28, 19 December 2019

Adapter Test Results refactoring

So, apart from small additions here and there, the adapter test results haven't received any meaningful update for some years. I have plans to at least partially address that, but before continuing, I really think we should completely drop the range column: it didn't turn out how we planned and I strongly think it has no meaningful significance for the reader (e.g. how far "Long" or "Very Long" actually is? Does it account for obstacles or other interferences?).

The audio column, on the other hand, still is relevant, but I think we should limit the allowed values to either ? (not tested), No (doesn't work or has major issues), Limited (works but has small issues on specific conditions -- e.g. multiple Wiimotes playing audio simultaneously) or Yes (works the same or better than the Wii Bluetooth module), just like the existing columns.

And finally, I would like to add a new column telling if the adapter in question is a standalone USB adapter or if it's the Bluetooth portion of a WiFi Card. Could be as simple as a "Type" column where the two allowed options are USB or PCIe. Thoughts? mbc07 (talk) 00:09, 14 December 2019 (CET)

I think those all sound like good ideas. I don't see a problem with any of that. My only idea is to label the rest of the columns with hover-over descriptions like the VID/PID have so it's obvious what the possible answers should be, to keep everything tidy. (Or a little clickable question mark/number instead, so that the hover-over descriptions can be read on mobile.) - Xerxes (talk) 21:15, 15 December 2019 (CET)
It's somewhat half-way done, ended having more columns than I expected. I was considering making another column for the chipset used and decouple that from the adapter name (currently listed under [] on the adapter name) but I think I'm crossing the line and going way too technical. Any thoughts before continuing? Any feedback on the added columns? mbc07 (talk) 21:51, 18 December 2019 (CET)
Another column isn't a big deal to add in my opinion since removing the range column and adding in the type and BT columns added up to the same width, and adding another chipset column would still be just as wide afterwards anyways. But it looks good the way it is too with the chipset in brackets, so it's really whatever you want. I think it looks really good so far. - Xerxes (talk) 00:28, 19 December 2019 (CET)