Rethinking the 3DS (DLC) DAT

General No-Intro related discussions.
Post Reply
jimmsu
Datter
Posts: 439
Joined: 14 May 2010 22:14

Re: Rethinking the 3DS (DLC) DAT

Post by jimmsu » 07 Dec 2016 00:20

How should we use the differnt versions for Eshop :

Rev 01 , Rev 02 (is normal for cardridge versions)
V16 , v64 , v2064 (is what nintendo uses)

Hiccup
Datter
Posts: 264
Joined: 09 Oct 2015 11:29

Re: Rethinking the 3DS (DLC) DAT

Post by Hiccup » 07 Dec 2016 20:43

I suppose that does give you more info, but it does require some calculations to work out what the revision (i.e. 0, 1, 2) is.

gamecaptor
Posts: 210
Joined: 16 Jul 2010 06:27

Re: Rethinking the 3DS (DLC) DAT

Post by gamecaptor » 08 Dec 2016 08:00

jimmsu wrote:How should we use the differnt versions for Eshop :

Rev 01 , Rev 02 (is normal for cardridge versions)
V16 , v64 , v2064 (is what nintendo uses)
Personally I like "rev ##" or "ver ##" (or "v#.#") numbering because it's just it easier and more to the point. That's why I love DVD stuff because they include the version number right there for you to see, i.e. PS2 Crash Bandicoot - The Wrath of Cortex (USA) (v1.01).

Currently you are using Nintendo version numbering for Wii (DLC) but Rev for DSI (DLC).

So that said, which makes the most sense for 3DS eShop? You can pull the "v###" directly out of the file correct? So maybe that should be how it is labeled?

Hiccup
Datter
Posts: 264
Joined: 09 Oct 2015 11:29

Re: Rethinking the 3DS (DLC) DAT

Post by Hiccup » 08 Dec 2016 12:32

I don't think the v#### can be pulled from the files themselves - but it can be found in the CDN urls (?)
Last edited by Hiccup on 07 Jan 2017 20:26, edited 1 time in total.

gamecaptor
Posts: 210
Joined: 16 Jul 2010 06:27

Re: Rethinking the 3DS (DLC) DAT

Post by gamecaptor » 08 Dec 2016 17:51

Hiccup wrote:I don't think the v#### can be pulled from the files themselves - but it can be found in the filename of the TMD pulled from the CDN (?)
So then if the information is available (or at least located fairly easily), should that be the naming of choice? It makes sense to me to go with that format.

We need to start a voting poll :)

jimmsu
Datter
Posts: 439
Joined: 14 May 2010 22:14

Re: Rethinking the 3DS (DLC) DAT

Post by jimmsu » 08 Dec 2016 23:17

gamecaptor wrote:
jimmsu wrote:How should we use the differnt versions for Eshop :

Rev 01 , Rev 02 (is normal for cardridge versions)
V16 , v64 , v2064 (is what nintendo uses)

Currently you are using Nintendo version numbering for Wii (DLC) but Rev for DSI (DLC).

So that said, which makes the most sense for 3DS eShop? You can pull the "v###" directly out of the file correct? So maybe that should be how it is labeled?
For the Rev for DSI (DLC) , that comes from gameheader info.
Converted DSI (DLC) files to .nds can be read in there and you get the info.

gamecaptor
Posts: 210
Joined: 16 Jul 2010 06:27

Re: Rethinking the 3DS (DLC) DAT

Post by gamecaptor » 09 Dec 2016 01:18

jimmsu wrote: For the Rev for DSI (DLC) , that comes from gameheader info.
Converted DSI (DLC) files to .nds can be read in there and you get the info.
That brings up another can of worms that might need to be opened. Is it worth looking at the DSI (DLC) [i.e. DSIWare] DAT since we now have direct access to them from the CDN as well?

I spoke with Ptrk25 over on GBATemp and he said he is thinking that CDN-FX 3.0 will be ready early next year (depending on his schedule). He said he will also replace the custom header with 0's, this would give a slightly "cleaner" output.

I am starting a new job at the first of the year so I'm not sure how much time I will have but I can certainly start on getting a base for the DAT going. Considering how much will need to be added, it will definitely be a group effort.

hking0036
Posts: 73
Joined: 01 Oct 2016 18:33

Re: Rethinking the 3DS (DLC) DAT

Post by hking0036 » 09 Dec 2016 21:04

jimmsu wrote:How should we use the differnt versions for Eshop :

