Adding an option to reboot after making the changes would really make this a nice application
Those aren't kips nor are they loaded via LayeredFS. They're basically exefs overrides similar to the hbl.nsp for the Album and are loaded via the loader.kip.Great.
Can it ignore 32,34,36 folder or add description about them in layeredfs tab?
I think these are default folder by atmosphere
Great.
Can it ignore 32,34,36 folder or add description about them in layeredfs tab?
I think these are default folder by atmosphere
Looks great! Is there a way we can name or label the items in the LayeredFS tab, for instance if I have one as my NX theme, and another as a Mario Odyssey mod, I'd like to differentiate them. I tried updating the NSWreleases.xml but that didn't do anything it seems.
The ReiNX toolkit already accomplishes, but not for LayeredFS management. For now, it just manages kips.Gotcha thanks I missed that.
Second question, would you be willing to please add support for ReiNX folder locations too? Since it essentially uses the same LayeredFS and Kips as Atmosphere, but instead stores them under it's own folder under [root]\ReiNX\ which is kept separate from the Atmosphere folder.
Gotcha thanks I missed that.
Second question, would you be willing to please add support for ReiNX folder locations too? Since it essentially uses the same LayeredFS and Kips as Atmosphere, but instead stores them under it's own folder under [root]\ReiNX\ which is kept separate from the Atmosphere folder.
Its most likely a issue with the new kip detection stuff, use 3.0.6 for now. Long story short i found a rather crippling bug in that new versions code an hour or so ago, i've removed the release from GitHub until i get it sorted.Kip_Select_V3.0.7 atmosphere 0.8.3 error ,crash OFW 6.2 .previous versions work normally
Only kip I've got is SaltyNX, which is used by ReverseNX.surprised people are still loading kips, don't even have anything that's still a kip that I can think of.