TX is on roll, release after release, and today's big release is brand-new SX OS v2.3 BETA

As you read thru TX's announcement below, you will quickly see that is jam-packed with all the features you have been requesting recently like SD EmuNAND and USB Homebrew, so check it out below:

Your favorite superheroes from Team Xecuter are back with another SX OS update.​

In v2.3 beta of SX OS we have some exciting new functionality that you, the community, has been requesting a lot. As you know, we value your feedback and support.. so your wishes are our command!

Let's have a look at the changelog:

• SD emuNAND support
  Since the introduction of our emuNAND feature we got a lot of comments about our initial decision to make the emuNAND data live on the actual system NAND. After lots of hard work we are happy to say we now have a workable solution for storing your emuNAND partition data on your microSD card. This has the upside of not using up any space on your Switch. In order to use the new microSD emuNAND system you will *not* have to format your microSD card. Simply enter the TX boot menu by holding Volume-+ while powering on your switch. Head into the options menu and select emuNAND on the left. Users of our existing emuNAND solution will see an option to migrate their existing emuNAND data. The migration process also cleans up the old emuNAND from the system NAND. Painless! We're interested in hearing your feedback about this exciting new functionality.
• The 'Emutendo' folder
  In addition to the new microSD emuNAND system we also introduce the 'Emutendo' folder on your microSD card. As you've probably noticed, the Switch saves various data to a 'Nintendo' folder on your microSD card. To completely decouple this data between your Original Firmware and your EmuNAND enabled firmware we have made EmuNAND enabled systems use this differently named folder. If you want keep using your old SD card data with your emuNAND, simply copy/rename the 'Nintendo' folder to 'Emutendo'.
• Added more directories to scan for content
  By popular demand we have added yet another list of subdirectories that will be scanned on your microSD card (or USB harddisk) for XCI/NSP/homebrew. The directories that have been added are:
  • – /sxos/updates
  • – /sxos/dlc
  • – /switch/updates
  • – /switch/dlc
• Homebrew menu takeover of any title by holding R
  Homebrew is usually launched from either the TX menu or the Homebrew Launcher menu. Both of these applications run as an 'applet' on the Switch. Applets do not have access to all of the system's memory, and thus any homebrew apps or games launched from here are affected by this as well. The only way to allow full use of the system's memory was to build and install homebrew NSP files. But now we have added another way to give homebrew applications full memory access! You can now hold the (R) button while launching any regular title, and this will launch the Homebrew Launcher Menu. Any homebrew launched from here will run with the same capabilities as a regular Switch game/app. Enjoy!
• Loading homebrew from USB
  More good news for homebrew lovers. You can now copy homebrew NRO files to your USB harddisk as well, and launch them directly from our SX OS menu.
• Stability improvements
  Overall stability of many components has been improved. This includes LayeredFS and USB incompatibilities. We have also fixed a bug which would prevent people from launching more than 32 titles.
• libusbfs update
  Last but not least a small update for developers. We've squashed a small bug in libusbfs pertaining the stat() function. If you had issues with this, grab an updated copy of libusbfs from our website!

The year 2018 is entering its final months. That does not mean we're taking a break from working on our beloved SX OS though. And yes, also those new 'unhackable' consoles are high up on the agenda. Don't worry, we will deliver.

Keep sending your feedback and ideas, they're very welcome.

See you all in the next update!

--< Team-Xecuter - Rocking the Switch in 2018 and beyond! >--​

Source: MaxConsole

 

[Ev1l0rd]

Oof so it's another hackjob?

I mean, I kinda suspected it given the repeated structure, but yes it is.

Also, sup guys, we can talk about stolen Atmosphere code again w/o it being off-topic since they stole the SDMMC driver from Atmosphere.

 

[Essasetic]

Nice to see Atmosphere ripping off TX again.

You reading the tweet wrong? Because it's the other way round. They're using their files lmao.

 

[thaikhoa]

Thanks Hexyz for detailed change logs.

 

[tinkle]

TX Released first.

 

[Essasetic]

TX Released first.

How is Atmosphere a rip off then?

--------------------- MERGED ---------------------------

