Creating New Campaign Map in Rome Remastered

The underlying map structure in Total War: Rome Remastered is exactly the same as for the original game and can still be changed via text file and tga image alterations, however, the visual element of the campaign map is now provided by a separate 3D mesh and textures.

• For differences between Remastered files and RTW see File Differences - Rome Remastered
• For detail on changes needed to port existing maps see Porting a Mod to Rome Remastered, Mapping/Campaign Differences

Map Structure

Functional Map

The Rome Remastered map system uses the old RTW base map_*.tga and text file system to generate the functional map, this original system still controls:

• Coordinates of settlements and ports and starting position of characters and agents
• Region boundaries
• Which areas are sea, accessible land, or blocked land (deep forest/mountains)
• Locations of features, such as cliffs, volcanos and rivers, so far as they effect events and movement on the map.
• Heights, ground_types and climates as used to generate battle-maps at each coordinate (modified by the geography.db).

Visible 3D Campaign Map

The visible 3D campaign map is created separately and is NOT automatically generated or changed by changing the base map files, it has no effect on the battle-maps generated from a battle on the campaign map. The 3D campaign map comprises:

• Cas mesh pieces and textures
• Heightmap bin files generated from the mesh pieces (used to set heights for display of cas models)
• Cas models for trees, settlements and resources (as in original RTW)
• Cas model and textures for the frame
• Cas model for the coastline (uses the surf texture and has a wave motion applied)
• Cas model for the rivers (has a moving 'water' texture applied)

It is possible to load a functional map with a non-matched 3D map, however, this will be confusing to the player, and too large an area of additional map without the appropriate heightmap bins generated from the mesh appears to cause an errorless CTD on loading.

2D map overview

Additionally, there is a 2D map overview section, which is displayed with the map fitted to screen size, the base images for it are the feral_map tga files in the campaign folder. The game generates overlays for this map view based on the game state and the functional map (e.g. boundaries are from map_regions.tga)

Functional Map Components

Any base map that loads under RTW should be capable of loading under RR including using the map.rwm from RTW. For general advice on making a Rome Total War map see the Mapping Index.

The files involved are basically the same as for RTW:

• In data/world/maps/base:
  • descr_terrain.txt - must include width and height of map_regions.tga
  • descr_regions.txt
  • descr_disasters.txt - can be blank but leave comments in to avoid 0kb file breaking filelist manifest
  • map_climates.tga - 2 x map_regions size +1
  • map_FE.tga - variable size
  • map_features.tga - map_regions size
  • map_ground_types.tga - 2 x map_regions size +1
  • map_heights.hgt - not required but see notes below
  • map_heights.tga - 2 x map_regions size +1
  • map_regions.tga - sets the size for other files
  • map_roughness.tga - 2 x map_regions size - required but doesn't appear to be used
  • map_trade_routes.tga - map_regions size - required but doesn't appear to be used
  • water_surface.tga - 256 x 256 - does not appear to be used in Remastered
  • map.rwm - generated by the game if a map is loaded that does not have one

• In data/world/campaign/campaign_name:
  • descr_events.txt - can be blank but leave comments in to avoid 0kb file breaking filelist manifest
  • descr_mercenaries.txt
  • descr_strat.txt - (a version of this file is also placed in data\original_overrides\resource_quantity\world\maps\campaign\imperial_campaign and is used if the user toggles resource setting to original)
  • descr_win_conditions.txt
  • feral_radar_map.tga and feral_radar_map_winter.tga - 1024 x 624
  • description files and leader pictures

For provincial campaigns, or if desired to have different campaign map to custom battle maps you can copy the base folder files into the campaign folder.

• In data/text
  • campaign_name_regions_and_settlement_names.txt - alternate language versions of this file will be required if different region/settlement names are used in the mod versus vanilla campaign

Differences from RTW

descr_strat.txt

The default descr_strat.txt used for 'remastered' settings has a quantity value specified for each resource, e.g.

 resource	marble,         3,         56,   62

which would give you one visible model but 3x the resource value to a merchant. This value is before the x/y coordinates so you need to add 1, here if you only want a single resource.

descr_win_conditions.txt

