- Thread starter Synecdoche
- Start date
- Views 29,655
- Replies 127
- Likes 22
As Bullseye said above, it's Atmosphere. I noticed this before releasing 4.5 and tried a fresh Atmo install and got the same load times. At the moment I'm not sure why this happens but it's definitely not Void.
they would've released them by now thats why i think there wont be any and from what i can see devs want ppl to use fusee-primary only
Absolutely, I'll update this later when I'm not working (and remove more stuff from Lite) but here's the list:
From the Payload Folder in the ZIP:
- Hekate By CTCaer - Custom Firmware Launcher and emuNAND Creator.
- Lockpick RCM By shchmue - Generates Encryption Keys
- Tegra Explorer By suchmememanyskill - Payload Based File Explorer
From the PC Tools Folder in the ZIP:
- Tegra RCM GUI By eliboa - PC RCM Payload Injector
- Switch Backup Manager By gibaBR - Switch Game Backup Manager
- NS-USBloader By developersu - Switch Game Installer for PC
- Appstore Work Bench - Appstore on your PC.
Well, they changed the way atmosphere works, so it might take a bit more time to test them. But I have no clue how they are compiled.
That Devs want people to use fusee primary does not mean that someone would like to use hekate and they would release them.
But as always, wait and see
Well, I am a user that fully turns off my console on a weekly basis, and if I am fiddling around or trying certain configurations long boot times can be annoying. So I understand what you say there.
For the time being it is more than fine to continue with atmosphere 0.12, but eventually you would like to be using the latest CFW.
I will personally wait for an update to hekate sigpatches for AMS 0.13 and will revert back to AMS 0.12 (as everything was working perfectly before).
When paper Mario origami king comes out I will see what to do
Just out of interest, two questions:
Why do you turn it off fully once a week? And in your opinion, what is the best configuration?
Well, I turn it off fully because due to work/personal life I will not be able to play with the console during some consecutive days and I do not want the battery to die on me with the console in sleep mode. Want to avoid battery desync if possible.
As for configuration what do you mean? CFW wise or NAND wise?
A smaller release to make everything a bit easier for everyone:
4.6
If you do have issues and you're able to fix them, let me know as well so I know how it was resolved.
4.6
- Updated Sigpatches to newest release for Atmosphere 13.0
- Removed the following to make Vöid Lite even Lighter for a bog-standard install. Removing everything I don't feel is needed to get you up and running with a smaller installation.
- Amiigo
- FTPD
- Switch Theme Installer
- Switch Cheat Updater
- N-Xplorer
- Amiigo Overlay
- Sys-Tune Overlay
- Updated VG Edit to the latest release.
If you do have issues and you're able to fix them, let me know as well so I know how it was resolved.
Last edited by Synecdoche,
Well, I'm personally keeping my sysNand on 4.1 FW and keeping my fuses intact as well as nogc patch. I went through all the Nintendo 3DS hacking scene and many people claimed that we would never get a cold boot and we initially got it for lower FW and some time after for all the FW. As I kept my sysnand FW low I was able to use it early on. Would be nice if we get there with the switch as well.
And for my EmuNAND I currently have 10.0.3 FW and the best configuration when I only want to play games is payload Hekate with autoboot to EmuNAND through fss0= due to faster boot-up times.
I am using the NS-atmosphere to push a payload, even if recently I got an RCM loader one that allows me to push different payloads and changing payloads is much more convenient with the latter.
When I started timing the boot-up times I also found that NS atmosphere is consistently faster (by 1 second) to push the payload than RCM loader one. Just curious thing to point out, not that I care about that second.
For anything else other than gaming, either I push the fusee-primary payload with RCM loader one or I just chain load it through hekate if I already have my console turned on
Last edited by Bullseye,
@Synecdoche
The PKG2 sigpatches have been updated 2 hours ago.
I have tested them with fss0=fusee-secondary.bin. Using this, the boottime is much faster.
Also, the backups are still running, everything works fine, now.
It would be cool, if you could pack these patches to void-nx and set the payload to fss0=fusee-secondary.bin.
Or is it unintentional to have fusee-secondary as payload for void-nx? If so, what is the benefit of using fusee-primary?
Another thing: I use hekate as atmosphere/reboot_payload.bin. This makes it much easier to switch to a different nand from vöid-nx (most people have multiple nands: one for online and one for offline backups).
Do you think, it would make sense to set hekate as default reboot payload in void-nx?
The PKG2 sigpatches have been updated 2 hours ago.
I have tested them with fss0=fusee-secondary.bin. Using this, the boottime is much faster.
Also, the backups are still running, everything works fine, now.It would be cool, if you could pack these patches to void-nx and set the payload to fss0=fusee-secondary.bin.
Or is it unintentional to have fusee-secondary as payload for void-nx? If so, what is the benefit of using fusee-primary?
Another thing: I use hekate as atmosphere/reboot_payload.bin. This makes it much easier to switch to a different nand from vöid-nx (most people have multiple nands: one for online and one for offline backups).
Do you think, it would make sense to set hekate as default reboot payload in void-nx?
Last edited by MSco,
@Synecdoche
The PKG2 sigpatches have been updated 2 hours ago.
I have tested them with fss0=fusee-secondary.bin. Using this, the boottime is much faster.
It would be cool, if you could pack these patches to void-nx and set the payload to fss0=fusee-secondary.bin.
Or is it unintentional to have fusee-secondary as payload for void-nx? If so, what is the benefit of using fusee-primary?
Another thing: I use hekate as atmosphere/reboot_payload.bin. This makes it much easier to switch to a different nand from vöid-nx (most people have multiple nands: one for online and one for offline backups).
Do you think, it would make sense to set hekate as default reboot payload in void-nx?
Fantastic, thank you very much for doing this!
The reason it isn't using fss0 at the moment is to make it HBG Shop compatible (I said the cursed words, sorry!), mainly so everyone is happy, however, I am working on a way to use fss0 but chainload primary through Hekate using the payload option, that way people can have fast boot time, use fss0, and use HBG if and when it's needed.
The issue is, at the moment I don't have enough time to shoot this out today due to work, however, this will be Void 5.0 as I want Void to be usable and accessible for literally everyone if possible.
So the plan is.
Use fss0 by default, include primary on the SD Card so people can go to payload > primary in Hekate is they need and/or want HBG, but use fss0 for speed and ease of use.
I'll let you know once this is done though!
@Synecdoche
The PKG2 sigpatches have been updated 2 hours ago.
I have tested them with fss0=fusee-secondary.bin. Using this, the boottime is much faster.
It would be cool, if you could pack these patches to void-nx and set the payload to fss0=fusee-secondary.bin.
Or is it unintentional to have fusee-secondary as payload for void-nx? If so, what is the benefit of using fusee-primary?
Another thing: I use hekate as atmosphere/reboot_payload.bin. This makes it much easier to switch to a different nand from vöid-nx (most people have multiple nands: one for online and one for offline backups).
Do you think, it would make sense to set hekate as default reboot payload in void-nx?
@MSco
Can you past your hekate_ipl.ini configuration please?
5.0 is out.
Boiled down to two new editions because let's be real, no one wants an unpatched version. It came to me that people would rather have faster load times and no HBG, than just a regular unpatched version. And given what Void is a noob-friendly package, I believe the majority would want to be patched over unpatched, as there is another CFW available if you don't want it patched at all.
If you'd like an unpatched version, they will remain on GitHub and maintained when absolutely needed (such as a new Atmosphere version), but until then, they will remain as they are as I don't think people want 6 different versions of Void (or if you do, let me know and I'll update them as well).
Now there is a regular version and an HBG version, but what's the difference?
Please note, this took a little thinking to get working due to being busy at the moment, so one or two things MAY be broken, but PLEASE if anything is broken in any version, let me know and I will fix it as soon as humanly possible.
Right now, on my end, everything is verified as working.
QUICK EDIT:
This may be the last update for a while, unless anything is broken of course, mainly due to right now I don't know what to add to make it any easier for people. Regardless, if you have any suggestions please let me know and I will do it as soon as possible.
Also a word on the Toolbox and Updater. Right now, I have no plans to do either, mainly because I don't want to fork both of those things and potentially screw up, and I especially don't want to step on anyone's toes on using it, such as Team Neptune or the old Kosmos team. If anyone has an updater or toolbox they'd like to donate or anything then that is very kind of you, if not, then please don't expect those features anytime soon.
Boiled down to two new editions because let's be real, no one wants an unpatched version. It came to me that people would rather have faster load times and no HBG, than just a regular unpatched version. And given what Void is a noob-friendly package, I believe the majority would want to be patched over unpatched, as there is another CFW available if you don't want it patched at all.
If you'd like an unpatched version, they will remain on GitHub and maintained when absolutely needed (such as a new Atmosphere version), but until then, they will remain as they are as I don't think people want 6 different versions of Void (or if you do, let me know and I'll update them as well).
Now there is a regular version and an HBG version, but what's the difference?
Normal
- Boots using Fusee Secondary, making load times a lot faster.
- This means that HBG Shop does NOT work with this version.
- This boots much faster than the HBG version due to using fss0.
- Names been changed to sysVOID and emuVOID, because why not?
- Added payload launcher homebrew app from suchmememanyskill to allow you to launch into Hekate if needed. Thanks to @MSco for the suggestion.
- Up to date, Hekate sigpatches included.
- Added Hekate and Fusee Primary to the payloads folder, for launching with Payload Launcher and if you want to chainload yourself using either version.
HBG
- Launches how it did previously, by chainloading Fusee Primary.
- Please note, this makes launching Atmosphere much slower.
- Names been changed to sysVOID and emuVOID, because why not?
- Up to date, sigpatches included.
- Added payload launcher homebrew app from suchmememanyskill to allow you to launch into Hekate if needed. Thanks to @MSco for the suggestion.
- Added Hekate and Fusee Primary to the payloads folder, for launching with Payload Launcher and if you want to chainload yourself using either version.
Please note, this took a little thinking to get working due to being busy at the moment, so one or two things MAY be broken, but PLEASE if anything is broken in any version, let me know and I will fix it as soon as humanly possible.
Right now, on my end, everything is verified as working.
QUICK EDIT:
This may be the last update for a while, unless anything is broken of course, mainly due to right now I don't know what to add to make it any easier for people. Regardless, if you have any suggestions please let me know and I will do it as soon as possible.
Also a word on the Toolbox and Updater. Right now, I have no plans to do either, mainly because I don't want to fork both of those things and potentially screw up, and I especially don't want to step on anyone's toes on using it, such as Team Neptune or the old Kosmos team. If anyone has an updater or toolbox they'd like to donate or anything then that is very kind of you, if not, then please don't expect those features anytime soon.
Last edited by Synecdoche,
@favoulos I simply use this one:
https://raw.githubusercontent.com/HarukoNX/PKG2-Patches/master/hekate/hekate_ipl.ini
@Synecdoche wow nice, thank you.
https://raw.githubusercontent.com/HarukoNX/PKG2-Patches/master/hekate/hekate_ipl.ini
@Synecdoche wow nice, thank you.
Similar threads
-
-
-
@
Xdqwerty:
@SylverReZ, @Psionic Roshambo something like each group of 3 does the exam (dunno how to explain it)+1 -
-
-
-
@
Xdqwerty:
@Psionic Roshambo, More or less those activities where two or more people do a exam instead of 1 (I still don't know how to explain)
-
-
-
-
-
-
-
@
K3Nv2:
I wish we could comment on Google reviews some of them just sound like they were written by r tards+2 -
-
-
-
-
-
-
-
S @ StealthD0g99:I think we as a society should take the Cave Johnson approach to scientific studies
-
-
-
@
K3Nv2:
Lmao now I can live the life of Juan https://store.playstation.com/en-us/product/UP5805-CUSA47233_00-0050709204508097
