[Solatar]

FSPort was an oversight, but as you can see from the 3.16.12 mediavps release thread, the different folder was intentional.

The zip (and 7z) have been set up to extract to a numbered folder called "mediavps_3612" as part of a concept for being able to retain compatibility going forward, rather than always directly over-writing the previous version.

This means that you will need to be sure about your mod.ini's and Launcher Mod selection to accomodate this change. We feel it is a good way to allow for existing mods to have a better amount of time in which to keep up.

As an example of this, while the MediaVPs make enhancements to the presentation of FS2 Campaign and provide updated assets, many times portions of assets get used in other areas. An example of this is Blue Planet. One of the warp gates uses maps (some, but not all) from the Hatshepsut. Because that model has now changed, Blue Planet must now include the maps that it sourced, which it should have done in the first place. But by providing the MediaVPs with the changes to it's own versioned directory, we spare users the headache of older mods breaking while the mod get's updated to working with the newer set (since not every mod can update and release at the same time as the MediaVPs) by letting them still continue to play with the older set since that's what the mods mod.ini will by default be pointing to.

[Fury]

Exactly. Naming change of mediavps mod folder was intentional. You would have had a ton of broken mods and campaigns in your hands if that hadn't been done. The bottom line is that anyone should be able to play mods and campaigns as-intended regardless of what mediavps version they were built on. Mucking around with mod.ini's is not recommended and should not be done unless you are sure the mod or campaign in question actually works with 3.6.12's without debug errors. That is a problem for authors to handle and issue an update, not end-user.

Next major update of mediavps should again use version number in the mod folder to avoid mods and campaigns designed for 3.6.'12 from breaking. In best-case scenario you only have current and previous mediavps installed. But of course, that all depends on authors to keep their mods up-to-date, which is not given.