[MrMittens]

Guess what the problem is? Yep, that's right. Same as before.

Sooo, since my hopes of finding the original ships.tbl in my trash is slim to none, I was hoping that someone would have a link to one? I would use Turey's installer but my computer doesn't seem to want to run it. Sorry.

[nubbles526]

Wow.....what happened?

Anyways, extract ship.tbl from root_fs2.vp through a program such as VP View.

[Jeff Vader]

Indeed. All the necessary retail table files are in Root_fs2.vp. If you have persistent ship issues, it means that either

a) you have an extra vp file somewhere (most likely in \freespace2\) that is causing problems or

b) you have an extra ships.tbl or ***-shp.tbm somewhere (most likely in \freespace2\data\tables) that is causing problems.

[MrMittens]

No extra .vps or anything. Complete fs2 vanilla. I actually started the campaign over with a new pilot for exactly this sort of reason.

[Jeff Vader]

Well, there really aren't any other explanations. Unless, of course, you've been tinkering the ships.tbl inside Root_fs2.vp.

Just for kicks, try the following:

- Rename \freespace2\data\ to \freespace2\data-old\.
- Create a new \data\ folder.
- If you like your current pilots, copy \players\ from \freespace2\data-old\ to \freespace2\data\.

And as a side note, you shouldn't be able to "find your old ships.tbl in your trash", since if it was in the trash, it would most certainly mean that you've actually removed it from the Root_fs2.vp. And we all know that modifying existing, and especially retail vp files, is a Neddy No-No.

[Droid803]

Holy ****.
Astaroths? How did that happen?
I get ullys...but astaroths?

[Jeff Vader]

#Default Player Ship

    * Defines the default player ship in the game and also in the FRED. If in a mission appears a ship that has not been properly included to tables then game replaces the ship with the Default Player Ship.

Usually the Default Player Ship is Ulysses. And that's why ****ed up table files tend to replace ships with the Ulysses. But obviously this time the default ship is the Astaroth, for some godforsaken reason.

I still stand by my previous theory. If you, MrMittens, are sure that you don't have extra vps anywhere, the culprit must be \freespace2\data\tables. A while back, I argued for two days with ShivanEmperor who persistently claimed that he had done everything correctly but still had no weapons. I refused to believe and provided the same explanations as I've provided in this thread. And I was right. He had been using a bizarre method of installing mods, which included extracting the contents of all mod vp files and placing them to \freespace2\data\. Fortunately, we did finally manage to solve the case

So trust me. You've done something evil.

[Droid803]

#Default Player Ship

    * Defines the default player ship in the game and also in the FRED. If in a mission appears a ship that has not been properly included to tables then game replaces the ship with the Default Player Ship.

Usually the Default Player Ship is Ulysses. And that's why ****ed up table files tend to replace ships with the Ulysses. But obviously this time the default ship is the Astaroth, for some godforsaken reason.

yeah, but which mod has the Astaroth as the default player ship? O_o

[MrMittens]

[Jeff Vader]

b) you have an extra ships.tbl or ***-shp.tbm somewhere (most likely in \freespace2\data\tables) that is causing problems.

If you, MrMittens, are sure that you don't have extra vps anywhere, the culprit must be \freespace2\data\tables.

[MrMittens]

b) you have an extra ships.tbl or ***-shp.tbm somewhere (most likely in \freespace2\data\tables) that is causing problems.

If you, MrMittens, are sure that you don't have extra vps anywhere, the culprit must be \freespace2\data\tables.

Your point being? From the emboldened text one may infer that I left no clue as to the contents of the tables folder, but that's not true. I did. Bottom left. Not that hard to see. Clearly labeled "tables" at the top.

[Fenrir]

You are using the SCP, right? I think your problem is that you don`t have mv_core.vp, which is necessary for FS2_Open to run correctly. Get it here. If you want them, get the other MediaVPs there, too.

Ideally, you should make a new folder in your FreeSpace directory called mediavps and put it in there so you can run it as a mod.

[Droid803]

Huh? I played FSO fine without MV_Core...

[MrMittens]

You are using the SCP, right? I think your problem is that you don`t have mv_core.vp, which is necessary for FS2_Open to run correctly. Get it here. If you want them, get the other MediaVPs there, too.

Ideally, you should make a new folder in your FreeSpace directory called mediavps and put it in there so you can run it as a mod.

First time I went through the game I had no extra .vps whatsoever. In fact, I was running the old 3.6.7 version which was terribly glitchy but still displayed the correct ships.

[Spicious]

Have you got any tbl or tbm files hanging around anywhere within your freespace directories?

[Fenrir]

Huh? I played FSO fine without MV_Core...

Yeah, I looked in the vp and I realized that it doesn`t seem to have anything absolutely essential to run the game. Maybe that was the case in the older versions. Or I`m just delusional.

[MrMittens]

Have you got any tbl or tbm files hanging around anywhere within your freespace directories?

Negative.

[Jeff Vader]

Your point being? From the emboldened text one may infer that I left no clue as to the contents of the tables folder, but that's not true. I did. Bottom left. Not that hard to see. Clearly labeled "tables" at the top.

Ach, sorry. Missed that. Just got back from nightshift before posting.

I think your problem is that you don`t have mv_core.vp, which is necessary for FS2_Open to run correctly.

mv_core, as the name partially suggests, is MediaVPs-related. The MediaVPs offer higher-poly models and purdier textures, among other things. But they are far from necessary in terms of getting the game itself to run. Good to have but not necessary.

Hmm. I just want to ask one more time: Have you tampered with the retail vps? All symptoms point to a table error, but since there aren't any extra vps or .tbl files, the only explanation would be that the ships.tbl in Root_fs2.vp has been modified with sexy fatal results. Redownloading the retail files either with Turey's Installer or manually from HotU might help. But no guarantees.

[MrMittens]

Since I'm on a Mac, I have no means by which to tamper with Root_fs2.vp.

As for re-downloading some things, I tried the other day but for some reason Turey's installer doesn't want to launch.

[Titan]

maybe the version you're running isn't supported by mac...