For hold_regions condition, the Settlement name must be used NOT the Region Name

map_heights.hgt

This is the same as in RTW, in case you've forgotten, you don't need to use a .hgt file the game will generate a map.rwm from just map_heights.tga, but the .hgt file can provided finer detail. However, if your map is the same size as the vanilla map in data/world/maps/base - then you either need your own .hgt file, or you will have to delete the base games' .hgt file - otherwise the game will just use that information instead of your map_heights.tga

3D Mesh Components

Main Mesh

Mesh cas files

• data/terrain/campaign/pieces/ - cas format (will open with IWTW latest version .cas to .dae)

The mesh is formed from these pieces joined together, the pieces should be rectangular and all at the same size. These mesh pieces are not automatically generated by the game so will not correspond with any changes made to the mapping .tga files.

Currently, RTW/BI seems to require a minimum of 104x files listed in descr_map_tiles.txt and also 13 tiles width in order for the heightmap bin files to work properly

Heightmap bins

• data/terrain/campaign/heightmap/ - bin files for functioning heights generated by the game from each of the pieces

The game generates .bin files based on the height information in the mesh piece .cas files. The data in the .bin files is for height points only no x,y coordinates are given. This data is used to set the height of settlement, tree and resource models on the campaign map, and to set the 'ground level' that armies and agents stand on.

Using a data\terrain\campaign\descr_map_tiles.txt file with differently named .cas and .bin files requested than in the original game will trigger the game to write new .bin files, if these files don't already exist in the mod-folder they will be written in:

data\terrain\campaign\heightmap

That's the main game data folder not the mod-folder, cut and paste them from there to your mod-folder! Cut, because if they overwrote your original game files, you will need to let the vanilla game recreate them based on the correct map.

Ideally, name your new piece .cas files differently from the vanilla ones to avoid any accidental overwriting.

Text File

• data/terrain/campaign/descr_map_tiles.txt - text file lists all the cas pieces and which summer/winter textures they use and which heightmap .bin file they use.

Textures

• data/terrain/campaign/textures/ - colour and normal textures for the terrain sections, the cas pieces use conventional uv mapping so although the existing textures are mapped as though projected horizontally, you can alter this. All the land textures with the exception of the farming overlay need to be 'painted' onto each pieces' texture.

Coastline

• data/terrain/campaign/coastline/coastline.cas - model of the surface
• data/terrain/campaign/descr_map_coastlines.txt - text file which lists the above model

Gives the surface for the waves/surf effect near the shoreline.

Rivers

• data/terrain/aerial_map/river_mesh.cas - the river model - will only be visible if above the level of the terrain mesh - unfortunately as the game still generates region boundaries with wiggles/bend variety automatically, and doesn't generate the mesh for the rivers, it is currently difficult if not impossible to get rivers and boundaries to align exactly

These do not automatically appear where the map_features.tga shows them, instead they use a model surface similar to the coastline in:

3D Frame

• data/terrain/campaign/frame/ - contains a cas model and textures for the 3d frame that hides the edges of the map

2D View Components

Large 2D Map

When you scroll into the campaign map or use the tab button, the game display switches to a 2d view with various overlays, the overlays are generated by the game but you will need a large base map underlying them showing your new map outline, the components are:

• data\world\maps\campaign\imperial_campaign\feral_map.tga.dds - 4080 x 2496 size - seems to work best if completely 'alpha'd out' with a black alpha layer!
• data\world\maps\campaign\imperial_campaign\feral_map_winter.tga.dds - winter version as above

NB: These textures need to be placed in mod-folder\data\world\maps\campaign\imperial_campaign\ for BI mods, they are not read from the \barbarian_invasion\ campaign folder.

The 'frame' seen in this view does not use the same textures as your model frame, this view uses parts of the textures in

• data/ui/culture/shared_new_extruded_0 and _1.tga

Mini Map

The mini map visible on the 3D View screen is based on:

• data\world\maps\campaign\imperial_campaign\feral_radar_map.tga - 1020 x 624 size
• data\world\maps\campaign\imperial_campaign\feral_radar_map_winter.tga - winter version as above