Last edited by DOCa Cola on January 14th, 2010, 8:32 am, edited 1 time in total.

Hey. as promised some info how to convert your maps properly from earlier versions of Fleet Operations to a 3.1.0 (or later) compatible format.The problem with earlier versions of Fleet Operations has been, that i was not able 'crack' the map versioning used by Armada 2 until the 3.1.0 release. 3.1.0 will be the last release where you have go through the pain of a map conversion like this.Some of you may remember that 3.0.2 included a new map format, that made it impossible to use previously made maps. The reason behind this was that fleet operations could only handle one map format and wasn't able to use the versioning features of armada 2 that can distinguish between different map formats.3.1.0 is now also capable of converting the real old maps that were created with 1.0-3.0.1 or maps from Armada 2 BUT of course restrictions still apply. Maps are usually filled with asteroids, wormholes, planets etc. Maps can only be used if all these objects still exist in that one particular mod. Maps created with Fleet Operations 3.0PR should still work with Fleet Operations 3.1.0 and later. Maps from Armada 2 are unlikely to work at all. Fleet Operations 3.1.0 now can read all Armada 2 map formats, but it isn't said, that it understands with what objects the map is populated.

Anyway, here is what you have to do:Fleet Operations 3.0PR mapsUnlike previous versions, 3.1.0 is capable of reading those map types again. 3.0PR may still have problems as many objects from 3.0PR don't exist in in 3.x versions anymore, so they may crash.no conversion should be required, though some maps may just not work properly

Fleet Operations 3.0.0-3.0.1 mapsIn theory you should be able to use 3.0.0 and 3.0.1 created maps without further complications. no conversion should be required

Fleet Operations 3.0.2-3.0.7 mapsThese maps have to be version tagged, so that 3.1.0 knows which format they have, as these maps have a different map format then those from stock Armada 2 which Fleet Operations was previously not able to distinguish.RequirementsThe conversion can be done through a Hex Editor of your choice (for example XVI32).Convert map from 3.0.2-3.0.7 to 3.1.0 (and later)

first of all, backup your map!

an unmodified 3.0.2-3.0.7 map should look similar to this. What has to be edited is the version. 2177 is the standard version of an Armada 2 map, which is wrong for those maps:

it has to be changed to 3007 like shown here:

save the map and you should be ready to go.

Please feel free to ask here in the forums, if you need any assistance with the process.

Don't change the version number on maps created with 3.0.1 or earlier, it will corrupt your map. If your map crashes and has been created with an earlier version than 3.0.2 it is likely that on object that fleet operations cannot read anymore is being used.

Last edited by shadow651 on January 16th, 2010, 6:15 am, edited 1 time in total.

Just to warn other people, I have some maps that have some so called 'easter eggs/map objects' in them. turns out that one of the following is changed or is diffrent so that they must be removed in 3.0.7 before converting to 3.1.0 otherwise it crashes when you try to load those maps. (allthough I haven't tried removing the eggs yet but all maps without these piticular ones works fine so...)

Also: Mort converted one of my maps for me but no .txt file came out with it. I then pulled up the editor and saved it again but no .txt file again ...

Are they necessary anymore? I noticed all the maps standard with FO still have them but I'm ... a little confused as to how this works. Will a 3.0.7 .txt file for that map still work or does an updated one need to be made? If so, what needs to be done?