I've just taken a look to this. And it is a loading order problem. And, yes, I'm using the latest available build (2nd hoopla from Taylor, ie, RC7.9x 3rd version).
Both, fsport-awakenings.vp and fsport3_0_3.vp have a ship.tbl. But they are different:+AWAKENINGS:
$Name: SF Dragon#Terrans+FSPORT:
$Name: SF Dragon (Terrans)
Despite of what Explorer file order shows, fsport-awakenings.vp has higher loading priority than fsport3_0_3.vp. ("-" is alphabetically before "3"). So Awakenings table takes the control and defines a different ship from the one used in port missions.
- The best one. Install each mod in its own folder and use Mod.ini and SecondaryList features. DO THIS ALWAYS, DON'T MIX MODS IN THE SAME FOLDER AND YOUR LIFE WILL BE BETTER.
- Not a really good one. Rename fsport3_0_3.vp to fsport-3_0_3.vp. Then you'll have moved the trouble to Awakenings Mod (if there were missions with Terran Dragons in it). But Port will work fine.
As a side note: I haven't checked all settings in both ship.tbl's, but even if there weren't different named ships, mixing both mods can change designed game balance. As an example: imagine that Awakenigs had a faster Herc because of whatever reason you can think of. Then Herc in port would be also faster, so missions with it would be somehow easier. So again, never mix mods, unless you are absolutely sure you're not going to have any undesired cross-effect.
I hear you there, snake. XD And Awakenings does work if you put it in a seperate folder with a mod.ini file with the lines:
secondarymod = fsport, mediavps;
Makes everything peachy keen.
Beware of the space you've put in "SecondaryMod = FSPort,mediavps;". IIRC you have to type without spaces in the list. With your typing FSOpen will be looking for a folder called " mediavps" instead of "mediavps".
And remember that "fsport" or "mediavps" should be changed to match the EXACT name you have actually used to place your mods or additions.