In fact TX stole code from them several times (the most recent example is the SDMMC driver which was from 2.3). They've also stolen code from several other developers. Just because they were first doesn't mean they're superior/original.

 

[Cubuss]

Did custom options to edit emunand size etc got removed ?

 

[thaikhoa]

At least, TX knows how to apply stealing codes to their creation. lol

 

[Ev1l0rd]

TX Released first.

TX stole the SDMMC driver from Atmosphere.

 

[thaikhoa]

Did custom options to edit emunand size etc got removed ?

Yes, they removed it in the latest one.

 

[mattytrog]

Here we go... The who ripped who off slanging match can begin...

It may use Atmospheres bits and pieces, but they seem to have implemented a working solution first, from these parts.

No point sitting on it. Thats the game. As the old Chinese proverb goes... "Shit or get off the pot."

TX assembled something first. For better or worse.

 

[Essasetic]

At least, TX knows how to apply stealing codes to their creation. lol

And how's that a positive? Literally anyone can do that.

 

[metaphz]

I have a backup of 1.0.0 untouched SysNAND, currently running 6.1.0 with 1 FUSE burned. Would the process be create the emuNAND while I'm still on 6.1.0, then restore my 1.0.0 NAND backup?

I have no interest (currently) in playing online (Switch has never been connected to WiFi), would only utilize emuNAND for "Brick" protection as my use case.

Lastly, I would like to be able to utilize networking for transferring files from PC to Switch. The whole DNS blocking idea looks like a poor stopgap measure. Would I be best served by setting up some rules in my router for my Switch to not allow access to WAN?

 

[Essasetic]

Here we go... The who ripped who off slanging match can begin...

It may use Atmospheres bits and pieces, but they seem to have implemented a working solution first, from these parts.

No point sitting on it. Thats the game. As the old Chinese proverb goes... "Shit or get off the pot."

TX assembled something first. For better or worse.

Even though the solution they made is a broken hackjob (like the first emunand) this could open up the doors to a lot of corruption in that case then.

 

[xabier]

Using the emunand. However I also don't recommend SX OS in general but you do you.

--------------------- MERGED ---------------------------


That and (since TX didn't make a partition for some reason I hope garyopa explains.) It can also delete everything for as something as simple as a homebrew crash.

Sd corruption is not an issue for me, I can backup my saves with checkpoint, I have enough room for my cartridge updates and digital splatoon on sysnand. I wouldn't go for emunand if I was banned but I m not. And corruption doesn't break anything, it s just a nuissance

 

[Essasetic]

However they were the first so I'll give them that I guess. Dammit TX you were doing well with not stealing code/making broken features.

--------------------- MERGED ---------------------------

Sd corruption is not an issue for me, I can backup my saves with checkpoint, I have enough room for my cartridge updates and digital splatoon on sysnand. I wouldn't go for emunand if I was banned but I m not.

Again. Only when something unintended happens is when the SD Card may start to corrupt.

 

[thaikhoa]

And how's that a positive? Literally anyone can do that.

As an end-user I don't care that much as it works. The one I care is how fast can I get new features. I'm playing game but not to code.

 

[Ev1l0rd]

Here we go... The who ripped who off slanging match can begin...

It may use Atmospheres bits and pieces, but they seem to have implemented a working solution first, from these parts.

No point sitting on it. Thats the game. As the old Chinese proverb goes... "Shit or get off the pot."

TX assembled something first. For better or worse.

They should respect and follow the license under which it got released.

GPL requires changes to be made available under same provisions as the license. I've repeated this over and over, and I'll say it again: They follow not a single clause of the projects they've just outright stolen.

This isn't a "who's who" situation, this is literally Warez and I'm still suprised as to why it's being permitted here when the rules explicitly forbid linking to Warez (which is done here indirectly by linking to MaxConsole which links to TX.

 

[Cubuss]

What internal storage should emunand be ? 25gb?

 

[Essasetic]

As an end-user I don't care that much as it works. The one I care is how fast can I get new features. I'm playing game but not to code.

That's the worst statement I've ever read.

 

[johnsnow]

TX stole the SDMMC driver from Atmosphere.

Nobody care man. The irony is Atmosphere stole the SDMMC driver code from Nintendo.