greenband

[刀evious]

Well some people hate AI but I'm pretty impressed.  I can now create model groups from some newer cod maps and import them into radiant.  Clowntown was the first try, and i think it looks pretty good but not perfect.  I still need to recreate the player collision and do a lot of manual stuff but I plan on doing several more maps.  here are some screenshots of the next one.  It still needs work, but hot damn.

 

 

 

 

 

 

 

 

 

 

Edited 11 hours ago by 刀evious

[刀evious]

 

 

[MikelMahou]

Hi there!

Nice work 刀evious!1

Can you describe your method with IA to get the files to import to radiant? 

I am doing something close to this, but for Cod Waw, so i would really interested.

Thank you!

Mikel

[Sharpe]

5 hours ago, 刀evious said:

 

 

Nice, are you using astra or fable 5.1 for this?

[MikelMahou]

Hi there!

I am asking about your method because i tried and actually use this one:

 

1. Extracting the Map Geometry & Models

Modern Call of Duty games pack assets inside encrypted database files (.fp / CASC / Fastfiles). To extract them, developers use low-level memory dumping and ripping tools:

• Cordisep & Saluki: Used heavily for modern era titles (like Warzone and newer Black Ops games) to export the raw .cast model files and materials. 

• Husky / C2M: Memory-ripping tools designed to extract BSP (Binary Space Partitioning) data directly from a map while the game is running. They output a raw .obj 3D file of the environment.

• Greyhound / Wraith Archon: Standard asset extractors used to pull individual static xmodels, weapons, and textures from the engine cache.

2. Processing and Reconstruction (Blender or Maya)

When you rip a map using tools like Husky, the resulting mesh consists of un-welded triangles and missing chunks. 

• You must import the .obj or .cast files into a 3D modeling program like Blender or Autodesk Maya.

• You will need to manually fix topology, separate the scene into modular Model Groups, and rebuild the textures.

3. Converting to CoD-Readable Formats

Radiant cannot open standard FBX or OBJ files directly. You must convert your cleaned 3D models into formats the older engines recognize:

• For World at War (CoD5): Models must be exported from Maya using the official Activision plugins as .XMODEL_EXPORT files and then compiled into .XMODEL using the Asset Manager (AssetMod / CoD5ModTools).

• For Black Ops 3: You can use the Asset Property Editor (APE) within the Black Ops 3 Mod Tools to import and process the meshes.

• To convert the actual layout brush data into something Radiant can open, developers often use community scripts like OBJ-to-CoD-Radiant-Map-File to generate a readable .map file.

Summary of the Reality

Porting an entire modern map backward is incredibly time-consuming. Because newer engines utilize advanced physics, massive asset budgets, and complex material layers that older engines like World at War cannot handle, the map geometry will usually function only as a visual reference template. You will ultimately have to manually rebuild most of the map layout directly inside CoD Radiant using native geometry blocks (brushes) and terrain patches. 

 

So, i am wondering if you have found a way better to do all this.

 

Thank you!

 

Mikel

[刀evious]

2 hours ago, MikelMahou said:

Hi there!

I am asking about your method because i tried and actually use this one:

 

1. Extracting the Map Geometry & Models

Modern Call of Duty games pack assets inside encrypted database files (.fp / CASC / Fastfiles). To extract them, developers use low-level memory dumping and ripping tools:

• Cordisep & Saluki: Used heavily for modern era titles (like Warzone and newer Black Ops games) to export the raw .cast model files and materials. 

• Husky / C2M: Memory-ripping tools designed to extract BSP (Binary Space Partitioning) data directly from a map while the game is running. They output a raw .obj 3D file of the environment.

• Greyhound / Wraith Archon: Standard asset extractors used to pull individual static xmodels, weapons, and textures from the engine cache.

 

2. Processing and Reconstruction (Blender or Maya)

When you rip a map using tools like Husky, the resulting mesh consists of un-welded triangles and missing chunks. 

• You must import the .obj or .cast files into a 3D modeling program like Blender or Autodesk Maya.

• You will need to manually fix topology, separate the scene into modular Model Groups, and rebuild the textures.

 

3. Converting to CoD-Readable Formats

Radiant cannot open standard FBX or OBJ files directly. You must convert your cleaned 3D models into formats the older engines recognize:

• For World at War (CoD5 Models must be exported from Maya using the official Activision plugins as .XMODEL_EXPORT files and then compiled into .XMODEL using the Asset Manager (AssetMod / CoD5ModTools).

• For Black Ops 3: You can use the Asset Property Editor (APE) within the Black Ops 3 Mod Tools to import and process the meshes.

• To convert the actual layout brush data into something Radiant can open, developers often use community scripts like OBJ-to-CoD-Radiant-Map-File to generate a readable .map file.

 

Summary of the Reality

Porting an entire modern map backward is incredibly time-consuming. Because newer engines utilize advanced physics, massive asset budgets, and complex material layers that older engines like World at War cannot handle, the map geometry will usually function only as a visual reference template. You will ultimately have to manually rebuild most of the map layout directly inside CoD Radiant using native geometry blocks (brushes) and terrain patches. 

 

So, i am wondering if you have found a way better to do all this.

 

Thank you!

 

Mikel

You described it pretty much exactly right.

[刀evious]

3 hours ago, Sharpe said:

Nice, are you using astra or fable 5.1 for this?

Been using mostly sol and fable, just got updated to astra tho.