Hi,

I've got a problem with my xnb files, but firs I have to get fix that my goal is to make a Xbox360 sprite based game, ok! Let's go:

During many days I am making the game on windows using TGA an JPG files, but today I got a look on the xnb files inside the Debug Content, and when I saw the size of the xnb files I almost fall from my chair, the memory size of the files are 4 times bigger than original TGA and JPG files if compared at windows Content.

Take a look at the MB size of the original and the xnb file:



This one is worst



So, my questions are:

When I shall publish the game to xbox360 the memory size of those files will keep huge just like above?

Is there a way to shrink the size of the XNB files to get the size of the original TGA and JPG files?



I will appreciate your help! ^^

Unfortunately that growth is the nature of the XNB file. It's a quickly read binary file, so it will not be as small as most file sizes. You can take a look at EasyZip (see link in my signature) which lets you have your project automatically place all the built content into a compressed ZIP file. It comes with a ZipContentManager that lets you stream the files out so you don't even have to unzip the package on the Xbox. I heard there are some bugs on Xbox, but that was just one or two and I haven't heard anything lately, but give it a try and see. It is open source, so you can also poke around and see if any bugs are easily fixable if they come up.

This is really (really) weird.

I have seen the exact oposite. As an example, I build a model and heavily smoothed it in Max, near to 200.000 vertices to do some test using nprof, and when the standard processor converts the x file (about 29 Mb in size without animations, and 30 Mb in size with constraints and 12 meshes animated) it ends with just 2 Mb!

Also, my tga files consistently decrease in size about 70 to 80%.

I will love to hear why are some files increasing and why others decrease (and decrease radically) in size.

Depends on the source data and the processor. For instance a PNG is a very compressed file. So if you build it to XNB with mipmaps you'll see massive size increases. As for you getting smaller files, that's new to me. I've never seen a file get smaller.

Well, to be strict, my tga files where uncompressed before processed by XNA, so maybe an aparent decrease in size is just because the way and format XNA ends with (with the xnb extension). I have a feel is something very similar to a .dds compresed file. But the .x file is a text file and it really decreased (as I said from 29 Mb to near 2 Mb).

Edit: I checked the .x file and it is 68.736 vertices. Decreased from 30.577 KB to 1.982 KB.

Anyways, I think the texture files size may increase if they where compresed before processed. As I said, I'll love to know why is this.

 

If you have an text file version of the X model, it will most likely shrink in size since the XNB is a binary format. Binary formats are almost always smaller than text equivalents. So that might explain why you see a gain there. Plus the XNB only stores the data that the processor deems relevant so any extra information or tags or other things like that won't end up in the final file. This can also result in a large cut-down of filesize.

Nick Gravelyn:

As for you getting smaller files, that's new to me. I've never seen a file get smaller.

If you convert a compressed format like .png or .jpg into uncompressed Color format, the data will get bigger.

If you convert an uncompressed format like .tga into compressed DXT format, the data will get smaller.

If you care about texture sizes, you should make sure your processor properties are set to use DXT compression.

Nick Gravelyn:

If you have an text file version of the X model, it will most likely shrink in size since the XNB is a binary format. Binary formats are almost always smaller than text equivalents. So that might explain why you see a gain there. Plus the XNB only stores the data that the processor deems relevant so any extra information or tags or other things like that won't end up in the final file. This can also result in a large cut-down of filesize.

 

Yep. That makes absolute sense. I think this about model files plus what Shawn said about compresed/uncompresed files explain it all.

So, there is no solution to this problem :-(  
 
However, my last chance to try shrinking those files is using that EasyZip, if that is the only way to shrink the files, I don't have another option except this :-\  
 
I wish with the Next GameStudio 3.0 they solve this problem with a new feature capable to reduce the size of the XNB files, I hope so.  
 
Thanks for help!

Fanboy Junior:

So, there is no solution to this problem :-( 

Sure there is.

"If you care about texture sizes, you should make sure your processor properties are set to use DXT compression."

If you want you can then use EasyZip to compress your data even further, but switching to DXT format is the easiest place to start.

Though remember DXT compression is lossy so may blur depending on what i in your textures and can possibly blur any alpha resulting in a non perfect alpha around edges.

The 3rd solution is not to worry about it.... disk space is cheap - are you actually running out?

Shawn Hargreaves:

Fanboy Junior:

So, there is no solution to this problem :-( 

Sure there is.

"If you care about texture sizes, you should make sure your processor properties are set to use DXT compression."

If you want you can then use EasyZip to compress your data even further, but switching to DXT format is the easiest place to start.

Nice, I will take a look at the DXT format! 
 
After you posted here I googled seeking this DXT creator and find some tools from ATI and Nvidia, well, if the result excite me, I will be glad to use that kind of file in my game  :-) 
 
Thanks