Jump to content

Recommended Posts

Posted (edited)
Do not put anything that goes on a 10C on the FC2 10A. That just makes no sense :)

 

On the A-10A, we have the AGM-65K ... the newest Maverick. The k-model is newer, than the G/H-models. :smilewink:

 

The Air Force took delivery of the first AGM-65D in October 1983, with initial operational capability in February 1986. Delivery of operational AGM-65G missiles took place in 1989. AGM-65 missiles were employed by F-16s and A-10s in 1991 to attack armored targets in the Persian Gulf during Operation Desert Storm. Mavericks played a large part in the destruction of Iraq's significant military force.

 

The main portion of the program calls for Raytheon to buy back guidance and control sections of some of the 5,300 IR-guided AGM-65Gs the AF bought after the 1991 Persian Gulf War. The IR seekers have six cards that are common with the CCD and are reused. The CCDs then are mated with the center aft section of the missiles that were earlier stripped of their IR seeker. The new missile will be known as the AGM-65K.

http://www.fas.org/man/dod-101/sys/smart/agm-65.htm

 

I don't know what your sources are?

Alternative, read reliable books like "Warthog - Flying the A-10 in the Gulf War" or something else. There, you will find the same information.

I don't know, why ED make sometimes such faults ... maybe "fair gameplay".

 

 

Do we have to edit the db_weapons with the weight of these newly included weapons ? Or can we leave default weight in db_weapons file ? I don't know if it affects anything more then payload loadout screen.. or is the weight coded in some otherfile ?

That's the last thing that this mod needs before release of v1 I think. Thanks for you help guys !

 

All data are in the warheads.lua.

You just have to add the CLSID (which you find in the Names.lua) in the db_weapons.lua and A-10A.lua.

 

 

kind regards,

fire

Edited by VTJG17_Fire

Hardware: Intel i5 4670K | Zalman NPS9900MAX | GeIL 16GB @1333MHz | Asrock Z97 Pro4 | Sapphire Radeon R9 380X Nitro | Samsung SSDs 840 series 120GB & 250 GB | Samsung HD204UI 2TB | be quiet! Pure Power 530W | Aerocool RS-9 Devil Red | Samsung SyncMaster SA350 24" + ASUS VE198S 19" | Saitek X52 | TrackIR 5 | Thrustmaster MFD Cougar | Speedlink Darksky LED | Razor Diamondback | Razor X-Mat Control | SoundBlaster Tactic 3D Rage ### Software: Windows 10 Pro 64Bit

[sIGPIC][/sIGPIC]

Posted

What's with the Cockpit-Bug?

 

 

kind regards,

fire

Hardware: Intel i5 4670K | Zalman NPS9900MAX | GeIL 16GB @1333MHz | Asrock Z97 Pro4 | Sapphire Radeon R9 380X Nitro | Samsung SSDs 840 series 120GB & 250 GB | Samsung HD204UI 2TB | be quiet! Pure Power 530W | Aerocool RS-9 Devil Red | Samsung SyncMaster SA350 24" + ASUS VE198S 19" | Saitek X52 | TrackIR 5 | Thrustmaster MFD Cougar | Speedlink Darksky LED | Razor Diamondback | Razor X-Mat Control | SoundBlaster Tactic 3D Rage ### Software: Windows 10 Pro 64Bit

[sIGPIC][/sIGPIC]

Posted

haven't reproduces it yet, for some missions the server.lua file responsible for the cockpit alignement is a custom one. so it might be causing problems, but as far as missions created for the simmod a-10 are concerned there is no problem afaik.

 

another fact is that this mod (Extended payload) does not modify anything view related, so no explications about this quite yet.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...