Disclaimer: I'm going to try and explain things to the best of my ability; however this is a pretty loaded topic. Things might get a little complicated at times, but please bear with me.
Alright, so first things first; this is not Killing Floor 1 and because of that you can't expect the map sizes to remain as small as they did in KF1. Now I'm sure someone in the room is going to tell me "
but, but"¦ there are loads of maps out for KF2 that are 50MB or lower, so why are yours so big?â€
Short answer *
TEXTURES*
Long answer; UE3 uses multiple texture maps to make up the in game materials that you see plastered on geometry. In KF2's case the game primarily uses three to four texture maps to make up a material;
Diffuse,
Normal,
Specular, and on occasion
Emissive. UE3 can however support many more than the four I just listed off.
In comparison KF1 primarily uses just a
Diffuse with the odd
Specular located in the "
Alpha Channel", and on occasion a
Bump map might be thrown in.
This however is only just the tip of the iceberg, there are many other factors that contribute to the increase in file size from Killing Floor 1 to Killing Floor 2.
Next up on the list is
Texture Resolution. On average KF2 uses textures that are twice the resolution of KF1, however doubling a textures resolution does not mean the size doubles as well. More often than not the images file size will increase exponentially this increase can be anywhere from
3x to
5x the original size, this is due to how texture compression algorithms operate on pixel information as well as how complicated that information is.
For the sake of simplicity I won't go into any specifics on the different types of compression methods out there, however I will provide some links at the bottom for further reading.
There are a few other factors that also contribute to the file size increase such as, but not limited to; the different compression methods used by UE3 Vs. UE2 and total amount of Unique non-referenced textures used in a given level.
To put it simply the overall level quality and complexity has drastically increased from KF1 to KF2, so an increase in file size is not only expected, but necessary as well.
Now that you understand why my maps are as big as they are I'm sure many of you are asking. "
Why are other maps so small?" There's actually a very simple answer to that, and it all has to do with referencing textures & assets already created and loaded into the game by Tripwire. If all you do when you create a map is reuse the assets that Tripwire has created then your total file size will remain quite small, since at that point all you're left with is geometry, light maps, and level data/scripting. All of that information can easily be fit into 20MB file.
In my maps however I will seldom if ever reuse any of Tripwire's assets from the base game, thus the much larger file size.
A prime example of this can be found in your games map folder. If you take a look at the size of all the default maps they average out to around 100MB~ each.
HOWEVER "Black Forest" is just over 500MB, this is because Black Forest uses primarily unique textures that aren't found in other maps and it's also a perfect example of what I just talked about.
So that basically covers why the vast majority of custom maps currently available for KF2 are so small.
A personal note from Me.
I understand that my maps are large when it comes to file size, but that doesn't mean that I'm not trying to compress things as much as possible.
HOWEVER until Tripwire enables full support for custom Master materials and some sort of compression for map packages passed through a redirect there is only so much I can do.
Also for any of you who are knowledgeable about common types of texture compression used in games I have tried to use "DDS" images with BC1, BC3, and BC3n texture compression (formally known as DXT1, DXT5, and DXT5_NM). However the UDK won't accept them since it already applies this type of compression on texture import. Normally this wouldn't be a problem, but I have noticed that when applying the same type of compression in engine as I do with the NVIDIA texture tools plugin for Photoshop I experience considerably better results in Photoshop than I do when using the UDK. I can only assume this is because the compression algorithms being used by Epic and the ones being used by NVIDIA are slightly different. I believe that this might very well be the case, especially after reading NVIDIA's documentation which states that the "
Direct Draw Surface" (DDS) format in particular can support numerous types of compression.
Hopefully all of you who read this found it useful, and now you have a better understanding of where things are at in the world of Killing Floor 2 custom maps.
Links for additional reading:
DDS Compression settings for export (Great tutorial by "DieByZer0" on the CryEngine forums)
Garage Games Texture compression Guide (Very good read)
Normal Map Compression
High Quality DXT Compression
Programming Guide for DDS
Reference for DDS
Compressed Texture Resources (Direct3D 9)
Block Compression (Direct3D 10)
