Okay...I'm not really a huge support guru, but there several big issues jumping right out at me here. Before we even get to what's going wrong with the Storm Front campaign, we need to fix some problems with where some of these files are located:
1) First off, the version of the FS2_Open engine you're using, 3.6.13, is waaaaaay out-of-date, so you want to update that. The most recent official release version is
3.6.18 final, though we also have a
3.7.0 release candidate out for testing; you'd probably want to go with 3.6.18 for right now to avoid the remote possibility of some other error popping up. Follow the install instructions on that thread, and then select the new 3.6.18 executable in the Launcher; you can then delete your 3.6.13 executable, and any other old FS2_Open versions you have lying around.
2) This is the real biggie here: you don't have the MediaVPs installed properly. The most important rule when playing FS2 mods is to never,
ever plop any VP files into the main FS2 directory. Delete anything in the main FS2 folder with an mv_ in the front of it; it looks like you have an extra set of some copy of the MediaVPs in there, which has the potential to cause all sorts of problems. Now, while you do have the right mediavps_3612 folder, there are definitely a few VP files in there that don't belong, and I'm not sure that the rest in there are the correct versions of the files. Your best bet is to just clear all of that out and re-download the 3.6.12 MediaVPs from the
release thread, following those instructions. Oh, and for the record, the 3.6.10 VPs are so far out of date that it isn't even funny, so don't go anywhere near those.
3) As far as I can see, the Storm Front campaigns don't have any dependence on the FSPort, so you don't need to worry about that at all. As it stands, your fsport and fsport-mediavps folders are completely empty, so listing them in a mod.ini file wouldn't accomplish anything anyway. It's probably best to delete those folders for now, since that way you won't confuse yourself by thinking that you have them in there.
4) Finally, installing FS2 to the Program Files folder has the potential to cause issues down the line, since Windows places certain additional restrictions on programs installed there; in addition, FS2 isn't a huge fan of dealing with elongated file paths. To save yourself some future headaches, we highly recommend installing the game to its old retail default location, C:\Games\FreeSpace2.
I think that takes care of the general stuff, so now on to Storm Front itself. That first error you posted there seems to be a mistake in one of the mission events, which would be something out of your control. What I would recommend doing is going to the
Storm Front campaign page and re-downloading at least the mission files VP, to see if that bug has been fixed in a newer version. Make sure to follow the installation instructions on that page to the letter; I'd also change the Storm Front mod.ini file back to its original version.
Finally, just for future reference, there's a great guide for installing FS2_Open and mods for it in
this thread; it'll help you avoid the more common mistakes when setting things up. If you're still having problems after going through this, just ask away.
