Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Also it should probably just be named F-100D and not F-100D (SEAD) since dynamic pylons makes this naming obsolete.
Thanks as always, Ace! The silver scheme was intended; labelling it "tan" was the error. I just forgot to update the texture's displayName parameter after a cut-and-paste. I've fixed this for my next update.
w.r.t. F-100D (SEAD), that vehicle displayName is inherited from the original class that I used as a base. Tacking on the "intended role" like that, based on default pylon loadout is something SOG devs have done with all their planes. With SOG's F-4, I decided that the AT role was generic enough and I over-wrote SOG's displayName in keeping with vanilla naming conventions. However, with F100-D, I decided to use the SEAD loadout as my default (I think I read somewhere that this was a common mission for the F-100 towards the end of service life with the USAF). And then I decided not to overwrite SOG's displayName in order to head off a barrage of complaints like, "Why is this plane spawning in with anti-radiation missiles?" For now, I'm going to leave it as-is.
Although also, F-100D generic variant doesn't show up in Zeus.