HellFire and BrimStone for SFP1/WOV/WOE (Version 1.1)

[FastCargo 412]

View File

HellFire and BrimStone for SFP1/WOV/WOE (Version 1.1)

---

******************************** Version 1.1 Updates *****************************

 

1. Readme Updated.

 

******************************** Version 1.0 Original Release ********************

 

Version 1.0

 

Thanks to the following folks:

 

TK - For the ThirdWire series of sims.

Bunyap and Wpnssgt - For the original Weapons Pack.

Mustang - For the great video tutorials.

To my fellow Combatace moderators - For helping me beta test and work out bugs.

Any errors or mistakes are entirely mine.

 

What you will need first:

 

Bunyap's Weapon's Pack - http://forum.combatace.com/index.php?autom...p;showfile=2672

 

Thirdwire Weapons Editor - http://www.thirdwire.com/downloads_tools.htm

 

Copy of SFP1/WOE/WOV patched to the latest standard (as of 11 Oct 07)

 

Optional: A hex editing program and/or a graphics editing program (Paint Shop Pro, GiMP, etc)

 

Notes and limitations:

 

I have included the reference materials I used to make the weapons. And for advanced modelers, I have also included the skin templates if you want to make your own or improve on mine.

 

Here is which racks go with which weapons:

 

Brimstone - Brimstone 3-pack

AGM-114A - M-272, M-279, M-299

AGM-114F - M-272, M-279, M-299

AGM-114L - M-272L, M-299L

 

The reason the L model needs a different rack is that ATRs cannot carry EOGR weapons, so I had to make TLR versions of those racks. Don't mix them up when building your loadout files.

 

Aircraft weapons stations must have ATR,LGR to be able to carry the AGM-114A and F models...and have TLR,EOGR to carry the AGM-114L and BrimStone missiles. The A/F models require a laser, while the L and Brimstone are radar (we use GPS as a substitute) guided.

 

Paint schemes are approximations. The HellFire has a LOT of different varients in schemes, so I went with the most reasonable. Early HellFires were very olive drab...however, recent pictures show almost a blue/black appearance. Brimstone test articles were very bright colored...the real thing seems almost an off white.

 

For multi-pack carry, if the TW engine finds a multi-rack that is listed eariler in the Weapondata.ini that can carry the missile, it will use that rack instead. You may have to fiddle with your loadout.ini files to get it to use the right rack.

 

The BrimStone racks appear to angle down...the pictures of it I saw on the Tornado showed different angles...and some other mountings showed parallel. So I compromised and gave it a slight downward slant so it won't look real odd on different aircraft.

 

This is FREEWARE only, NO money is allowed to be made on the contents of these files, in whole or in part.

 

Feel free to redistribute, as long as the original authors are given appropriate credit.

 

Questions? Contact me at Combatace.

 

FastCargo

11 Oct 07

---

• Submitter
  FastCargo
• Submitted
  10/11/2007
• Category
  Single Ordnance Files

 

[FastCargo 412]

Alright guys, couple of minor issues for the upload.

 

One, I just found in the Weapondata.ini an old entry from the Weapons Pack.

 

[WeaponData829]

TypeName=M299

FullName=M299

ModelName=LAU

Mass=50.000000

Diameter=0.000000

Length=0.000000

AttachmentType=USAF

NationName=USAF

StartYear=1955

EndYear=2020

Availability=2

BaseQuantity=25

Exported=FALSE

ExportStartYear=0

ExportEndYear=0

ExportAvailability=0

WeaponDataType=6

WeaponsRackType=ATR

NumWeapons=4

LoadLimit=60.000000

LengthLimit=1.500000

MaxFuelAmount=0.000000

Attachment01Position=0.142000,0.000000,-0.185000

Attachment01Angle=0.000000,0.000000,0.000000

Attachment02Position=-0.142000,0.000000,-0.185000

Attachment02Angle=0.000000,0.000000,0.000000

Attachment03Position=0.142000,0.000000,-0.486000

Attachment03Angle=0.000000,0.000000,0.000000

