MapView2-MAP2_241201(Wndows).7z

MapView2 (MAP2 version)

2024 dec 01

MapView .exe
McdView .exe 4.2.1.0
PckView .exe 4.3.2.0
XCom .dll
DSShared .dll
YamlDotNet.dll 0.0.1.0 (c) Antoine Aubry and contributors

ConfigConverter .exe 2.2.2.2
RulesetConverter.exe 1.3.0.2

Modified version of MapView2 by KevL -which is a major rewrite of the original MapView by Ben Ratzlaff aka Daishiva (and others)
It has not been exhaustivaly tested. Use at your own discrection.
It adds suppport for a new MAP2 format for map files, which stores info in 16 bits instead of 8 bits, virtually overcoming the limit of 253 different tiles for any maplock/terrain.

MapView2 is a map and routes editor for XCOM UFO/TFTD. It nominally requires the
original UFO/TFTD resources, such as PCK/TAB/MCD files. It can edit pre-existing
MAP/MAP2 and RMP files, and create new ones from scratch.

In case of two MAP/MAP2 files with the same name existing under a MAP folder, the MAP2 one WILL BE IGNORED.
Removed checks for MCD tilesets exceeding max. byte-value (253) when working with MAP2 format.
Added checks to avoid exporting a MAP2 file with IDtiles exceeding 253 to MAP format.

PckView is included as a spriteset editor and a very simple sprite editor - it
can be used to create/edit/save PCK+TAB files.

McdView is included as a partset editor - it can be used to create/edit/save MCD
files.

REQUIREMENTS:
32/64-bit Windows OS, .NET 4.8, ~2 MB disk installation, XCOM:UFO and/or
XCOM:TFTD Resources

MapView2-MAP2 contains 2 converter utilities:

1. RulesetConverter is a utility that converts data from an OxC/e ruleset file
   to a YAML file - MapTilesets.tpl - which contains data that can be used by
   MapView2.

See RulesetConverter.txt

2. ConfigConverter is included that might/should be able to convert a
   MapEdit.dat file, which is used by MapView1, into a MapView2 configuration file
   for tilesets. MapView2 uses YAML to save most if not all settings; MapView1 uses
   a custom parser.

See ConfigConverter.txt

Not all MapEdit.dat files will convert gracefully. The design of how tilesets
load, store, and access their configurations has changed substantially. Instead
of loading/storing tilesets under a group and subgroup, the group and category
of a tileset is now stored within the tileset definition itself. A default
resource folder is assigned upon installation, for either or both UFO and TFTD,
which is typically the parent-path of the MAPS, ROUTES, and TERRAIN folders of
your stock XCOM installation(s). However, if you prefer to use a scratch
directory for editing tilesets, tilesets can be created (or manually copied)
into an arbitrary folder of your choice, as long as it is a parent folder that
has the subfolders MAPS and ROUTES for the .MAP and .RMP files respectively.

That would then become a tileset's "basepath". See the CHM helpfile's
Configuration page for further details, as well as the header doc in
MapTilesets.yml in the /settings subfolder (created during first run).