I was talking about the entire mod, not just the patch file.
It applies to any .vp files. If they are in \Freespace 2\ or in an active mod folder, they will be used by the game engine. Then there's the part about .vp files themselves. They are container files. Kind of like .zip, except that there is no compression. The .vp files contain all sorts of data: models, textures, effects, sounds and such. Under certain circumstances it is possible that two different .vp files contain some same files. Say, table files for example. If this happens, the .vp file that comes first in terms of mod folder usage and alphabetical order is read first. This is why I suggested renaming the patch file so that it would be read first.
-spec -glow -env -missile_lighting -normal -3dshockwave -targetinfo -rearm_timer -3dwarp -warp_flash -snd_preload -noparseerrors -safeloading -fps
I just read this over and caught myself. Notice it doesn't say "-mediavps" anywhere. Why isn't it detecting the mediavps?
It's just that the -mod parameter isn't listed in the settings.ini. If you've selected the \mediavps\ folder as a mod or
if you've selected a mod folder with a mod.ini referring to \mediavps\, the MediaVPs will be used. And your fs2_open.log revealed that everything is in order.
Did you try either of my suggestions (renaming the patch or moving it away completely)?