So it seems if there is an error of some sort it won't actually show it to the user if a bootlogo is being used. I was using kip1patch=nosigchk with a modified FS.kip (I did the hex edit suggested in another thread that I think they called "ACID patching" to get NRPs built with tools like 4NXCI to work) which I guess wasn't doing anything before since I suppose that patch wasn't actually active yet or something. As such it sort of got carried over from before I even had the modified kernel. Anyway, this caused it to just hang on the boot logo. If I went into the menu and manually launched it, only then could I see the error. So perhaps it should do something when there are errors to actually let the user know what's up or even that there was an error and not just things acting up or whatever (I had assumed it just simply didn't work right the first few times.) Honestly I'd personally rather it did something like showing the text over the bootlogo even if that's what it takes (though that certainly wouldn't be nice.) At least that would be my suggestion if it can't actually clear the logo off and show the full text when something goes wrong. Kind of a "it's not a great solution, but at least it does what's necessary" sort of thing.
BTW, is there any chance anyone would be willing to show me exactly what INI lines I need for ReiNX? They don't support using Hekate because they expect you to just launch their payload, but I need Hekate's ability to do things like making/restoring backups and, more importantly, I plan to go the SwitchMe route whenever those things ship and a Hekate that is able to do all those things and chainload makes a heck of a lot more sense than a specific CFW's payload that may even change how it works from time to time and need frequent updating... Since they keep changing things around (like removing fs_mitm.kip) it seems beneficial to not necessarily always use the payload (for instance, if I put fs_mitm.kip in a separate folder I can manually load it when needed -- and since it causes problems with one game yet I need it for another this is useful.) Well, at the minimum it would be nice to at least have the basics. For instance, should I be using the atmosphere=1 line? It does a lot of the stuff Atmosphere does, but not all. It's not very clear what it means about atmosphere patching. I initially thought it referred to stuff like layeredfs from whatever it said before when the readme was even more sparse than it is now, but now I realize that I have even less idea what it means than I thought I did before (and I was already pretty doubtful.) I've been setting it with ReiNX, but I don't know if I should or if it may be doing more harm than any good. I'm also curious about this pm.kip. The official releases do not include it, but the sdfiles build linked to on the first page has it. I have no idea what it does and it's surprisingly hard to google and actually get anything useful. Given that they've stopped including the layeredfs fs_mitm.kip but it still works (for now) I'm wondering if this is one of those "basically beneficial, but not officially supported" things? Similarly I'm not clear on what SVC even is and googling it has been even less helpful than searching about the pm.kip, but that one I've assumed is one of those "if you have to ask it's not something you need to mess with" things (still, it would be nice to know what the heck it even is even if that is the case.) It's actually weird how hard it is to find information about some of this stuff. Simply put I haven't found anything clear on exactly what to put in there for this and even third party "SDFILES.zip" builds by various people (and of course their own) do not include anything about it. We're supposed to just know, but I don't just know.
BTW, is there any chance anyone would be willing to show me exactly what INI lines I need for ReiNX? They don't support using Hekate because they expect you to just launch their payload, but I need Hekate's ability to do things like making/restoring backups and, more importantly, I plan to go the SwitchMe route whenever those things ship and a Hekate that is able to do all those things and chainload makes a heck of a lot more sense than a specific CFW's payload that may even change how it works from time to time and need frequent updating... Since they keep changing things around (like removing fs_mitm.kip) it seems beneficial to not necessarily always use the payload (for instance, if I put fs_mitm.kip in a separate folder I can manually load it when needed -- and since it causes problems with one game yet I need it for another this is useful.) Well, at the minimum it would be nice to at least have the basics. For instance, should I be using the atmosphere=1 line? It does a lot of the stuff Atmosphere does, but not all. It's not very clear what it means about atmosphere patching. I initially thought it referred to stuff like layeredfs from whatever it said before when the readme was even more sparse than it is now, but now I realize that I have even less idea what it means than I thought I did before (and I was already pretty doubtful.) I've been setting it with ReiNX, but I don't know if I should or if it may be doing more harm than any good. I'm also curious about this pm.kip. The official releases do not include it, but the sdfiles build linked to on the first page has it. I have no idea what it does and it's surprisingly hard to google and actually get anything useful. Given that they've stopped including the layeredfs fs_mitm.kip but it still works (for now) I'm wondering if this is one of those "basically beneficial, but not officially supported" things? Similarly I'm not clear on what SVC even is and googling it has been even less helpful than searching about the pm.kip, but that one I've assumed is one of those "if you have to ask it's not something you need to mess with" things (still, it would be nice to know what the heck it even is even if that is the case.) It's actually weird how hard it is to find information about some of this stuff. Simply put I haven't found anything clear on exactly what to put in there for this and even third party "SDFILES.zip" builds by various people (and of course their own) do not include anything about it. We're supposed to just know, but I don't just know.
