SF2 Lockheed YF-12A "Starduster" (Veltro2K) Redux...

[+Viper63a 651]

View File

SF2 Lockheed YF-12A "Starduster" (Veltro2K) Redux...

---

SF2 Lockheed YF-12A "Starduster" (Veltro2K) Redux...
by Viper63a

 

This started out as an add-on pack to the "What If... SF2 Lockheed (Y)F-12A Starduster by Veltro2K" pack released by Wrench, but by the time I got done with it...it became a stand alone pack. Nothing else is required, but if you want to download the inspiration for this pack, you can find it here...

 

http://combatace.com/topic/76491-what-if-sf2-lockheed-yf-12a-starduster-by-veltro2k/

 

This pack adds the YF-12A "Starduster" and a new 1950/60s era pilot in grey flight suit. Comes complete with new skins, Hangar, Loading, Loadout and Decal files.

 

As always, I recommend that you back up your mod folder before you install any new mod...just in case.

 

* To install, simply unzip and copy the contents of the "To_Mod_Folder" folder to your StrikeFighter2 mod folder and Overwrite (if needed).

 

My StrikeFighter2 mod on Win97 64-bit was..(yours may be different)...

 

C:\Users\<your_id>\Saved Games\Thirdwire\StrikeFighter2...

 

Original "Readmes" are in the Extra folder with some other goodies...

 

Enjoy!

 

=Viper=

 

----------------------------

 

Credits:
Veltro2k for the YF-12A
???? for the J-79 engine and AB sounds -- spillone? fubar? !!!I can't remember WHERE they came from;
Pasko for the orignal MiG Pilot figure and his F-106 cockpit (reused/modded herein)
Wrench for the original ini work, decals and assembling the package

 

----------------------------

---

• Submitter
  viper63a
• Submitted
  11/04/2015
• Category
  Other

 

[Wrench 9,461]

You should have left the AircraftFullName= exactly as how I'd originally set it up. That will make it match the stock 3w and all 3rd party naming conventions.

 

I recommend end users change it back to

 

AircraftFullName=F-12A Starduster
AircraftShortName=F-12A

[+Menrva 3,998]

Well, actually this package contains a historically correct skin that represents the YF-12, not a fictional F-12A as if it went into full production, so I'd rather keep the plane's name as Viper set it, of course all end users are free to rename it to whatever they like.

 

Thanks a lot Viper, you made my day.

[+Viper63a 651]

We can have it both ways...LOL. I released Version 2 whereI renamed the jet's main folder to "YF-12A" so it will not change the original pack from F-12A to YF-12A. So the users can have both YF-12A and the F-12A jets...My bad!...Sorry about that Wrench....

 

=V=

Edited November 4, 2015 by viper63a

[+crisisloaner 784]

The download link doesn't work ,where is the package ?

[Wrench 9,461]

well, just think about the designations (letter/number) and what it means...

 

"Y" always designated a pre-production version used for proof of concept and testing. All the way back to 1930s

F (obviously) for fighter

12 for McNamara's "unitized numbering convention" for all services

A for first sub-variant (should actually be "B" for production models, following the logic of the time frame)

 

the name itself, "Blackbird" was ONLY reserved for the SR-71. The name I used on the original pack, as stated in the original readme, follows pretty much exactly HOW Lockheed did/does things.

 

One of the major questions would be... why would ADC need an all black INTERCEPTOR? The SR-71 were black due to the use of radar absorbent paint (iirc, "Iron Ball"). They've no need to hide, as the air intercept radar would give away their position as soon as it was turned on and searching for targets (think of a flashlight in a pitch black room)

 

but, whatever.

[+Viper63a 651]

I agree with you Wrench, just looking for a loop hole here.

 

I read somewhere that the YF-12As were used to hide the existence of the Black A-12s after the existence of A-12s were accidentally leaked. So no, there is no need for an all Black Fighter, unless they were trying to passively mislead people into thinking the secret Black A-12s were actually Black YF-12As...I beleive F-104 or 106s replaced the need for F-12A. They were cheaper and not painted black.

 

The name "Blackbird" was not officially designated until the SR-71, but that doesn't mean the name hasn't been around long before then.

 

I think YF-12B and Cs never went into production as Fighters, instead the parts were re-purposed to became the secret SR-71s to replace the A-12s.

 

This brings into question, Why "A-12"? This was a CIA bird, but it had an "Attack" designation? Curious, do you know?

 

:)

Edited November 4, 2015 by viper63a

[+Menrva 3,998]

I don't know why, Wrench, but it seems that the YF-12A was indeed black, because it was after all a pre-production version; just check the wiki, there are some photos there, although I fear that one is of a SR-71 Blackbird: https://en.wikipedia.org/wiki/Lockheed_YF-12

 

Viper just planned to recreate, by my request, the pre-production YF-12A version (despite of the fact that there were only three of those), not an additional skin for the what if interceptor F-12A, that is all.

 

This brings into question, Why "A-12"? This was a CIA bird, but it had an "Attack" designation? Curious, do you know?

 

It had nothing to do with the usual "Attack" designation, according to this: https://en.wikipedia.org/wiki/Lockheed_A-12

 

Most likely hence why the YF-12A was black, because they took some of the existing A-12s and converted them to interceptors.

Edited November 4, 2015 by blaze95

[+Viper63a 651]

The download link doesn't work ,where is the package ?

You must have caught it while I was uploading the Version 2? I just checked it, try again please...

 

=v=

 

Ahhhh....A-12 - 'A referring to "Archangel"' cool!

 

=V=

Edited November 4, 2015 by viper63a

[Wrench 9,461]

well, as we're NOT talking pre-production or prototypes, but "operational" ADC birds, they would have most likely used the same color schemes as the 102 and 106s in ADC service; a light grey.

 

