It appears Sathy is supercap2s-01.pof in sparky_fs2.vp, and is not present in mediavps3612. So.. 3.6.12 MVPs uses the retail Sathy? 3.6.12 models are in MV_Assets.3612.vp
I'm using
VPGUI (requires .Net Framework 4.5), you can also use
Maja Express (requires Java).
To view all the models, tables, etc, install
Model View,
jTBLEdit, eh.. you'll need the Descent Manager DLL pack from
DMTools (run dp2003.exe) for Model View, I believe (model view I linked is newer than the one included in DMTools so use that, not the included one). You could also use the table viewer in DMTools instead of jTBLEdit. There are also ANI View, and pilot view, I think.
You should only need VP viewer, model viewer, maybe table viewer (to see what textures etc are used with MVPs 2014 for troubleshooting)
Keep in mind that the ships table file (.tbl) for FreeSpace is most likely modded with a .tbm in MVPs 3.6.12 / 3.6.14 (so that the table can be modified, instead of being overridden for minor edits).
You can easily open table files in Notepad without using a table viewer, but it might be a bit easier to read in a viewer (as it is probably sorted into columns for you)
HOWEVER I'm not sure if jTBLView or TableView32 {from DMTools} supports tbm files; you might have to use notepad for those.
Someone who has modded FS recently should be able to help you sort these out; but you can start playing with it using the information I gave above. Oh, and
read skim through this:
http://www.hard-light.net/wiki/index.php/FS2_Data_StructureEDIT: Oh, and how FS2 handles hierarchy:
Say you are running a mod (fscoolmod36) which depended on 3.6.14 MVPs:
fscoolmod36\data\models\fancymodel6.pof would override fscoolmod36\models.vp/data/models/fancymodel6.pof
If there was a fancymodel6 in MVPs 3.6.14, whether a file or in the 3.6.14 vps, fscoolmod36's version would be used instead, as fscoolmod36 is selected as a mod
And, of course, any retail fancymodel6 would not be used, file \data\models\fancymodel6.pof or .vp/data/models/fancymodel6.pof
Basically, this allows mods to be distributed without distributing any assets from the mods they are based on, unless the assets are modified, and, it allows users to extract the assets, modify them, and place them into the directory for testing, without changing the .vp file (which would make diagnosing errors more difficult as you wouldn't know if the distributed .vp had been altered -- modifying .VP files is
highly discouraged, unless you are making your own mod. To change something, extract the files you want to change and leave them in the mod's \data\models or \data\tables etc).