REPRISE EAGLE MAP EDITOR

BUILD 3.4.3 · PROPRIETARY PROJECT EAGLE TECHNOLOGY

PROCEDURAL ENGINE.
RENDERWARE.
FULL PIPELINE.

Presented by the project as the first complete procedural engine for RenderWare focused on game editing and customization: an integrated environment capable of interpreting, generating, reshaping, texturing, validating, testing and applying native content without relying on a fragmented chain of external tools.

Explore architecture → See technical systems

PUBLIC OVERVIEW · INTERNAL IMPLEMENTATION

C# · .NET 8 · WPFDesktop core and application

DFF · TXD · COLNative RenderWare pipeline

IDE · IPL · IMG · gta.datWorld and streaming

.reprise-mapNon-destructive project

TECHNICAL DEFINITION

More than an editor.
An engine inside the workflow.

Reprise Eagle Map Editor is not a Blender extension, an isolated plugin or merely an asset generator. Its core works directly with GTA San Andreas and the RenderWare ecosystem, keeping map context, geometry, materials, textures, collision, streaming, IDs, data files and project state inside the same pipeline.

Scan → index → generate → edit → reconstruct → validate → test → apply.

That complete cycle — from native reading to validated commit — is what defines the project as a procedural production engine rather than a single-purpose procedural tool.

SCANRead the installation and native dependencies without using the game folder as the workspace.

RESOLVEResolve assets, models, textures, collisions, instances and world relationships.

GENERATEGenerate or reshape content procedurally through parameters, spatial rules and constraints.

EDITEdit objects, vertices, faces, materials, UV, textures, collision and properties visually.

VALIDATECheck topology, RenderWare compatibility, IDs, UV, skinning, collision and runtime limits.

PREVIEWBuild an isolated test replica and launch GTA for external validation.

COMMITApply only authorized changes with staging, backup, conflict checking and rollback.

ARCHITECTURE

Separated layers.
One technical context.

The architecture separates scanning, editing, procedural generation, validation, preview and writing so deep operations do not turn the original game installation into the workspace.

Native Scanner & Catalog

Controlled installation scanning, default.dat/gta.dat resolution and indexing of IDE, IPL, IMG, DFF, TXD, COL and water data while preserving asset identity, dependencies and real load order.

World & Spatial Layer

Spatial index and streamed world context for global, per-IPL, layered and regional work while preserving relationships between instances, models, LOD and map data.

Procedural Core

Deterministic spatial generation and transformation layer: parametric presets, roads, mesh composition, automatic collision, character reshaping and other procedural systems tied to the final game format.

Native Asset Editing

Controlled DFF/TXD/COL reading, editing and writing with geometry, materials, UV, prelight, vertex colors, Skin PLG and native fidelity where required.

Validation & Fidelity

Topology, runtime limits, UV integrity, collision, skinning, model identity and structural safety checks before a result is considered applicable.

Project / Cache / Commit

Changes live in the .reprise-map document and working cache. Commit uses staging, fingerprints, conflict verification, backups and transactional rollback.

PROCEDURAL PIPELINE

Procedural without losing
native compatibility.

Procedural generation does not end as a generic mesh. The result must return to the RenderWare ecosystem with valid identity, UV, materials, collision, limits and game references.

SCANRead the installation and native dependencies without using the game folder as the workspace.

RESOLVEResolve assets, models, textures, collisions, instances and world relationships.

GENERATEGenerate or reshape content procedurally through parameters, spatial rules and constraints.

EDITEdit objects, vertices, faces, materials, UV, textures, collision and properties visually.

VALIDATECheck topology, RenderWare compatibility, IDs, UV, skinning, collision and runtime limits.

PREVIEWBuild an isolated test replica and launch GTA for external validation.

COMMITApply only authorized changes with staging, backup, conflict checking and rollback.

TECHNICAL SYSTEMS

An ecosystem for
editing and generation.

The modules below represent public technical capabilities. Implementation details, internal algorithms and source code remain restricted to the team.

Native Streamed World

Full-world or per-IPL loading, spatial indexing and layer/distance/context filtering with detail/LOD, interiors, water and collision relationships.

WORLD

Object & Mesh Workspace

Multi-selection, X/Y/Z transforms, vertex/face editing, join/split, mesh composition, magnetism, snapping, guides, undo/redo and controlled sculpting.

MESH

RenderWare DFF Pipeline

DFF parser/editor/writer with geometry, materials, transforms, vertex colors/prelight, Skin PLG and native-fidelity operations.