Yes, a few of the protos show they were black (as evidenced in photos in the Aerofax & WarbirdTech books I referenced in my original credits ). But, for things like these, I have no trust in Wiki ... but prefer the references I have; they tend to have bit more detail (and I'm sure their data is probably cut/pasted into the Wiki entries).

Be happy to zip the books up and pm to either or both of you.

 

oh, and just little advice on decals ...one doesn't need 24 ADC tail badges; just one decal set to Level=0, as they represent the 'command' (think if it like a insignia or nation name). I also would have gone to decals for the fuselage tags and wing stars. They're quite blurry when viewed in game ( sometimes are artifacts of skin size, or more likely material applied to the LOD).

[+Viper63a 651]

But Black is so cool?! :)

 

On the decals, understand. I prefer decals as well, and will convert them over.

 

One question on the tail decal. What do I do if I want a mix of decals? Not all just one. I notice the game will randomly select the range indicated in the Texture.ini? If I have 24 tail numbers and I want random mix of 5 or 6 tail command type emblems. Does the sn000 = tail000?

 

On the reference, please send to ****. I would appreciate it.

 

=V=

Edited November 5, 2015 by Wrench
removed email addy --- never post that in the open!

[+daddyairplanes 8,680]

Random mixes have to be called in the textureset, along with the total number and start (typically 000) and end points (0xx)

 

As to your 5-6 types, what I do is have the most common as "decal", then the different ones as whatever they are in the lineup (decal007, decal014 etc). It will default to the standard decal unless the specific one is selected.

 

Finally, I've grown to preferring to group most decals as serials. Like I said it will still select the main one but allows for differences

(Like transports for MAC and then a few in the ANG)

 

Kevin, i'm on my tablet on break from driving, otherwise I would show the lines for random decals

[KJakker 875]

Dose this version have the M-61 cannon installed like in the drawing below?

 

 

[+Viper63a 651]

Dose this version have the M-61 cannon installed like in the drawing below?

Very Interesting...No, it does not...but that would be cool.

 

On another topic of the "Blackbird" moniker....

https://books.google.com/books?id=77oeBQAAQBAJ&pg=PA54&lpg=PA54&dq=AF-12+M-61&source=bl&ots=Jaa7JqN1qR&sig=ZepY5IVFUyKPHf49wVZWJZcOTY0&hl=en&sa=X&ved=0CB0Q6AEwAGoVChMI7a60-574yAIVhUcmCh2YlguV#v=onepage&q=AF-12%20M-61&f=false

 

=V=

[Wrench 9,461]

that book might be found "elsewhere" on pdf, if one searches hard and long enough

 

adding a gun is truly a nothing job...with mue's lod viewer, it's a very simple matter to figure out where the muzzle flash should show up

[+Viper63a 651]

I've not used a LOD viewer, I've been testing everything in-game. Do you know where I can get a LOD viewer?

 

=V=

[+Viper63a 651]

Thanks, that lod viewer made decal placing ALOT easier....

 

* Version 3 11/06/2015 uploaded....
1) Armed with M61 Cannon. No documentation, so best guess at where it is supposed to be. Took cue from the lodview info.
2) Changed all but 2 painted emblems to decals. Right outer wing bottom decal would bleed over to the top of the wing. I tried placing it all over the place with no joy. So, I just left the emblem painted on the skin.

 

Also, in the ..."Objects\Aircraft\YF-12A\AF_Blk" folder, there are 3 alt skins...

YF-12_Decal_Free.jpg - No decal painted onto the skin - a blank bird.

YF-12_Decal_Mixed.jpg - All blank except the two decals under the wing (Default).

YF-12_Decal_Painted.jpg - All decals are painted unto the skin.

 

= V=

[+Viper63a 651]

Reuploaded version 3, missed a sound file. Still waiting for admin approval...

 

=V=

[+Viper63a 651]

Version 3.5 is up with a new cockpit sound and a fix for the gun aiming....

[+Viper63a 651]

Version 4 Released..

 

Had some issues with tail number randomization after Version 3. All the planes were using tail number ***42 with a Skunk emblem. So in Version 4 multiple tail numbers are used again, but the emblem will always be the ADC patch.

 

=V=

[Icarus999 70]

Anybody have any info on the YF-12's radar capabilities?  Seems to me that the search and track strength could be bumped up a bit, the Aim-47 had a very long range.

[+Viper63a 651]

This mod was built off Wrench's repackaged version, so I am guessing it is pretty accurate...But, will take a look. Wrench sent me some info on the YF-12...

 

=V=

[+Typhoid 231]

does pretty well against Klaxian ships.......

 

[+Viper63a 651]

does pretty well against Klaxian ships.......

 

LOL...I've fought that fight as well...Yes they do...

 

:)

[+Viper63a 651]

Anybody have any info on the YF-12's radar capabilities?  Seems to me that the search and track strength could be bumped up a bit, the Aim-47 had a very long range.

So, FM and I was looking at the INI files. FM helps me a lot with the INI files...and we noticed that Radar settings are higher in the  DATA.INI file than in the "F-12_AVIONICS.INI". So I bumped up the "F-12_AVIONICS.INI" to match the "YF-12_DATA.INI". We also corrected the weight of the AIM-47...both will be in the next release. But if you want to try the new Radar settings, change the following in the "F-12_AVIONICS.INI" file. Please let me know what you think.. 

 

//SearchRange=70

//SearchStrength=70

//SearchTargetTime=5.0

SearchRange=150

SearchStrength=200

SearchTargetTime=1.0

 

//TrackRange=60

//TrackStrength=60

//TrackMemroyTime=5.0

TrackRange=100

TrackStrength=200

TrackMemroyTime=3.0

 

Viper