OpenXcom Forum
Modding => Tools => Topic started by: misterx on January 22, 2020, 03:44:30 pm
-
So as title says, what are the programs to build and modify maps for opexcom? luke83 user hosts on his site "DaiShivas Mapview" (http://openxcommods.weebly.com/daishivas-mapview.html#) and kevL has made a mapview 2 version (https://github.com/kevL/OpenXCOM.Tools/blob/master/Distribution/README.md), but are there are other alternatives?
-
how many programs do you want?
one is enough, two is already too much
-
how many programs do you want?
one is enough, two is already too much
just for enqury, as Freddie said "the bigger the better" (https://www.youtube.com/watch?v=U4hClju4ajY). Which one do you guys recommend to use?
-
just for enqury, as Freddie said "the bigger the better" (https://www.youtube.com/watch?v=U4hClju4ajY). Which one do you guys recommend to use?
Some map making veterans as Luke83 prefer MapView2.
While other veterans as Solarius Scorch and Hobbes prefer the old MapView1.
IMHO, MV2 is easier and better to understand, also is in active development by KevL. I tried to use MV1 some time ago and I still prefer the newer version.
Enviado desde mi LG-M400 mediante Tapatalk
-
Mv1 and Mv2 should not be seen as in competition. This is not simply an opinion.*
Mv2 IS Mv1. Daishiva gave his blessing (we discussed things a bit) and he Liked the repo. To me, it's as if he was glad someone came along to look after his child and help it grow up, when life took him in a different direction.
I took the most advanced codebase of Mv1 i could find, and appended the "2" only when the format of the metadata changed to YAML (making said metadata no longer compatible w/ older versions).
The only reason that some persons still use Mv1, as far as I can see, is because they have HUGE (thousands) of mapblocks and are therefore understandably reluctant to upgrade to the new metadata format. There are, however, 2 standalone apps packaged w/ Mv2 [RulesetConverter and ConfigConverter] that can do such a conversion - not sure how well they work though. RulesetConverter is recommended since it uses the YAML input of an OxC ruleset, which is more likely to provide correct input than the paths files of Mv1. A user might have to make a few trial & error runthroughs to get things right, though.
And, whether it's noticeable at a glance or not, Mv2 is a massively advanced/enhanced version of Mv.
* or if it is it's a fairly sophisticated one
anyway, carry on. I get food on my plate no matter which one is used ...
-
I did try to convert my MV1 stuff to MV2, but it failed. It worked for Finnik, but the two of us couldn't find what could be wrong on my end. Ultimately I gave up.
I would appreciate having a detailed tutorial, maybe I would be able to find the issue then. I would like to update, I really dig the new features.
-
What are the differences between those programs, i mean, explained to those that are laymen?
-
I did try to convert my MV1 stuff to MV2, but it failed. It worked for Finnik, but the two of us couldn't find what could be wrong on my end. Ultimately I gave up.
I would appreciate having a detailed tutorial, maybe I would be able to find the issue then. I would like to update, I really dig the new features.
... let's try to get it working, Solarius
can you point me to an OxC ruleset that has your terrains defined? I'd like to try running it through the RulesetConverter ...
it doesn't have to be all your terrains, but a ruleset with a substantial subset could be a good start,
-
What are the differences between those programs, i mean, explained to those that are laymen?
just fixes/enhancements
like when zoomed in on a Map, and the scrollbars are visible, you can hold down the rightmousebutton and pan the map around
route files can be exported and used as templates
to select a tile in TopView, the tile-lozenge has to be clicked on (in Mv1 clicking on the background outside the map-lozenge selects the tile closest to the click-point)
various test functions, warn about out of bounds routenodes, warn if MCD record count has been exceeded ...
too many to document. Like i said Mv2 IS Mv1 (an upgraded version and it uses a different file format to store tileset data)
-
... let's try to get it working, Solarius
can you point me to an OxC ruleset that has your terrains defined? I'd like to try running it through the RulesetConverter ...
it doesn't have to be all your terrains, but a ruleset with a substantial subset could be a good start,
You could just use the one from SupSupers OpenXcom Github: https://github.com/OpenXcom/OpenXcom/blob/master/bin/standard/xcom1/terrains.rul
If the ruleset converter works correctly that would be really nice.
-
You could just use the one from SupSupers OpenXcom Github: https://github.com/OpenXcom/OpenXcom/blob/master/bin/standard/xcom1/terrains.rul
If the ruleset converter works correctly that would be really nice.
The converters work for me (and i've tested them against other OxC rulesets and Mv1 configs). But how things should turn out depends on how your Mv2 Configurator (on install and under the Edit menu) is set
-
... let's try to get it working, Solarius
can you point me to an OxC ruleset that has your terrains defined? I'd like to try running it through the RulesetConverter ...
it doesn't have to be all your terrains, but a ruleset with a substantial subset could be a good start,
Thanks man, I really appreciate it.
I have no idea what you mean by a ruleset (MapView doesn't use .rul files... At least not the old one), but I'll attach my MapEdit.dat.
I can also link you the whole terrain folder if you like, just let me know.
-
nono. Mv2 has two "converter" apps: (1) RulesetConverter.exe (2) ConfigConverter/ConfigConverter.exe
(1) if you double-click RulesetConverter.exe (see screenshot #1) you can browse to an OxC .rul file and convert its "terrains:" definitions (if it has any) to a MapTilesets.yml for Mv2. By default it assumes that the basepath of your "terrains" (that is, the parent directory of the MAPS, ROUTES, AND TERRAIN directories) is going to be the same as the basepath set by the Configurator of Mv2. So tick the "add Basepath" box (and browse to the basepath of your MAPS, ROUTES, AND TERRAIN directories) only if you intend to set Mv2's Configurator basepath to some other directory.
For example, since Mv2 requires the CURSOR.PCK+TAB in xcom's UFOGRAPH directory (and benefits from SCANG.DAT and LOFTEMPS.DAT in GEODATA) set the Configurator's basepath to the parent of those directories (in Mv2 itself). But if the MAPS, ROUTES, AND TERRAIN directories that you want to work with are under some other directory, then the "add Basepath" browser should point to the latter.
( Note that multiple MapTilesets.yml can be merged together in a text editor. )
(2) ConfigConverter.exe on the other hand (see screenshot #2) parses the Mv1 config files (MapEdit.dat, Images.dat, Paths.pth) and tries to output a MapTilesets.yml based on those.
MapEdit.dat by itself isn't enough ...
basically, i need the fullpath of your UFOGRAPH folder, and the .rul file(s) from say FMP that has its "terrains" definitions -- as input for the RulesetConverter. Or MapEdit.dat, Images.dat, Paths.pth -- as input for the ConfigConverter.
or try it yerself,
-
OK, thanks KevL. So if understand corerctly, the RulesetConverter method assumes that:
1) The mod contains all terrains. Which is far from the truth, I am working on several mods, and many terrains are unique to one or some of them.
2) All terrains are in one .rul file. Not true, because not only terrains, UFOs and craft are typically in different rulesets, but also terrains tend to be split into multiple rulesets for sanity.
So, the ConfigConverter looks like the way to go for me, therefore I'm attaching all three files you mentioned.
Many thanks for the help!
-
An other strategy could be to rebuild mapview tileset by import mod rule files ::)
https://openxcom.org/forum/index.php/topic,1321.msg122525.html#msg122525 (https://openxcom.org/forum/index.php/topic,1321.msg122525.html#msg122525)
-
So, the ConfigConverter looks like the way to go for me, therefore I'm attaching all three files you mentioned.
@Solarius
1. open Mapview2
2. goto Edit|Configurator
3. select XCOM Resource paths
4. set UFO to "D:\ufa_zapasowa\UFO" (no quotes)
5. set TFTD to "D:\ufa_zapasowa\XComTFTD" (no quotes)
6. E=mc^2
7. let Mapview2 restart, then close it.
8. in subfolder /settings, rename your current MapTilesets.yml (eg, MapTilesets_bak.yml)
9. drop in the attached MapTilesets.yml
10. open MapView2 while doing a voodoo chicken dance
Notes:
- changed the duplicated "XBASE_05" to "XBASE_06" (which was missing from the sequence of XBASE_0*)
(group: UFO - Terrain, category: X-Com Base Expanded)
- deleted the duplicated "XBASES00" to "XBASES03" (but no maps were missing from the sequence)
(group: TFTD - Terrain, category: X-Com Underwater Base)
- warning regarding "LINERT0*" - the terrain "DECKC" is assigned twice on each Map (left as-is)
(group: TFTD - Terrain, category: Cruise Ship 1 Terror Site)
- changed terrain "plane" (mcd/pck/tab reference) to uppercase "PLANE"
- tilesets that exhibited anomalies during the conversion (terrain variables were redefined between UFO and TFTD):
- type: XBASES00
- type: XBASES01
- type: XBASES02
- type: XBASES03
- type: HANGAR_UPPER_CHAMBER
- type: EXPANDEDTERROR22
- type: MARS00
- type: MARS01
- type: MARS02
- type: MARS03
- type: MARS04
- type: MARS05
- type: MARS06
- type: MARS07
- type: MARS08
- type: MARS09
- type: MARS10
- type: SEABED00
- type: SEABED01
- type: SEABED02
- type: SEABED03
- type: SEABED04
- type: SEABED05
- type: SEABED06
- type: SEABED07
- type: SEABED08
- type: SEABED09
- type: SEABED10
- type: SEABED11
- type: SEABED12
- type: GRUNGE00
- type: GRUNGE01
- type: GRUNGE02
- type: GRUNGE03
- type: GRUNGE04
- type: GRUNGE05
- type: GRUNGE06
- type: GRUNGE07
- type: GRUNGE08
- type: GRUNGE09
- type: GRUNGE10
- type: GRUNGE11
- type: GRUNGE12
- type: GRUNGE13
- type: GRUNGE14
- type: GRUNGE15
- type: GRUNGE16
- type: LINERT00
- type: LINERT01
- type: UPLANET_00
- type: UPLANET_01
- type: UPLANET_02
- type: UPLANET_03
- type: UPLANET_04
- type: UPLANET_05
- type: UPLANET_06
- type: UPLANET_07
- type: UPLANET_08
- type: UPLANET_09
- type: UPLANET_10
- type: UPLANET_11
- type: UPLANET_12
- type: UPLANET_13
- type: UPLANET_14
- type: UPLANET_15
- type: UPLANET_16
- type: UPLANET_17
- type: UPLANET_18
- type: UPLANET_19
- type: UFO_125
- type: MOON_OUTPOST00
- type: SCI_HOUSE
To edit a tileset, select it in the maptree, right click -> Edit Tileset ...
[F1] should open the Help file
there's also a keyboard_cheatsheet.txt
If we're lucky this will work first go, but I suggest just browsing around (in Mv2) for a day before doing serious editing.
oh, and back up yer stuff ! as in ... now (plsktks)
-
Oh man. It works! And how!
It's like upgrading from a C64 to Amiga 500... Thank you, thank you, thanks you.
-
coolio :)
/enjoy