.sw.vtx files are related to software rendering, a feature that has been deprecated in every modern source engine game. Maybe some beta branch or pre-2006 branch of the engine will need them but otherwise might as well add the option to skip packing them to reduce file size a bit.
EDIT: I should clarify that no official released valve-made source engine game requires the .sw.vtx files for any sort of legacy support reasons or something either, they are completely useless space-wasting files (although pretty minor, the average uncompressed map will probably only see single digit MB differences). Only reason I added it as a parameter and not just omitting them entirely incase there's some odd edge-case with an ancient/beta engine branch. That being said it would probably make more sense to invert this and make it -swvtx instead.
Team Fortress 2's VScript update added support for packed upgrade files. This simply looks for "SetCustomUpgradesFile" in the entity I/O.
.sw.vtx files are related to software rendering, a feature that has been deprecated in every modern source engine game. Maybe some beta branch or pre-2006 branch of the engine will need them but otherwise might as well add the option to skip packing them to reduce file size a bit.
EDIT: I should clarify that no official released valve-made source engine game requires the .sw.vtx files for any sort of legacy support reasons or something either, they are completely useless space-wasting files (although pretty minor, the average uncompressed map will probably only see single digit MB differences). Only reason I added it as a parameter and not just omitting them entirely incase there's some odd edge-case with an ancient/beta engine branch. That being said it would probably make more sense to invert this and make it -swvtx instead.