Pre Civ

Pre Civ: What It Actually Does and How to Stop Wasting Time On It

Pre Civ is a preprocessing pipeline for Civilization VI modding and asset work. It sits between your raw model files, textures, and the game engine, converting everything into the formats the game actually expects at runtime. Without it, you are either stuck trying to import assets manually or dealing with broken textures, missing materials, and path errors that take hours to track down. The tool itself is mostly a set of batch converters with a configurator that reads your project structure and spits out a compiled output folder. Download the latest build from the official forum thread on CivFanatics. Put it in a directory that does not have spaces in the path. This is not a suggestion. I spent two days debugging what turned out to be a PowerShell encoding issue caused by a space in C:\Program Files\Pre Civ, and the fix was moving it to C:\tools\pre-civ. Once installed, open the config editor. You will see a tree of input directories. Map your source folder structure here — models, textures, UI elements, sound files. Each category has a different set of conversion flags. Leave them on defaults until you understand what each one does. Run a dry first pass. The tool has a preview mode that logs what it would convert without writing anything. Check the log output for errors before running the actual conversion. Missing texture formats, unsupported polygon counts, and mismatched material paths all show up cleanly in the log. If the dry run throws zero errors, switch to production mode and run it again.

What Happens Under the Hood

Pre Civ does four things in sequence. It normalizes file paths against the Civilization VI asset registry. It resamples textures to the target resolution tiers the engine uses — 2K, 1K, 512, 256 — based on the material type. It converts meshes through a glTF to the proprietary binary format that the engine reads. Finally it packages everything into the .cip file structure that the game loads at startup. The pipeline is deterministic. Run the same inputs twice and you get byte-identical output. That matters when you are testing changes. The thing nobody mentions upfront is that the tool does not validate PBR material correctness. It will happily convert a roughness map into a diffuse map if your config is mislabeled, and you will not know until you are playtesting in-game and wondering why your marble floor looks like it is made of wet plastic. I learned this the hard way when a client sent me a Unity export where the metallic and roughness channels were swapped. The converter accepted it. The game rendered the entire building suite as chrome. The fix was a simple node reassignment in Substance Painter before re-exporting. Going back and rewriting the material graph after the conversion is slow. Do it before you run Pre Civ.

Common Pitfalls and Edge Cases

There is a well-known issue with animated meshes that have joint names exceeding 32 characters. The converter truncates them silently, and the skeleton breaks at runtime. I hit this with a custom unit animation rig where every bone was suffixed with descriptive labels like weapon_l_finger_03_ik_joint. The solution was a bulk rename script that ran before the conversion pass. It strips the suffixes down to the standard weapon_l_finger_03 format that the engine expects. You can write this yourself or find community scripts in the tools subforum. Another issue is the texture compression choice. Pre Civ defaults to BC7 for most maps. That is fine for PC. If you are building for console or need to stay within VRAM budgets, switch to BC3 for normal maps and BC1 for diffuse where color fidelity is less critical. The quality difference is negligible on a monitor unless you are zooming into a texture at 400 percent. It can cut your texture memory footprint by roughly 40 percent on large projects. UI elements have their own gotcha. Pre Civ will convert image files, but it does not handle atlas packing automatically. If you have fifty individual button states and expect the tool to merge them into a single sheet, it will not. You need to prepare your atlases separately using a tool like TexturePacker and then point Pre Civ at the atlas file instead of the individual elements. Forcing it to process the individual files creates duplicate entries in the atlas registry and the game skips them silently, leaving empty UI slots at runtime.

When Pre Civ Fails Completely

There are scenarios where this tool is the wrong choice. If you are working with high-poly scanned geometry from photogrammetry — models above 500K triangles per mesh — the converter will choke or produce terrible LOD results. Pre Civ is designed for artist-authored game assets, not raw scan data. In those cases, you need to decimate and retopo in Blender first, then feed the cleaned meshes into the pipeline. Trying to run raw scan data through it directly just wastes time and produces unusable output. Similarly, if your project relies heavily on shader network nodes that use expressions not supported by the converter — complex procedural noise, custom GLSL passes — the material will bake to a flat color or go fully transparent. The tool only supports a subset of the shader language that Civilization VI actually uses. Check the compatibility list in the documentation before committing a material-heavy workflow to it.

Performance and Workflow Tips

The tool runs single-threaded by default. If you have a multi-core machine, enable the parallel conversion flag in the advanced settings. It roughly halves conversion time on projects with more than a thousand assets. I went from about forty minutes on a typical city-state asset pack down to eighteen minutes after enabling it. The trade-off is higher RAM usage during the run. Keep an eye on your available memory. If you are running below four gigabytes free, disable the parallel flag and let it process sequentially to avoid crashes. Keep your source folder structure consistent. The tool relies on path conventions to determine how to process files. Change the folder names mid-project and it will silently misroute files into the wrong conversion pipeline. I once renamed a Textures folder to Assets_Tex after running the initial config, and the next build had no textures at all because the converter was looking in the old location. It took me an hour to realize the path was stale. The log showed the missing files but I was too focused on the conversion output to notice. If you are maintaining a long-term mod, version your Pre Civ output folder alongside your source. The tool is fast enough that you can regenerate on every commit. That way you can always roll back to a known-good build if a later change breaks something downstream.

The Bottom Line

Pre Civ is functional but unforgiving. It does exactly what it says and nothing more. The configuration matters more than the tool itself. Get your paths right, validate your materials before conversion, handle joint naming and atlas packing manually, and you will save yourself most of the headaches that come with it. It is not a magic import button. It is a batch processor that rewards careful preparation and punishes guesswork.