Sure, it will be very complicated. Thats why I asked if I could do any log or anything to help. I have the problem here, I could try or test anything. Also reported very specific situations when this happens (vsync and fullscreen and just only happens on one game)
I remember the first days of bt passthrough. It was a pain to deal with it. Full of problems and only devs and lot of PR testing made it way better.
Im not getting any ideas. Not sure why.
Btw, not sure if retroarch dolphin core supports bt passthrough. I could give it a test too.
It's most certainly some kind of strange timing issue on your hardware. With Bluetooth Passthrough, Dolphin has almost no control Wii Remotes, it's letting the Bluetooth and game do all the work.
The thing that would cause a disconnection is if emulation somehow got delayed a large amount or, during boot, another program was pinging your bluetooth device in certain conditions. There really isn't anything (known) in Dolphin that would cause this behavior.
Hi. But its only in this game.
And its only on fullscreen. When windowed doesnt miss a single speaker audio, not a single disconnect, its perfect (again, only in this game. Others are always perfect)
Thats gets thing more complicated.
And im pretty sure that older dolphin builds worked fine. But I tested the older ones and problem is there. What hardware changed since it worked fine? Gpu, windows 10 build, gpu drivers and nothing more. I have a normal build, haswell i7, enough power to think about missing frames or something like that. It should be something about amd drivers, dolphin, or any other software getting in the way.
So not sure what to think.
Im think bt passthrough can be changed somehow. I remember first days of bt passthrough. Leo did a lot of changes. And even the wii bt module didnt remember pairing for example. So a lot of stuff was fixed/changed.
Maybe if I do a clean install will work fine. But cant test that atm.
Tried retroarch dolphin but cannont made it boot. Will have to test further.
Sorry to repeat things many times. But english is not my language and sometimes im not sure if im understandable at all.
Got retroarch to load dolphin games. But cant see any passthrough option. It is supported on this core?
Also noticed on normal dolphin that if you mess too much with nsmb trying to connect (not sync) wiimotes, wiimote Will start blinking just a second instead of 4 or 5 seconds, that means wii bt module is activelly refusing connection. And once that happens, you Will have to resync wiimotes with the Dolphin sync button or wont work anymore on Dolphin on any game.
Only nsmb triggers this. It makes Dolphin/wii bt module forget pairing if you insist too much.
(04-02-2019, 05:44 AM)mbc07 Wrote: [ -> ]Let me quote myself from another BT Passthrough thread:
That's still the case nowadays. An timing issue surely exists but it probably won't be fixed until it can be consistently reproduced...
@JMC47 @mbc07
Hi guys. Some news. I saw latest build added back dx12.
And guess what?
The problem is not present using dx12 backend.
Hope this help to fix or find the problem.
If I change to vulkan or dx11, problem is there. Probably latest windows 10 build changed something about fullscreen and vsync. Or maybe its on dolphin side.
Now that we have a working and not working options, if you need some test, just ask.
Tried more than 10 tines with dx12, problem is not there at all. Instant connect on nsmb, no disconnects, it just works.
Windows 10 gets exclusive fullscreen faster on D3D12 in my experience. That's probably the reason.
Hi. Could be. But frequent disconnects on nsmb could be because of this too?
Maybe there is some desync in the way other backends gets fullscreen, but it doesnt affect other games. That is weird. I tried all dolphin fullscreen settings, borderless, etc with no luck on dx11 and vulkan.
(04-03-2019, 03:09 PM)trihy Wrote: [ -> ]Hi. Could be. But frequent disconnects on nsmb could be because of this too?
Maybe there is some desync in the way other backends gets fullscreen, but it doesnt affect other games. That is weird. I tried all dolphin fullscreen settings, borderless, etc with no luck on dx11 and vulkan.
trihy:
I was doing some testing on NSMBW with D3D11 on the 5.0-10617 build and I did not see any of our old issues. I think problem this may finally be resolved, along with the recent crashes when using bluetooth passthrough and relaunching a game.
Can you please check on your end?
(07-13-2019, 10:56 AM)themanuel Wrote: [ -> ]trihy:
I was doing some testing on NSMBW with D3D11 on the 5.0-10617 build and I did not see any of our old issues. I think problem this may finally be resolved, along with the recent crashes when using bluetooth passthrough and relaunching a game.
Can you please check on your end?
Hi. Sure. I didnt test more of this because since dx12 was re added to dolphin, works perfect.
But here is my test with todays build:
Dx11 works fine, wiimote connect instantly.
Dx12 works fine, wiimote connect instantly (never had this problem on dx12 since was re added to dolphin)
Vulkan, problem, wiimote takes 20 seconds or more to connect after a few tries. Same problem described on first post. Only happens with nsmb.
OpenGL, didnt test, cause opengl has many other problems on my amd card (rx580)
I think dx12 is the backend to use. Great performance and no wiimote connecting bugs.
So, what changed? Well, seems now dx11 doesnt have this problem.
You are right. OpenGL still has the issue for me too. Luckily I normally use D3D11.