The Call of Duty-IDE

The Call of Duty-IDE is an open-source project hosted on GitHub. To get started, clone the repository and install the Python runtime using the command python -m pip install -r requirements.txt. The project requires Python 3.10 or higher.

The software uses an optional AI assistance feature, which asynchronously loads models using the current textured renderer. If GPU rendering is unavailable, software fallback is used. An alternative path with native Qt OpenGL rendering is available by setting the environment variable PYLERIUM_NATIVE_GL=1.

There are three main command-line tools available: loadout-menu.py, orchestration-menu.py, and test_orchestration.py. The loadout-menu.py tool provides an original loadout menu with asset support, while orchestration-menu.py serves as a separate local runner and orchestration workspace. test_orchestration.py checks offscreen integration.

The runner shares many features with the loadout-menu.py tool, such as background, typography, selection cards, wireframe canvas, and preview panel. However, it has a separate functional interface and uses the BO6-inspired theme for lobby, loadouts, operators, maps, missions, arsenal, workshop, console, barracks, assets, settings, and plugins pages. The runner does not pixel-for-pixel recreate every game screen and does not include any proprietary game assets.

The assets manifest is defined in the assets/manifest.json file, which maps project IDs, stable keys, and loadout keys to files within the assets/ directory. If any assets are missing, the system falls back to procedural artwork. The example assets include original SVG drawings and a single OBJ inspection prop.

Icons are centered within the card's image zone, preserving aspect ratio and keeping labels clear. The ASSETS.icon() function returns a centered, transparent, DPI-aware QIcon. Backgrounds fill their area with cropping, maintaining the original gradient, vignette, orange lighting, and animated atmospheric overlays above the background.

OBJ models support vertices, polygon faces, negative indices, UV coordinates, and line segments. They are automatically centered and fitted, with rotation values in degrees. When importing models, OBJ files, .mtl files, and texture subfolders must be kept together, with the importer copying referenced dependencies while preserving their relative paths. Any missing or external resources are reported.

Existing models imported by the older single-file importer need to be re-imported from their original folder to recover omitted materials and textures. Models and textures load on background workers, separate from card paint events. The OBJ, GLB, glTF, STL, PLY, and OFF formats are supported, with external material and texture dependencies requiring separate importation alongside their source model.

Static geometry is supported, but skeletal animation is not evaluated. GPU shading supports discovered materials and maps, while a software fallback preserves textured model inspection. If resources are missing or unsupported content is encountered, an explanation is provided.

The Assets studio allows users to select project and execution-slot assignments, filter targets, preview images and models, adjust rotation, assign texture overrides, and remove artwork. The Reload Asset Manifest command should be used after external changes. Each loadout card displays static image/model artwork, with an inspection panel supporting orbit, zoom, fit, materials/wireframe, and expanded inspection.

The runner's Assets page allows users to import files and update the manifest. In Python, loadout data can be managed using the asset_helper.py module. To import an icon, model, or texture, use the ASSETS.import_file() function with the appropriate file path and variable name. ASSETS.set_item() can then be used to assign the imported icon, model, rotation, or texture to a specific project. The background can be set using ASSETS.import_file() and ASSETS.set_background().