DFF

TXD / Texture / UV

TXD dictionary reading/writing, surface painting, overlays, image projection, UV editing, fidelity protection and texture operations integrated with geometry.

TXD

COL Modeler

Collision reading/writing, vertex/face/box/sphere/surface editing and simplified collision generation from visual geometry.

COL

Procedural Construction

Parametric library and spatial generation for reusable structures, architectural components and procedural-road authoring data integrated into the project.

PROC

Character / Ped Systems

DFF/TXD validation, RenderWare morphing, region sculpting, skin topology binding, procedural wardrobe, animation inspection, NPC generation, atlases, hair and reference-reconstruction pipelines.

PED

Reference Reconstruction

Deterministic pipeline for reference analysis, landmarks, silhouette, fitting, facial/body reconstruction, UV refit, texture baking and structural validation without requiring generative AI for the procedural core.

PFSR

Vehicle & Handling Workflow

Part composition and repair, embedded collision, DFF validation, handling.cfg editing and vehicle-specific preview workflows.

VEH

Weapons & HUD Assets

Weapon configuration, FX parameters, HUD texture editing and external-model validation before integration.

WPN

GXT Text Pipeline

GTA San Andreas GXT reading, editing, merging and writing, including tables, TKEY/TDAT, hashes and 8/16-bit variants.

GXT

External 3D Conversion

External mesh import/conversion including Collada, glTF/GLB and other importer-supported workflows with axis, scale, polygon and model-identity handling.

GTA V / CodeWalker Bridge

Resource and placement/archetype representations used by conversion workflows, reorganized into the editor asset pipeline.

BRIDGE

Project, Preview & Rollback

Persistent projects, incremental cache, fingerprints, isolated preview, compatibility testing, commit planning and transactional restore.

SAFE

FORMATS & DATA

RenderWare and world data
treated as one system.

The tool does not treat each file as an island. Visual assets, map data, streaming archives and configuration are related inside the same project.

RenderWareDFF, TXD, COL, materials, UV, vertex colors, Skin PLG, bounds and collision.

MapIDE, IPL, instances, LOD, coordinates, categories, water and spatial index.

Game filesIMG v2, default.dat, gta.dat, handling.cfg, GXT and supported auxiliary data.

ImportExternal meshes, textures, Collada, glTF/GLB and conversion-specific bridges.

Project.reprise-map documents, embedded assets, patches, fingerprints and procedural state.

TestingIsolated cache, preview bootstrap, compatibility validation and transactional commit.

PRODUCTION SAFETY

Deep editing
without using the original as workspace.

The scanner and catalog understand the installation. The project and cache hold modifications. Writing back to the installation is a separate, validated stage.

Read-oriented scanning and inspection before modification.

Project/cache workspace instead of direct work inside the original installation.

External preview in a prepared test environment.

Fingerprints and expected-file-state verification.

Staging and backups before commit operations.

Transactional rollback when an operation cannot complete safely.

ADVANTAGES

Less conversion.
More context.

The gain is not only automating one task, but keeping generation, editing, validation and integration inside the same technical context.

Integrated engine, not an extension

The procedural engine lives inside the editor workflow and produces content directly for a pipeline that understands RenderWare and the game world.

Deterministic procedural core

Rules, parameters and constraints can generate repeatable results without making generative AI a required dependency of the core.

End-to-end native editing

Map, DFF, TXD, COL, UV, materials, characters, vehicles and related data can be handled without losing asset context.

Less manual import/export

Reduces the chain of opening tool A, exporting, converting, fixing, importing into tool B and rebuilding references manually.

Compatibility as a requirement

A procedural result is not ready only because it looks right; format and runtime validation are part of the pipeline.

Scalable production

Presets, procedural generation, multi-selection, construction tools and automation reduce repetitive operations in large expansions.

Test before commit

Content can be prepared and tested before being written to the target installation.

Shared technology foundation

The same architecture serves as a base for internal tools and pipelines connected to Project Eagle and the Reprise ecosystem.

PROPRIETARY TECHNOLOGY

The technology is visible.
Access is not public.

This page exists to show the public what the team has built and which technical problems the tool solves. The executable, source code, internal documentation, proprietary algorithms, production presets and development packages are not publicly distributed.

TEAM-ONLY DOWNLOAD · PROJECT EAGLE

Access is provided only to authorized Project Eagle team members. There is no public download link, community build or evaluation package.

Visit Project Eagle →