(01-15-2019, 03:47 PM)JMC47 Wrote: [ -> ]Sounds like your NAND has other problems than just this issue.
I don't want derail from the original topic but the game has a problem, whether it is launched from Wii Menu or Dolphin's GUI.
Hi, yes, lets stay on topic.
My nand is a backup from my wii nand. Always worked fine. Did a nand check and didnt reported any errors, also did nand update and says everything is up to date.
You can also launch wii menú without having your own nand. Just the menú ios.
Any dev with Windows to check the nsmb not connecting till that screen issue?
I brought it up because a messed up NAND can cause things like Wii Remotes to malfunction, it wasn't meant as a derailment.
(01-16-2019, 02:10 AM)JMC47 Wrote: [ -> ]I brought it up because a messed up NAND can cause things like Wii Remotes to malfunction, it wasn't meant as a derailment.
Hi, I found something.
If you disable vsync on Dolphin settings, NSMB Will connect before that screen, like any other game.
Enable vsync, wont connect until that screen.
Its easy to replicate.
Turn on single core and see if it still happens. That way vsync makes no difference at all internally to the game.
(01-16-2019, 04:15 AM)JMC47 Wrote: [ -> ]Turn on single core and see if it still happens. That way vsync makes no difference at all internally to the game.
Hi. Disabled dual core on global settings, same problem.
Disabled dual core on game properties, same problem.
Even I would say disabling dual core makes the connect even a Little later than before. Just when the screen I posted dissappear it Will connect, not during. With dual core enabled Will connect on that screen.
Only fix so far is disabling vsync.
Disabling vsync on single core affects it literally none, or else we'd have determinism issues.
Actually the game could running above 60 FPS while loading and since this is a Wii Bluetooth Module, it needs the game full speed. Disabling vsync would make sense then.
(01-16-2019, 05:46 AM)JMC47 Wrote: [ -> ]Disabling vsync on single core affects it literally none, or else we'd have determinism issues.
Actually the game could running above 60 FPS while loading and since this is a Wii Bluetooth Module, it needs the game full speed. Disabling vsync would make sense then.
I never had this problema before. Always used nsmb to sync my wiimotes.
Not sure which build introduced this problem. Every other game connect at the wii warning screen. The warning screen last like 30 sec.
Also made a portable Dolphin latest build, everything default, installed system menú ios (not my nand) started any game, hit menú on controller, system menú, went to disc channel, cannot read disc. So there is a problem there too. Im using spanish language on wii settings. Not much more, left most on stock.
(01-16-2019, 03:56 AM)trihy Wrote: [ -> ]Hi, I found something.
If you disable vsync on Dolphin settings, NSMB Will connect before that screen, like any other game.
Enable vsync, wont connect until that screen.
Its easy to replicate.
Nice find.
I can confirm that this resolves both, the NSMBW and Zelda Skyward Sword issue where Wiimotes won't connect if any button is pressed too soon after the game loads
This also resolves the issue where eventually the wiimote disconnects for 5-6s after playing NSMBW for a while.
Finally, I narrowed down the problem to the D3D and OpenGL back-ends. This does not happen for me with Vulkan.
Trihy: can you verify if the problem goes away when you use the Vulkan graphics back-end?
Hi, nice finds too.
Tested every graphic backend
-Vulkan NSMB wont connect until that screen.
-Directx 11 NSMB wont connect until that screen.
-OpenGL NSMB connects fine like other games, at the warning screen.
So, on my end, only OpenGL works fine.
Im using amd gpu here.
All graphics backend with vsync on.
BTW the problem is not just at the beggining, if you wait too long to press a button on the wiimote and try to connect a few minutes after the game started, also wont connect.