[Jeff Vader]

The question is why keep ancient builds in existance and on a downlaod site when they are buggy compared to the newer ones? Why not just delete builds that are say 2 years old and from things like SCP 3.6.5? No reason to keep them in existance.

Some campaigns/mods refuse to work properly with newer builds. And there are not enough people to restore campaigns/mods for newer builds.

[chief1983]

High Max, don't tell me you've never deleted something, then shortly thereafter wished you hadn't.  I don't know if we still have the codebase at the time those builds were made, so if they were deleted it might be hard to get them back.  Even then it's still not really hurting anything, they're not huge files.

[Snail]

I want to discuss the presence of ship prefixes in names. Canonically, they're not widely used in FS2 and I don't see the point in adding them now.

In the first mission, it was weird to me to read this:

GVD Psamtik
GVD Hatshepsut

NTCv Belisarius
NTCv Deimos

I like the fact that the FSU team has added proper Alt Names, though.

I am 100% with Mobius on this one. In fact, I don't remember a time when I agreed with him more.

Prefixes are redundant. It's regular procedure in FreeSpace to just have the name of the ship rather than including the prefix. There were very few missions which included prefixes in Retail (the only ones I can remember are the SOC Loops). The fact that they've been added back really seems to me not really pointless, but an annoying addition.

Given that the MediaVPs are considered 'official', they really set the standard for other campaigns. The MediaVPs having these annoying prefixes seems to make them stand out to me as a sort of oddball or anomaly that really needs to be changed. Worse is the fact that the prefix naming convention isn't uniform throughout the campaign with some missions not having them while some others do.

[Aurora Paradox]

RELEASE: 3.6.10 Media VPs

==> In the "Custom Flags field" copy & paste (Without the quotes): "-ambient_factor 35 -ogl_spec 20 -spec_exp 15 -spec_point 1.2 -spec_static 1.5 -spec_tube 1.5"

(Note, any of these settings and the others in the lists can be tweaked as desired. See the Wiki Page on Launcher Flags for more information on each:
   http://www.hard-light.net/wiki/index.php/Command-Line_Reference )

I meant to ask this when the mediavps were  released however it slipped my mind.  What exactly do these custom field tags change?

[Romanmolf]

Blowfish is right. we will ALWAYS need to update our builds.

[dragonsniper]

It's worth the tiny 10mb's of bandwidth that's used getting it.

[blowfish]

I meant to ask this when the mediavps were  released however it slipped my mind.  What exactly do these custom field tags change?

The page explaining all of that is linked in the post you quoted

[Aurora Paradox]

I meant to ask this when the mediavps were  released however it slipped my mind.  What exactly do these custom field tags change?

The page explaining all of that is linked in the post you quoted

*slaps forehead*

I don't know how I missed that.

[Ransom]

Chalk up another vote for the removal of prefixes. Not much I can add to what's already been said by Snail and Mobius, but if nothing else, they look silly.

[Zacam]

Ransom's vote has me.

I was the one that did that out of a need for consistency and I decided on including the prefix because it also shows on the Nameplate texture.

Alternatively, the prefix could be dropped from the Ship Class line.

A: Remove prefix from Ship Name, leaving everything else be
B: Remove prefix from displaying in Ship Class instead

[General Battuta]

Remove from ship name, keep for class.

I think.

[The E]

Remove from ship name, keep for class, keep for nameplates. That'd be my vote...

[Androgeos Exeunt]

Remove from ship name, keep for class, keep for nameplates and keep it consistent!

[Droid803]

Remove from name, keep for class, keep for nameplate.

[Goober5000]

Keep for class and nameplate, definitely.  Also, the ship class should be GT regardless of whether it's Terran GTVA or Terran NTF.  Only one mission (The Romans Blunder) in FS1, ST, or FS2 ever used alternate names for rebel ships.  Even if the NTF is using a ship, it's still a GTVA design.  (The only NTF-designed ship, the Iceni, remains consistent with this rule.)

I personally prefer to keep the prefix on the ship name as well, but that varies a lot, even in the canon campaigns.

[ssmit132]

I don't know. Just, whatever you go with, keep them consistent.

[Dilmah G]

Hmmm, well I personally preferred the designation prefixes in front of the name. It made it more formal to me, like USS John Stennis, instead of like

-John Stennis, USS Nimitz Class Carrier

And the Aquitaine is always/usually referred to as the "GTD Aquitaine", and not "Aquitaine", I mean of course you'd refer to it like that casually. But as soon as you drop the prefixes these stop being the names of Multi-Trillion-Dollar warships and just become "Proper Nouns". IMO anyway

[Snail]

I personally prefer to keep the prefix on the ship name as well, but that varies a lot, even in the canon campaigns.

Barring FS1, the only canon missions which used prefixes were the SOC loops (Rebels and Renegades, Love the Treason..., ...But Hate the Traitor, As Lightning Fall and Into the Lion's Den). The rest (Should I really list them?) didn't use them prefixes.

[sfried]

Blowfish is right. we will ALWAYS need to update our builds.

It's worth the tiny 10mb's of bandwidth that's used getting it.

It's a hassle and some don't always have time to keep up.

[blowfish]

Meh.  If you don't have time for that download, you probably don't have the time for Freespace either (unless you're on dial-up ).  Anyway, it's not like you need to download EVERY nightly build that comes out, just a few of them.  SCP will always continue improving.  Unless you'd prefer that the code be frozen in its current state and declared final, despite bugs and unfulfilled feature requests .  So just update your build occasionally and you'll be fine.