Have you had a chance to look into the slowness upon waking from sleep? It still exists in the 1.1 beta you posted earlier. Loading states doesn't seem to fix it, but closing and re-opening the ROM does. On 3.0.0 via Pegaswitch.
Kirby Super Star seems to work fine now. Also Final Fantasy III (aka FFVI) used to lag like crazy during its intro but it seems to run fine now as well. Still have the sleep mode causes extreme slow down, but otherwise it is way better! Great work cpasjuste.
Others have said exFAT can be problematic in terms of corruption. I would suggest trying FAT32 and see if that works better. I think it might be libnx related bugs.
Sorry to be spammy but just wanted to follow-up so that you/others know. I pulled it off the dock and it switched seamlessly to the switch itself (with sound and such fine), and put it back on the dock and it switched seamlessly to docked mode. Pretty cool.
Just confirmed this myself. It works fine in docked mode (docked it then started the pSNES app and loaded a ROM - all good). I also confirmed it works fine with my Pro controller!
Runs great on 3.0.0 via Pegaswitch!
I loaded two different ROMs and had no problem saving state after opening the second one (via +/- -> States -> 0).
Would be nice to bind things like save/load state or rewind/fastforward to keys via the Joypad menu.
Noticed a bug: if I put the Switch to...
Hah okay, thanks for the reply, that's beyond my understanding. Here's to hoping Hekate sleep gets fixed for 3.0.0, but with nwert shutting down the public repo.... Who knows :wacko:
Thanks for all your work on this by the way, amazing job!
Where exactly is nx-hbloader contained? Is it part of the nx-hbmenu? Or is it something that gets called as part of the Pegaswitch exploit chain? Would it make sense to try to pull and run my own latest up to date DNS and webserver for the exploit to try? Or is it not related to that? Right now...
That's what I took it as - no worries! Just wanted to make sure accurate information was provided to help narrow down where the issue might be. Honestly, I am probably just going to be using Hekate going forward now that the sleep bug is fixed, and will be using Atmosphere (cold boot?!) when it...
Okay, I noticed someone said this earlier in the thread, but I wanted to test/confirm this.
For what it is worth, I am on 3.0.0, and if I use Hekate-ipl to boot into a CFW allowing you to use HBL from the Album icon, I can run the threaded versions fine. There is no crash on ROM load.
HOWEVER...
Yeah, still getting a 2162-0002 immediately after loading a ROM. Tried with and without configs. Tried a few different threaded builds etc. Just doesn't seem to work on 3.0.0 :'(.
I did try the "stable" download link from OP and it works fine, no issues there. So who knows.
A little bit behind in following this, but, should these threaded builds work on a 3.0.0 switch? I keep getting a 2162-0002 error immediately after trying to load a ROM (been trying snes9x2010 specifically).
It's up on their site @ $35 -- https://team-xecuter.com/
$25 just for their OS license... I guess w/o the jig and dongle?
auto
See -- https://team-xecuter.com/
I've been playing fallout4 all day, I went into a elevator and it kept going, never stopped, waited 5 minutes, must of been a bug. How bout you, whatcha do today?