XCI-Cutter tool (Windows)

daniyo · Jun 19, 2018

I'm having some trouble with some trimmed+split 4GB files. SX OS recognizes the split games but return a "Game card could not be read". Trimmed files work on single file roms (smaller than 4GB). Any ideas?

ravensfan8448 · Jun 19, 2018

daniyo said:
I'm having some trouble with some trimmed+split 4GB files. SX OS recognizes the split games but return a "Game card could not be read". Trimmed files work on single file roms (smaller than 4GB). Any ideas?

I'm having the same issue as you. I thought I was running an outdated version of XCI cutter, because the properties on the exe shows it as version 2.4.0.0 which evidently has broken cutting. I just downloaded the exe for 2.4.1 from the github again though and its the same exe I had before, still showing as 2.4.0.0.

MHDestination · Jun 19, 2018

ravensfan8448 said:
I'm having the same issue as you. I thought I was running an outdated version of XCI cutter, because the properties on the exe shows it as version 2.4.0.0 which evidently has broken cutting. I just downloaded the exe for 2.4.1 from the github again though and its the same exe I had before, still showing as 2.4.0.0.

Okay, i've sent a mail to Team Xecuter.

Maybe their backuploader needs a specific part size.

For now you'll have to use exFAT for games >4GB.

Splitting will be fixed as soon as i'll receive a response by TX.

daniyo · Jun 19, 2018

MHDestination said:
Okay, i've sent a mail to Team Xecuter.

Maybe their backuploader needs a specific part size.

For now you'll have to use exFAT for games >4GB.

Splitting will be fixed as soon as i'll receive a response by TX.

I also sent an email to TX earlier this morning so I will keep you guys updated either way!

Cha0tic · Jun 19, 2018

How do I choose between cutting/splitting? Would like to just try to trim some games.

oops never mind just saw it says split to 4gb.

MHDestination · Jun 19, 2018

Cha0tic said:
How do I choose between cutting/splitting? Would like to just try to trim some games.

just don't click the checkbox for "4GB splitting".

Then it will just trim.

Cha0tic · Jun 19, 2018

MHDestination said:
just don't click the checkbox for "4GB splitting".

Then it will just trim.

Just saw it and edited my previous post lol

dsafra · Jun 19, 2018

ummmm u asking about if they can addd the sx can read the extension of splitted file? because splitting again all games nooooo

MHDestination · Jun 20, 2018

I've got a response from Team Xecuter. The devs need to investigate why SX OS doesn't play split games.
Might take some days.

But they sent me a license to test & try to fix it myself.

Thanks @ Team Xecuter!

Dmafra · Jun 20, 2018

Layeredfs games are trimmed on procces or if I use this tool will be even smaller?

MHDestination · Jun 20, 2018

Dmafra said:
Layeredfs games are trimmed on procces or if I use this tool will be even smaller?

For layeredfs you'll use only the extracted gamedata (exefs + romfs). Therefore there's nothing to trim.

Layeredfs is even smaller than trimmed dumps.

mypetfrog · Jun 20, 2018

Thanks for sorting this, I thought it was just me.... Fingers crossed it's a simple and quick fix

daniyo · Jun 20, 2018

Thanks for fixing the XCI Splitter! I will give it a try tonight!

MHDestination · Jun 20, 2018

I've figured out why SX OS won't play split dumps.

SX OS is a bit picky regarding filesize.
The parts have to be aligned to sdcard clustersize.

I've changed the partsize to a multiple of 32k. Now everything is working as it should.

New bugfix release is up:
https://github.com/Destiny1984/XCI-Cutter/releases/tag/v2.4.2

Unfortunately everyone who has split their dumps with an earlier version,
has to merge the files ("Uncut" option) and split again with the fixed version.

KTroopA · Jun 20, 2018

MHDestination said:
I've figured out why SX OS won't play split dumps.

SX OS is a bit picky regarding filesize.
The parts have to be aligned to sdcard clustersize.

I've changed the partsize to a multiple of 32k. Now everything is working as it should.

New bugfix release is up:
https://github.com/Destiny1984/XCI-Cutter/releases/tag/v2.4.2

Unfortunately everyone who has split their dumps with an earlier version,
has to merge the files ("Uncut" option) and split again with the fixed version.

great work mate, thank you loads for this

mypetfrog · Jun 20, 2018

Brilliant - thanks. Testing now

PatrickStarSb · Jun 21, 2018

2.4.2 download link is broken...

edit: nvm back up

tuntun · Jun 21, 2018

hmmm tried the new version of the splitter and got the same error,

BOTW

and the error is "game cart could not be read" tried two different files.

on 4.1 and sd card is 128 gb fat32

DocKlokMan · Jun 21, 2018

It's due to fragmentation. If it's not split to cluster size then the Switch thinks there's gaps in the code when it reaches the end of the cluster. While 32K is the default cluster for FAT32, it's not the only cluster size. For larger cards some formatters may default to 64K which would leave a gap at the end of some segments due to this code here:

Code:

Friend ReadOnly ChunkSize As UInt32 = 2 ^ 32 - 32 * 1024

which would leave one 64K cluster half empty.

Either make it 2^32 flat or make them 2GB instead of 4GB if you're having issues with the split files fitting on the cards (2^31)

MHDestination · Jun 21, 2018

tuntun said:
hmmm tried the new version of the splitter and got the same error,

BOTW

and the error is "game cart could not be read" tried two different files.

on 4.1 and sd card is 128 gb fat32

Please format your sd card with 32k clustersize.
You can use GUI Format for that.

AnalogMan said:
Either make it 2^32 flat or make them 2GB instead of 4GB if you're having issues with the split files fitting on the cards (2^31)

2^32 would be exactly 1 byte to big for FAT32.

2GB parts might give to many parts for bigger gamecarts (>32GB).
I'm not sure if SX OS would handle parts with two digits (.xc10 .xc11 .xc12 ...)

To make sure that the files are usable with 64k clusters I could just subtract 64k from 4GB:

Code:

Friend ReadOnly ChunkSize As UInt32 = 2 ^ 32 - 64 * 1024

(But i think a maximum of 32k clusters is the better choice for sdcards.
64k wastes to much space when you have many small files)

Member

Active Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Well-Known Member

Active Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

Active Member

Plugin Dev

Well-Known Member

Similar threads

Popular threads in this forum