Rev 01 , Rev 02 (is normal for cardridge versions)
V16 , v64 , v2064 (is what nintendo uses)
It makes more sense to give a version number for digital updates rather than a revision noumber imo, plus it's the versioning that nintendo uses directly, as revisions are on carts.

gamecaptor
Posts: 210
Joined: 16 Jul 2010 06:27

Re: Rethinking the 3DS (DLC) DAT

Post by gamecaptor » 10 Dec 2016 00:00

hking0036 wrote:
jimmsu wrote:How should we use the differnt versions for Eshop :

Rev 01 , Rev 02 (is normal for cardridge versions)
V16 , v64 , v2064 (is what nintendo uses)
It makes more sense to give a version number for digital updates rather than a revision noumber imo, plus it's the versioning that nintendo uses directly, as revisions are on carts.
Actually I agree with that. I believe in pretty much every case the start screen of a game that has an update will reflect the version number (but I could be completely wrong; I'll need to check it out). Especially in the case of the update .cia files themselves it would makes sense for it to reflect that specific version update (i.e. v1.01).

Hiccup
Datter
Posts: 264
Joined: 09 Oct 2015 11:29

Re: Rethinking the 3DS (DLC) DAT

Post by Hiccup » 10 Dec 2016 11:34

Some games don't have that version number. And anyway, that number always doesn't tell you what revision the title is (v## or Rev 0, Rev 1 etc), but agree it should be included somehow.

Hiccup
Datter
Posts: 264
Joined: 09 Oct 2015 11:29

Re: Rethinking the 3DS (DLC) DAT

Post by Hiccup » 10 Dec 2016 11:34

hking0036 wrote:
jimmsu wrote:How should we use the differnt versions for Eshop :

Rev 01 , Rev 02 (is normal for cardridge versions)
V16 , v64 , v2064 (is what nintendo uses)
It makes more sense to give a version number for digital updates rather than a revision noumber imo, plus it's the versioning that nintendo uses directly, as revisions are on carts.
Don't forget that revisioning is also used for digital stuff.

hking0036
Posts: 73
Joined: 01 Oct 2016 18:33

Re: Rethinking the 3DS (DLC) DAT

Post by hking0036 » 10 Dec 2016 18:18

Hiccup wrote:
hking0036 wrote:
jimmsu wrote:How should we use the differnt versions for Eshop :

Rev 01 , Rev 02 (is normal for cardridge versions)
V16 , v64 , v2064 (is what nintendo uses)
It makes more sense to give a version number for digital updates rather than a revision noumber imo, plus it's the versioning that nintendo uses directly, as revisions are on carts.
Don't forget that revisioning is also used for digital stuff.
yes, but when nintendo is already providing version numbers it's simpler and makes more sense to go with the version numbers they already come with than to try and convert it into another format. This way, if anyone looks at the dump and sees a version number they know which one they have. If you change that to a revision it could lead to confusion comparing stuff from cdn to the dat.

norkmetnoil577
Datter
Posts: 16
Joined: 20 Aug 2016 21:30

Re: Rethinking the 3DS (DLC) DAT

Post by norkmetnoil577 » 15 Dec 2016 01:43

I like the idea of getting a more unaltered format, getting more releases covered, and all that come with this!

gamecaptor
Posts: 210
Joined: 16 Jul 2010 06:27

Re: Rethinking the 3DS (DLC) DAT

Post by gamecaptor » 15 Dec 2016 06:34

hking0036 wrote:yes, but when nintendo is already providing version numbers it's simpler and makes more sense to go with the version numbers they already come with than to try and convert it into another format. This way, if anyone looks at the dump and sees a version number they know which one they have. If you change that to a revision it could lead to confusion comparing stuff from cdn to the dat.
You are correct, it does ultimately make the most sense and probably the best way to address it.
norkmetnoil577 wrote:I like the idea of getting a more unaltered format, getting more releases covered, and all that come with this!
I'm hoping we can get this going in 2017.

jimmsu
Datter
Posts: 439
Joined: 14 May 2010 22:14

Re: Rethinking the 3DS (DLC) DAT

Post by jimmsu » 03 Jan 2017 00:24

I have seen a dat made by bsbt.

viewtopic.php?f=11&t=2829#p16889

Maybe we should do like that , only use the encrypted files like they are on the servers.

name , folder , files

Pokédex™ 3D
0004000000032600/00000000
0004000000032600/00000001
0004000000032600/tmd

Post Reply