DirectXTex VS Cryengine-Converter

Optimized Vanilla Textures were optimized for PC and then ported to console. They were optimized using an 'optimizer' for Skyrim, which was not updated for the textures FO4 has. It did add mipmaps for the textures that were supposedly missing some and shrank the resolution; however, seeing as the Creation Kit uses Microsoft's own DDS compression program that adds mipmaps automatically, you're literally just re-adding vanilla textures that have been decompressed and then recompressed with extra loss on the visuals and taking up space. Also, specular maps must be compressed with the Photoshop Intel plugin in order to compress them properly or a program that will allow you to have the red and green channels saved in BC5U format (which is a normal map compression and flipped). GIMP does not do it correctly and I'm very doubtful the program that was used to shrink things did either since it was not designed for FO4's specularity.

DirectXTex

The images are in a split DDS format. To convert them to e.g. PNG files, you first have to concat the files and then use a tool such as texconv.

Yep, the images used for each part of the minigame (a couple variations each of lock background, pick, pins, and springs) are stored as .dds files, DXT1 format. You can convert another image format to this type of texture-- I used texconv. Overwriting the default textures with your new files will replace the assets ingame.

However I've found that MS TexConv from the DirectXTex package is the best way for loosing less quality, so I save my textures as lossless PNGs and use TexConv with my own wrapper then.

You can use texdiag to see information about a texture.

I know only Nvidia texture tools exporter but it's not in masse sorry My suggestion is to create a python script that uses texconv.exe for every file in a directory, pretty easy to get

xLODGen/DynDOLOD/TexGen uses Texoncv to compress textures.

Not necessary on Xbox. Xbox graphics will not function properly without mipmaps so the developers would have had to run everything through xtexconv for Xbox optimization. See Microsoft Documentation on DirectXTex. Code samples for xtexconv for the curious are located here.

All textures/images are .dds files. I use TexConv.exe to convert them to png files. texconv.exe *.dds -ft png

Here's a tool for extracting assets from Star Citizen. https://github.com/Markemp/Cryengine-Converter

Eventually I found unp4k (Github). This allows you to extract the big 'data.p4k' file. Then you have access to all the model files, though they're in .cgf and .cga formats (cryengine). Just opening these in cryengine wouldn't work. After some research I stumbled upon Cry Engine Converter (Github). This allows you to convert those files into usable files. This was huge for me.

Use unp4k Tools and than Cryengine-Converter.

Cryengine Converter: https://github.com/Markemp/Cryengine-Converter/releases/latest

Models are Cryengine .cgf and .skin files. You can use Markemp/Cryengine-Converter to convert them to Collada (.dae) files, and potentially KhronosGroup/COLLADA2GLTF to convert the Collada files to glTF files afterwards.

A quick Google search turns up this project: https://github.com/Markemp/Cryengine-Converter

Hi everyone. Just want to put out some observations of some work I've done recently getting CIG's new #ivo file format able to be processed with my Cryengine Converter program, and how that should help with load times and performance.

To convert the object 3d assets from .cgf to something like .dae or .obj, you can use CryEngine Converter. For textures, I use the Star Citizen texture converter to convert the split .dds textures to .tif.