Attachment04Position=-0.142000,0.000000,-0.486000

Attachment04Angle=0.000000,0.000000,0.000000

 

Now, though this should not conflict what you put into the pack, this rack has no LOD file with that name. So it may cause problems. I would recommend substituting this entry with the one from the bottom of your Weaponsdata.ini:

 

[WeaponData829]

TypeName=M-299L

FullName=HellFire 4-Pack (Late)

ModelName=HellFire4Rail

Mass=66.000000

Diameter=0.178000

Length=1.600000

AttachmentType=USN

NationName=USMC

StartYear=1995

EndYear=2020

Availability=2

BaseQuantity=25

Exported=TRUE

ExportStartYear=1995

ExportEndYear=2020

ExportAvailability=2

WeaponDataType=6

WeaponsRackType=TLR

NumWeapons=4

LoadLimit=50.000000

LengthLimit=1.800000

MaxFuelAmount=0.000000

Attachment01Position=0.170200,0.140500,-0.050700

Attachment01Angle=0.000000,0.000000,0.000000

Attachment02Position=-0.170200,0.140500,-0.050700

Attachment02Angle=0.000000,0.000000,0.000000

Attachment03Position=0.127600,0.140500,-0.335600

Attachment03Angle=0.000000,0.000000,0.000000

Attachment04Position=-0.127600,0.140500,-0.335600

Attachment04Angle=0.000000,0.000000,0.000000

 

One less issue to worry about.

 

Also, I didn't specify which racks go with which weapons.

 

Brimstone - Brimstone 3-pack

AGM-114A - M-272, M-279, M-299

AGM-114F - M-272, M-279, M-299

AGM-114L - M-272L, M-299L

 

The reason the L model needs a different rack is that ATRs cannot carry EOGR weapons, so I had to make TLR versions of those racks. Don't mix them up when building your loadout files.

 

FastCargo

[+suhsjake 11]

Good Work FastCargo. What about the TOW missile Family? Keep it up Fastcargo.

[+ravenclaw_007 7,236]

great work i realy like the brimstone on the tornado

 

 

 

thank you and keep up the good work

[Hazen75 0]

After I installed the weapons and racks, the skins for the AGM-114A are NOT showing and the rack for the Brimstone is also not showing. I use these weapons and racks on the AH-1W Cobra. What do I need to do to get them to show up?

 

Hazen Cowan

 

Edited by FastCargo - Don't post your email on a public forum...a sure way to get on a spammers list.

[FastCargo 412]

After I installed the weapons and racks, the skins for the AGM-114A are NOT showing and the rack for the Brimstone is also not showing. I use these weapons and racks on the AH-1W Cobra. What do I need to do to get them to show up?

 

Okay, a two part question.

 

First, I understand the skin is not showing for the AGM-114A? Did you check that the AGM-114A.bmp file is in your Strike Fighters/Objects/Weapons directory? I know, stupid question but I need to ask. And, did you do a substitute install or a overwrite install?

 

Second, is the rack for the Brimstone not showing? Or the skin for the rack for the Brimstone not showing?

 

FastCargo

[Hazen75 0]

I did a new install on the Hellfires and the rack skin for the brimstone is not showing on the choosen aircraft.

[Mr. T 0]

This was covered in another forum in this general area.... have you not looked in there for your answer? I assure you it is in there you infidel.

[FastCargo 412]

I did a new install on the Hellfires and the rack skin for the brimstone is not showing on the choosen aircraft.

 

Odd, in both cases a skin isn't showing. I would recommend redownloading the addon, and verify all the files exist in the Objects/Weapons directory included with the addon, then copying the .LOD and .BMP files over to your install, overwriting the ones already there.

 

There is absolutely no reason the skins shouldn't be showing. The only thing I can think of was that the .bmps got corrupted.

 

FastCargo

[Canadair 16]

In the readme you state, that one has to fidget with loadout in order to have the proper rack showing

Which is okei for loadout taken from the loadoutfile, but it happens that when brimstone for instance are player-chosen and not preloaded it loads, , as you stated, th first compatible rack found; is there any workaround with this, r I am making mistakes?

