Everyone knows, you can stop now.
Even if that were true, who do you think cares about that?
Everyone knows, you can stop now.
Even if that were true, who do you think cares about that?
For an example.. Eshop games/update are always NSP files then you can installed it. Some XCI game are available for eShop then I would installed XCI instead. Some XCI games are not available for eShop then you can installed XCI instead. So both are better.
D
Deleted User
Guest
OP
I have looked at the thread now and am surprised that so many have answered in it. However, I also noticed that many such topics instrumentalize to speak TX badly.
So people, before it drifts too far to the left or right, please stick to the topic. This topic should not be used to pillory TX´s XCI Loader or their CFW.
Please stay objective in this topic.
Thanks xD
So people, before it drifts too far to the left or right, please stick to the topic. This topic should not be used to pillory TX´s XCI Loader or their CFW.
Please stay objective in this topic.
Thanks xD
A thread with no apparent solution. Up to this point I wonder how true Backup Loader could exist on Wii and WiiU and on Switch only talk about redirecting Backup as if it were cartridges with protected code. Was it on Wii and Wii U that it was also protected so that Backups Loaders existed?
Still waiting for an XCI loader that's free. (Fuck NSP format, XCI keeps your NAND clean)
Because it was much more simple on them. It didn't really require a lot of modification on actual firmware more than third-party IOS to apply the same function. Sure there were DARKCORP that did make it more streamlined else Neogamma was quite popular. Or Softchip.
XCI definitely does not keep your NAND clean.
Why would releasing a free XCI loader help TX? Its the main advantage TX has over Atmosphere or any other CFW. Not wanting to provide "a better implementation" doesnt make sense. They don't need a better implementation to steal (since their own one works and is the only working one available).
I hear far too many excuses for why we dont have a free XCI loader and none of them really make any sense to me.
The "dont support piracy" argument doesnt hold up when you can already install NSPs and convert XCIs to NSPs.And you also have free tools that dump your own carts to XCI format.
My understanding is also that TX didnt create the XCI format. So not only are you not vindicating TX by supporting the format, but the format is already been supported by people outside TX.
And then theres the argument about there arent any advantages to XCI over NSP or at least no need for it, which again doesnt hold up cuz there clearly are reasons such as not having to install your games, being able to load XCIs off a HDD, etc.
Has anyone got any real reasons besides being scared that Nintendo might come after them?
People don't generally care about .XCI usage anymore than they cared about .3DS usage. Most of the people I encountered wanting to use .3DS files were people hesitant to leave Gateway, but Luma3DS natives could not have cared less. Generally speaking, Atmosphere/ReiNX natives don't seem to care either.
Many people, myself included, wouldn't use HDD storage, as it hinders or downright ruins the portability of the Switch, and the installation of an NSP file effectively isn't any different time-wise than sending an XCI file to an HDD or SD.
Considering the above, and considering that XCI files can easily be installed as if they were NSP files, XCI support is just not worth the trouble at all.
TL;DR, we have game backups already in the form of NSP files, and there doesn't seem to be any real advantage in using XCI files.
Last edited by Lacius,
Having all your XCIs on a HDD isnt made redundant with the portability of the device. You can store all your XCIs on the HDD just like how you would on a PC, except I can still play them all on the TV. And if I want to take any of the games away with me, I can install the XCI to the nand or mSD card. Nothing is "hindered" here. Its basically giving you a whole new option of convenience.
And the 3DS comparison isnt the same. 3DS flash carts used mSD cards for storage. When you can insert that same mSD card into your 3DS and install CIAs, its pretty much the same thing.
But when you have a 2TB USB drive plugged into your dock on SXOS, I cant just switch to Atmosphere and carry on using that same 2TB drive.
The only way this becomes the same without a free XCI loader is if someone creates a way to mount the HDD as the storage device when docked, and then allow us to install our NSPs onto it.
And even then theres still the worry about not always knowing what you're installing and potentially risking a brick. I dont ever have to install XCIs before testing them and therefore never have to worry about it causing a brick.
As you said, if I want to be portable, I need to install my backups to the NAND or microSD card. Using uninstalled XCI files is a hindrance in this regard.
My point was that people don't usually care about .XCI backup-loading in almost the exact manner they don't care about .3DS backup-loading.
It's pretty much impossible to brick by installing an NSP file using an installer that checks to make sure the file is signed properly. On the other hand, XCI backup-loading doesn't do the same thing.
In other words, NSP backup-loading is safer.
Its not a "hindrance", its an option. No one is saying you have to pledge your allegiance to XCI, and then not be allowed to still use NSPs or install games.
People keep looking at this like its some kind of war, where you need to pick a side. When actually this made up war is being used as a excuse to not provide an extra option that many people would use. Why the need to make excuses? I don't know.
This deep rooted mentality of creating a divide between the user base and then pitting them against each other, is really weird.
Well it wasnt a very good comparison. You compared XCI loading (which literally has advantages), to 3DS backup loading that had zero advantages.
Theres a good reason why people didnt care about .3DS backups, and those reasons dont apply here with XCI loading.
How am I gonna brick anything with a XCI that never installs in the first place? In what way are NSPs more safer?
You're arguing semantics. The option is a hindrance.
When I'm making the point that a.) People generally only care that they have backup loading options, and b.) It's mostly users of Gateway and SX OS that care about .3DS and .XCI backup loading respectively, it's actually a very good analogy. Since it's an analogy, it's not going to be exactly the same.
An XCI-run backup can run malicious code (e.g. A prodinfo bricker) that's embedded. However, if I'm using a proper NSP installer that checks if the file was signed properly, it's impossible to install an NSP with something like the aforementioned malicious code embedded in it, since that would cause it to be unsigned.
Last edited by Lacius,
It doesn't install, but it's still running code. That's where the danger lies, if the XCI file was messed with.
This.
A good example was that old pikabricker.
It wasn't the installation that bricked your console, but rather running it.
While pikabricker (afaik) was never distributed as an XCI, it would have been trivial to convert it and use it in that format.
Im not arguing semantics. You're calling it a hindrance when the only hindrance is to the person having to create the XCI loader. If thats the real issue, then say it like it is.
And its not a good analogy when you're comparing two instances that arent the same. People didnt care about Gateway because it was completely redundant. XCI loading isnt redundant. There are uses for it that NSPs cant provide.
And on the subject of being "safer", of course a signed NSP is the safest thing out there, but signed NSPs arent the only type of NSP you're installing. Homebrew games wont be signed (such as that AM2R port that was made). And correct me if Im wrong, but when people change the firmware requirements of a game and repackage the NSP, that will also no longer be signed.
Also when people convert XCIs to NSP, that also isnt signed.
The point is that with both NSPs and XCIs, you're agreeing to accept the responsibility of running unsigned code. At some point you're gonna want to, and will knowingly accept the risk that comes with it. This applies to NSPs and XCIs.
Pikabricker was distributed as a NSP also. If NSPs were so safe, then it would've been released as an XCI instead. But it tried to reach the masses, and did so as a NSP.
So the general use of NSPs arent necessarily safer. There's an option where you can choose to only use signed NSPs, but by the same token, you can also use tools to verify NCA signatures within an XCI too.
NSPs in general arent more safer.
And as I said before, by accepting to use a XCI loader, you're not picking a side and deciding to never use NSPs again. You can still use NSPs with all of it's benefits, while still using XCIs.
You're making it sound like a war when its not. This isnt really about XCIs vs NSPs. Its about people being able to use their XCIs with their NSPs.
i convert all nszs to xci so i can simply mount them on my other switch that’s permanently hooked up to my tv and hdd
well useful when wanting to play a bunch of random stuff on the big screen and not having to waste time installing anything
well useful when wanting to play a bunch of random stuff on the big screen and not having to waste time installing anything
