I tried again by copying over the sys-clk zip into the SD root.
It seems to be working again, but it seems to be somewhat buggy. It's randomly stopping. Not sure what's going on, but oh well, at least it works again.
sys-clk is the one stopping.
MissionControl I installed, but I am not using any bluetooth controller (the WiiU 3rd party one I had is not recognized)
Might need to talk to the sys-clk devs on that one. I can't think of any reason why MissionControl would interfere with it. Have you tried removing it to see if sys-clk starts behaving again? Maybe you have too many sysmodules running? (I don't run any others so I don't know if this manifests as a crash or not)
As for your controller, head on over to the github page and create an issue with the controller details and I'll work with you to support it.
For sysmodules, I believe I have Edizon, Emuiibo, sys-clk and the monitor one, that's all the ones I have.
What do I need to remove to effectively remove MissionControl from Atmosphere, precisely?
As for the controller, sure thing!
Let me know what I need to do so I can prepare the controller info for inclusion, before opening the issue.
Last edited by ShadowOne333,
D
Deleted User
Guest
Ill make an issue later today once I am home
Another thing I noticed is that my system now crashes(sometimes it just freezes/hangs without a atmo crash screen) when trying to connect any DS4 controller after connecting/syncing a second one.
Again I will submit an issue for you once I'm home for your convenience as requested, still wanted to mention it just in case
Did you install the version posted in that issue I linked you to? The system crash sounds like the DS4 battery bug that is fixed in that build.Ill make an issue later today once I am home
Another thing I noticed is that my system now crashes(sometimes it just freezes/hangs without a atmo crash screen) when trying to connect any DS4 controller after connecting/syncing a second one.
Again I will submit an issue for you once I'm home for your convenience as requested, still wanted to mention it just in case
I also wasn't able to reproduce the issue you mentioned in-game. I suggest you try with the battery fix build before opening any new issues.
Did you manage to fix the battery level and charge indicator? I do hope you fixed it because my charge indicator seems random and I have not been tinkering with my code since I fixed my DS4.
Yeah as far as I know it's fixed. I'm not convinced the indicator is exactly right, I think the switch format might be nonlinear. But that's a problem for all controllers, not just DS4.
I will wait patiently for the next release then. The current release works perfectly for my DS4 aside of no motion and rumble. I hope you can figure out those soon!
How can I get the required data/info to submit the controller for addition?
I downloaded the nro from the releases page and ran it while the WiiU controller tried to sync up, but the only listed devices are the joycons and the Pro Controller.
My controller is a PowerA WiiU Pro Mini Elite Controller.
I downloaded the nro from the releases page and ran it while the WiiU controller tried to sync up, but the only listed devices are the joycons and the Pro Controller.
My controller is a PowerA WiiU Pro Mini Elite Controller.
Last edited by ShadowOne333,
Keep in mind that any controllers that don't have a name recognised by the switch get renamed to Pro Controller so will appear in the database that way.
If it still doesn't appear to be getting stored in the database you can use this build to make a log of the pairing attempt.
Sure! Open a github issue with info about the controller and the output of btdb.nro after attempting to pair.
Where is the log stored?
I tried running the Bluetooth NRO again, and I'm still getting the same 3 paired controllers.
My two joycons and a Pro Controller.
Output:
Last edited by ShadowOne333,
The log will be placed in your SD root under btdrv-mitm.log. Note that the log is wiped every time you reboot.
Doesn't look like it's managed to pair with the console though. I'll need to see a log. Open a github issue to continue this discussion though. It helps me follow things up more easily and other users experiencing similar issues don't have to search for comments buried in this thread.
Last edited by ndeadly,
Just a heads up before people start complaining of issues, the new Atmosphere (0.14.2) just released will likely not work with MissionControl until I make a new release. Incidently however, this release was issued in part to fix a problem with mitm sysmodules and allow me to ditch the modified boot2 I currently distribute. Thanks SciresM!
I'll be releasing an update soon to address this, add support for additional controllers and fix a few bugs people have been experiencing.
I'll be releasing an update soon to address this, add support for additional controllers and fix a few bugs people have been experiencing.
Similar threads
-
@ HiradeGirl:
@K3Nv2 I did that using Citra for 3DS games. Bottom screen was my smartphone. Until I got the touch screen. -
-
-
-
@
Psionic Roshambo:
Ken I have that sort of set up on Drastic on Pi for games that don't require touch -
-
-
Any TV with your PC connected with Citra and any smartphone to use as a screen using a free play store app.+1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