[FastCargo 412]

Nope, you're not making a mistake. There is a workaround...but it's fairly involved. I'll post how this afternoon when I get the time.

 

FastCargo

[Canadair 16]

Nope, you're not making a mistake. There is a workaround...but it's fairly involved. I'll post how this afternoon when I get the time.

 

FastCargo

Thanks FC, no rush.

[FastCargo 412]

Okay, I forgot...got a bit busy. Anyway, here's the 'workaround'...it's actually more of a fix.

 

First, take a look at your Weapondata.ini file. Lets say for today we want to fix our IRM rails (2IR).

 

[WeaponData600]

TypeName=LAU-105

FullName=LAU-105 DRA

ModelName=LAU-105

Mass=73.029999

Diameter=0.100000

Length=2.800000

AttachmentType=NATO,USAF,USN

NationName=USAF

StartYear=0

EndYear=0

Availability=2

BaseQuantity=4

Exported=TRUE

ExportStartYear=0

ExportEndYear=0

ExportAvailability=2

WeaponDataType=6

WeaponsRackType=2IR

NumWeapons=2

LoadLimit=95.000000

LengthLimit=3.000000

MaxFuelAmount=0.000000

Attachment01Position=0.282000,0.000000,-0.020000

Attachment01Angle=0.000000,0.000000,-5156.620156

Attachment02Position=-0.282000,0.000000,-0.020000

Attachment02Angle=0.000000,0.000000,5156.620156

 

[WeaponData800]

TypeName=ATAL

FullName=2 Pack Stinger Rack

ModelName=ATAL

Mass=20.000000

Diameter=0.200000

Length=1.600000

AttachmentType=USAF

NationName=USAF

StartYear=1978

EndYear=2020

Availability=2

BaseQuantity=12

Exported=TRUE

ExportStartYear=1978

ExportEndYear=2020

ExportAvailability=2

WeaponDataType=6

WeaponsRackType=2IR

NumWeapons=2

LoadLimit=50.000000

LengthLimit=1.600000

MaxFuelAmount=0.000000

Attachment01Position=0.137000,0.000000,0.034500

Attachment01Angle=0.000000,0.000000,0.000000

Attachment02Position=-0.137000,0.000000,0.034500

Attachment02Angle=0.000000,0.000000,0.000000

 

Note the bolded areas...these are important.

 

Now, the situation currently as you see it. There are 2IR rails in this order. If you were to go into your loadout menu to load two Stingers, it would use the LAU-105 rail, because it comes first in the weapondata.ini (actually weapondata.dat...but that's another story)...which would result in Stingers hanging on a Sidewinder rail...silly looking. However, notice that it would not happen the other way around...because of the LoadLimit and LengthLimit restrictions...you couldn't load a 'winder on a Stinger rail unless you 'forced it' via the Loadout.ini.

 

So, here's how to fix it.

 

Backup your weapondata.ini first!!!!

 

First, find all the weapondata.ini entries of the same type...in this case WeaponsRackType=2IR. Find each weapon entry of that type, copy and paste all into a new text file.

 

Then, sort them.

 

A) By AttachmentType

B) Then by LengthLimit

C) Then by LoadLimit

 

A few notes. For those racks that do not have Length/LoadLimit entries, you may want to consider making some that match the largest weapon that rack will carry. This will help prevent weird loadouts and will also help sorting.

 

Renumber the entries so that the reordered entries plug into the previous slots using copy and overwrite. Finish by doing the weapon editor dance.

 

You should now have entries that will help avoid mismatched racks/missiles. The more restrictive your AttachmentType entries are (for the aircraft, rack, and weapon) the less chance of getting a mismatch.

 

Also, by sorting your racks as above, the engine will not attempt to load a rack that the weapon cannot fit on.

 

FastCargo

[Canadair 16]

Thanks FC. Make me wish all FI and Check Pilots and instructors were like you,,,

sadly it does not happen. (cries on md-80 CBT) :sorry: