ZebraEngine: GuardianForce sourced NSPs crashes on boot.
Title was: Only Boomerang injects work
INFO:
To provide some needed info on this issue. These are the known Saturn Tribute base files.
1.) Cotton2 Saturn Tribute [0100A18015268000][v0][Base].nsp
2.) Cotton Boomerang Saturn Tribute [010077001526E000][v0][Base].nsp
3.) Guardian Force Saturn Tribute [0100C67015270000][v0][Base].nsp
4.) Cotton Guardian Force Saturn Tribute [0100094014BE4000][v0][JP].nsp (3-in-1)(1gb)
5.) Cotton Guardian Force Saturn Tribute [0100094014BE4000][v0][JP].xci (3-in-1)(2gb)
This issue thread is specifically about # 3. This is worth pointing out because # 4 is easy to get confused with # 3. In the US, it is just Guardian Force. No “Cotton” at the beginning of its name.
Until recently, I did not even know that the 3-in-1 NSP even existed. It WAS unsupported, and might be what was confused for this issue. But I don't think so. Either way, it is supported going forward in the next build.
Check the TitleID’s of your files before reporting.
Comments (12)
-
reporter -
reporter - edited description
- changed title to ZebraEngine: GuardianForce crashes on boot.
-
reporter - changed title to ZebraEngine: GuardianForce NSPs crashe on boot.
-
Cotton Boomerang Saturn Tribute NSP = Worked with custom wallpaper and game ran
Cotton Guardian Force Saturn Tribute NSP = CaVE Created NSP, Game Errors when launching “Error Code: 2002-0001” if you click OK it shows your custom controller prompt and you will get the error again, click OK and yo will see the custom wallpaper that was added during setup but the game will not load.
Cotton 2 Saturn Tribute NSP = Worked with custom wallpaper and game ran
** During CaVE Zebra setup I did not know what to put for the INI. CaVE has it checked already and green even though its blank. I just left that as is during my testing.
The errors I got from Cotton Guardian Force Saturn Tribute NSP creation could be my file is bad. But I will let other weigh in and test that.
-
reporter When a option is already ticked green, it means its optional. The option in the case of the ini being that you can either select a pre-made one, or let CaVE generate a default one. Either way, in the Advanced Settings you can choose to adjusts those options.
I will wait for a further test to make a conclusion, as you suggest it may have been your fault for selecting a bad ini?
FYI, when selecting a wallpaper, I would recommend not selecting it in the first slot. The first slot is used by the default black wallpaper, and seeing as that was the issue with GuardianForce, it not copying over that default wallpaper… Replacing it with a custom one negates the result of the test. Im guessing you replaced the first wallpaper, it it still crashed. Thus… I cant say this is the same issue I am trying to resolve. Perhaps its another though.
For the sake of being on the same page, and ruling this out… This is the info on my base GuardianForce NSP.
Guardian Force Saturn Tribute [0100C67015270000][v0][Base].nsp
Sha1: E3C9E1A02FBF07C984045D3388F350D1947120A0
MD5: 94831853E30A3F98274DD329D15B502F
CRC32: E927B353
Please confirm its the same or different if the issue persists.
In the meantime, as you have indicated that you made 2 working NSPs, I will point you to these 2 other Issues that you can weigh in on. Invisible Menu (I.E. you cant see it at all) and Advanced Menu being broken (I.E. no settings in it have values.)
-
I did not weigh in on those two issues because I’m not sure what that is even about. I don't really understand what the issue was in the first place.
If by menu issues you mean by pressing the “-” button in the game the menu pops up just fine. I created one NSP with the option hidden and one with the option not hidden. As far as I can tell everything works fine.
I don't know much about the Saturn system. But I can say that I created a Game with CaVE and it loads, took a custom wallpaper, and plays. Outside of that I don't have much experience in this console .
-
reporter This should be discussed in the other topic… but…
The invisible menu issue is quite simple, as I explained. Can you see the menu at all when you press the - button? If so, its working correctly! If you cannot… its bugged. The issue is unrelated to choosing to hide that UI element that reminds you of how to bring up the menu. But its good to hear that itself is working.
You don’t need to know much if anything about Saturn to test these things, or report on them. A menu is a menu. Can you see it, or not. As for the setup wizards Advanced menu, the issue is… do the options in that page have values, or are they ALL blank?
-
reporter - edited description
- changed title to ZebraEngine: GuardianForce sourced NSPs crashes on boot.
-
reporter - edited description
-
reporter While I deem it not related to this issue, its worth mentioning here that I have fixed compatibility with the 3-in-1 NSP now that I am aware of it. Due to its name, and me not knowing it existed… it was getting confused with the real Guardian Force NSP thats on topic to this issue.
Also, while he did not post it here, once Tokyo got the correct NSP, he did confirm that the real Guardian Force NSP does now boot/work correctly.
-
1.) Cotton2 Saturn Tribute [0100A18015268000][v0][Base].nsp Works 2.) Cotton Boomerang Saturn Tribute [010077001526E000][v0][Base].nsp Works 3.) Guardian Force Saturn Tribute [0100C67015270000][v0][Base].nsp Works 4.) Cotton Guardian Force Saturn Tribute [0100094014BE4000][v0][JP].nsp (3-in-1)(1gb) Works, however my NSP is ~900 MB 5.) Cotton Guardian Force Saturn Tribute [0100094014BE4000][v0][JP].xci (3-in-1)(2gb) Works, however my XCI is ~1.3 GB
-
reporter - changed status to resolved
Fixed and Resolved!
FYI, I was just rounding up on those 3-in-1 sizes. Your 900MB NSP is probably the same. But your 1.3gb XCI is different than my 1.949GB xci.
- Log in to comment
This has been verified false.
It is likely an exaggeration from a guy too lazy to prove it. He likely tried and failed to use GaurdianForce, succeeded with Boomerang, and just concluded Cotton2 did not work.
Cotton 2 definitely did and does work.
However… as indicated, GuardianForce did not always work. That issue was because the default black wallpaper was not getting copied over, and the app of course tried to load it. This is now fixed.
I will repurpose this issue thread for THAT issue.