Yes, they did and apparently they work fine and the ones that don't work do if reprocessed. That's the reason for my guess.Has someone checked if XCIs including updates+dlcs and everything else work again with SX OS 2.9.1 ?
Yes, they did and apparently they work fine and the ones that don't work do if reprocessed. That's the reason for my guess.Has someone checked if XCIs including updates+dlcs and everything else work again with SX OS 2.9.1 ?
Yeah but apparently the ones made with newer NSCB versions are ok, so my guess is that it's related to people still having some from that specific version or from certain discord that spent months using an older version.Just about SX OX 2.9.1:
"There is still XCI compatibility issues, we're looking into, but this should solve *a lot* of issues for people who could not play any games on 9.x.
We're investigating those... People who repacked games to include updates, those are the only ones that still have issues on 9.x."
I've read of errors using XCIs + going online. I never go online, so I just read it.
And I've read of homebrew not working in docked-mode.
Hello, i got more information, i've pinpointed what is the NSCBuilder version that is causing ISSUES. It's 0.79, Torna, XC2, MK8 with updates and DLC will FAIL on SX OS 2.9.1 / FW 9.0 when converted with that version of the tool, but if extracted with NSCBuilder 0.90 and repacked with 0.90 they work fine on SX OS 2.9.1 / FW 9.0.You mean about the xci not working working again when reprocessed? I have a guess about that.
When nscb process a convert from xci to nsp if you change it back to xci it will figure out it was a xci originally so it will restore isgamecard to 1. There was an old version that had a bug where it restored it when it shouldn't, this version was been used by some discord group for several weeks or months.
Well that bug was fixed quickly and when reprocessed the program figures out the original flag for those xci so that's my untested guess.
I think the bug was in 0.65 from memory but not sure it was in a really old version.
I'm pretty sure you don't need to extract them, only reprocessed them. My guess is that is related to the bug it had in the restoration of isgamecard, also any newer version will do. 0.91b for example that is the latest.Hello, i got more information, i've pinpointed what is the NSCBuilder version that is causing ISSUES. It's 0.79, Torna, XC2, MK8 with updates and DLC will FAIL on SX OS 2.9.1 / FW 9.0 when converted with that version of the tool, but if extracted with NSCBuilder 0.90 and repacked with 0.90 they work fine on SX OS 2.9.1 / FW 9.0.
I hope this helps resolving the issues and find out why specifically the games fail!
Good day.
If one of you do a verify over one of the addected files and show me the result i'd know if my guess is correct. If i my guess is correct i can fix it infile. Level 2 is enough, just want to see if it says isgamecard was changed from 0 to 1. 1 to 0 is normal, 0 to 1 means it was affected by the bug and changed the isgamecard on something that was eshop originally.OMG. Would be nice to get a small batch to check if a XCI is affected or not.
I'm pretty sure you don't need to extract them, only reprocessed them. My guess is that is related to the bug it had in the restoration of isgamecard, also any newer version will do. 0.91b for example that is the latest.
So basically just use mode1 or 2 with the files, the reason it fixes it is because it figures if the original content was eshop or physical and restores the header.
--------------------- MERGED ---------------------------
If one of you do a verify over one of the addected files and show me the result i'd know if my guess is correct. If i my guess is correct i can fix it infile. Level 2 is enough, just want to see if it says isgamecard was changed from 0 to 1. 1 to 0 is normal, 0 to 1 means it was affected by the bug and changed the isgamecard on something that was eshop originally.
I'm pretty sure you don't need to extract them, only reprocessed them. My guess is that is related to the bug it had in the restoration of isgamecard, also any newer version will do. 0.91b for example that is the latest.
So basically just use mode1 or 2 with the files, the reason it fixes it is because it figures if the original content was eshop or physical and restores the header.
--------------------- MERGED ---------------------------
If one of you do a verify over one of the addected files and show me the result i'd know if my guess is correct. If i my guess is correct i can fix it infile. Level 2 is enough, just want to see if it says isgamecard was changed from 0 to 1. 1 to 0 is normal, 0 to 1 means it was affected by the bug and changed the isgamecard on something that was eshop originally.
If i my guess is correct i can fix it infile.
Just need a screenshot of verify from 4, for example. I want to see if it's the isgamecard thing.
On one that doesn't work. @18Phoenix @huma_dawii
Nope, it's not what i thought. I don't see the reasoning then. I shouldn't have change anything important there. Also pretty standard, just titlerights removed.
Nope, it's not what i thought. I don't see the reasoning then. I shouldn't have change anything important there. Also pretty standard, just titlerights removed.
Maybe order of the files, perhaps?
Maybe they need them ordered by title now? If it's that no other route than redoing files.
IF they were done with legacy or the equivalent to legacy it would orther them by name, on other hand the new mode reads the cnmts and should pack the files in order, that may be the reason. If is this second guess not sure if it's xecuter's fault, it may be a change on Nintendo's side.
Oh, wait. The error is while mounting? Now that i think about it if it's while mounting it could actually be xecuter's, depends on how they handle that.
@18Phoenix If you can check some of yours? If what fails isn't in order i think that's the reason.
One final note, i'll need to check how i pack them in mode 1, not sure if it's in order or depends on how the nsp, xci you input is packed. For example SD2nsp and dumped nsps are not packed by cnmt like Nintendo's order usually. Mode 2 should do that, so a Mode2 + packed by id should fix them when rebuilding for now. Again, if my current guess is right.
I think it could be the order. Not sure of course. BTW 0.91b has the bar issue from the second picture fixed.View attachment 181250View attachment 181251 What happened here, looks wierd ?
or
View attachment 181252