Jump to content

dtmdragon

+MODDER
  • Content count

    2,013
  • Joined

  • Last visited

  • Days Won

    28

Everything posted by dtmdragon

  1. I am trying to find a work around for the Vikhr rocket launcher tubes. The problem is a TLR/ ATR weapons rack can only carry a maximum of 6 LGR missiles but we need it to carry 8. The current workaround is to change the Vikhr launching tubes to a rocket pod (RP) which allows you to carry 8. Unfortunately even though the missiles in the rocket pod are laser guided and track to a laser designated target, the HUD symbology displayed is that of an unguided rocket pod. Not only that but the TV screen in the cockpit will not show the lased designated image. There are models of both 6 and 8 tube pods so I have made both at this stage. So you can have the correct 8 tube load of Vikhr LGR rockets that display incorrect HUD symbology and no cockpit TV screen target image. Or you can have an incorrect 6 tube load of LGR missiles that display the correct HUD and cockpit TV screen symbology/ images. 6 tubes: 8 tubes:
  2. Awesome!!! That single seat F-4E would make a good F-4E(F) the proposed single-seat simplified version of F-4E for the German Air Force before they changed to the F-4F. Is it a LOD modification or just cleaver .INI and texture editing?
  3. Nice work with both Av-8 Packs! Where can we find the BRU42A and BRU42A_I? I have checked your weapons packs but its not there.... Cheers, Dan.
  4. It's 20 past midnight here in New Zealand so it's officially Christmas here. Have a great day guys and stay safe. I'm working the night shift but I'll be home first thing to spend the day with my wife and kids. It's been a crazy shift so far we have had to serious head on crashes and had to cut the drivers out of both. Then two cardiac arrests one after the other! Finally managed to grab a shower and hopefully a few hours sleep. So keep safe everyone especially if your traveling and enjoy your loved ones tomorrow. There's a few people out there who won't get to.
  5. Who has Star Wars Tickets?

    Just got back from it an wow! They did it justice! Wide open for a sequel to...
  6. The 'Boys from Syracuse' nailing Iraqi armour with their trial 30mm GPU-5/A Pave Claw pods during the opening days of Desert Storm.
  7. From what I can find on Google the active homing version of the R-27 AA-10 Alamo was never actually produced and put into service. But I was watching a recent RT video clip on you tube about the SU-34 now being armed with air-to-air ordnance over Syria which suggests otherwise. The reporter does a brief speal on each missile and when he talks about the R-27 he states is a fire and forget missile or something to that effect. So for a R-27 to be fire and forget it must be the active homing variety (R-27EA) and not the SAHM R-27ER? What do you guys think?
  8. Who has Star Wars Tickets?

    Taking my son for his 8th birthday (25th of December!) first thing next week.
  9. Modern RAF Smart Bombs

    Version

    518 downloads

    Modern RAF Smart Bombs. Includes: -Enhanced Paveway II -Enhanced Paveway III -Paveway IV In order to simulate the fact that these weapons can be either GPS or laser guided depending on what the aircrew decide before dropping them I have included two of each type. One is GPS guided and the other is laser guided. On my RAF aircraft (GR4, GR7, GR9 and Typhoon) that use these bombs I have used the loadout.ini file to load a mix of GPS and laser guided versions of the same bomb to imitate that flexability in the air. Credit goes to 331KillerBee for his Ordnance Shop II where these weapons have been modified from. Drop the files into your weapons folder to install, easy as that.
  10. I have noticed the the odd add on aircraft that will slowly rotate left or right in one direction when stationary on the runway before takeoff. It will do this with no throttle applied. When you try and take off there will be an initial pull in that discretion. The pull is more pronounced if you let auto pilot take off. Any ideas why? I have pored over the data.ini to figure out why to no avail.
  11. Su-39 and F-35A. Su-39 is the worst and is the one I am trying to fix to make a Su-25T. I have checked the engine thrust co-ordinates but they are symmetrical. All the landing gear statements except the rolling radius I have changed match the SF2 Su-25. I will now check the wing data etc.
  12. Cheers guys, don't think we're going to get a hard and fast answer on this one lol
  13. What If...

    Nice, doing 'what ifs' is one of the best aspects of SF2 I reakon
  14. It's the Alamo E but it is externally identical to the R-27ER Alamo C as it simply had the R-77 seaker head in place of the SAHM Alamo C head.
  15. ВВС РОССИИ SU-25SM somewhere over Syria...
  16. Does anyone have a decal or template with the Russian Air force writing that seems to be on all the tail fins of todays Russian fighters?
  17. That's the it, VVS RUSSIA in Cyrillic. Thanks will download tonight after work
  18. Version 1.0

    363 downloads

    'What if' F/A-16C Blk 30/32 CAS Vipers Background: In the 1980's, the USAF started setting aside F-16s for the planned A-16 modification, a dedicated CAS version. In 1989, the designation block 60 was reserved for the A-16. The A-16 Block 60 was to be equipped with a 30 mm cannon. This project failed because the 30 mm gun would heat up and singe the inner components of the left fuselage. The Block 60 did not go into production and the A-16 became wrapped up in the debate about close CAS. The supporters of the A-16 project wanted the USAF to replace its A-10A Thunderbolt with A-16's, arguing that the A-10 was too slow to survive above a high-tech battlefield. Detractors argued that the A-16 had insufficient range and load-carrying capability to make an effective attack aircraft, and, in addition, it would be too vulnerable to enemy anti-aircraft fire. However the USAF was ordered to retain two wings of A-10 aircraft for the CAS mission. No order for the A-16 was ever placed. When the USAF was forced to opt for the A-10 instead of the A-16, the decision was made to retrofit up to 400 existing Block30/32 F-16C/D's with new equipment to perform the CAS and BAI (Battlefield Air Interdiction) missions, effectively killing the A-16 program. Modifications would include a GPS, Digital Terrain System, system hardening, modular mission computer, and an Automatic Target Handoff System. A prototype Block 30 was based at Shaw AFB and went through numerous physical adjustments. Official designation, was to be F/A-16. In January 1992, this plan too was abandoned in favor of using LANTIRN Block40/42 F-16C/D's. The USAF was reluctant to let the idea of a dedicated CAS F-16 go, and planned to replace its A-10's with F-16s fitted with a version of the Warthog's Avenger cannon. In November 1988, the 174th TFW New York ANG transited from the A-10A to the F-16A/B block 10, becoming the first unit to operate the F-16 in a CAS support role. During Desert Storm, their F-16A/B aircraft were equipped with the GPU-5/A Pave Claw pod on the centerline station. If the tests were successful, there were plans for a fleet of F/A-16C's with the same armament. To demonstrate the concept, the AF installed Pave Penny avionics, 30mm gun pods and European One paint jobs on 7 F-16C's. A single F-16D was given similar treatment with a Falcon Eye system as well. These aircraft flew from Nellis with the 'WA' tailcode. The F-16s from the 174th were deployed to the Persian Gulf during Desert Storm, but the project proved to be a miserable failure. Precision aiming was impossible for several reasons: • The pylon mount isn't as steady as the A-10's rigid mounting; • The F-16 flies much faster than an A-10, giving the pilots too little time approaching the target; • Firing the gun shook the aircraft harshly and made it impossible to control; • Essential CCIP (continuously computed impact point) software was unavailable. Pilots ended up using the gun as an area effect weapon, spraying multiple targets with ammunition, producing an effect rather like a cluster bomb. It took only a couple of days of this before they gave up, unbolted the gun pods, and went back to dropping cluster bombs. And so the F/A-16C plan was quietly forgotten.... BUT...... What if the project was a success? And so I give you the F/A-16C Blk 30/32 CAS Viper: 3 separate aircraft: - F/A-16C Block 30 1986- 1993 (1986 Service date makes it NATO Fighters 5 compatible, 1991 would be more realistic.) - F/A-16C Block 32 1993- 2003 - F/A-16CM Block 30 2003+ Unique CAS loadouts including the Pave Claw 30mm gun pods. There are heaps of extra loadouts if you have a look with the mission editor. All F/A-16C have the Falcon Eye FLIR pod on the nose in front of the canopy. It was slaved to the pilot’s helmet which had a helmet mounted display. Basically anywhere the pilot looked at night he would see the world in infrared. It was also the West’s first HMD with targeting information, weapons cueing, navigation and terrain avoidance ques. There are Euro-one style skins for the early F/A-16C, the latter blocks two have a mix of normal F-16 camo skins and a lighter ghost grey style like on the A-10. To install: Drop into your C:\Users\xxxxxx\Saved Games\ThirdWire\StrikeFighters XXXXX Included in the folder 'NATO Fighters 5' is a modified 1986 Red Storm NATO Fighters campaign that includes the F/A-16. It will show up as an extra campaign and not affect any of the NATO Fighters 5 campaigns. Credits: - The Viper Team for their stunning viper packs. - Ravenclaw_007 for his new weapon packs. - Migbuster fot the F-16C skin templates. - Nato Fighters Team. Enjoy, Dan (dtmdragon) Combat Ace fair use agreement applies.
  19. F/A-16C Block 30 CAS Viper F/A-16C Block 32 CAS Viper F/A-16CM Block 30 CAS Viper
  20. File Name: 'What if' F/A-16C Blk 30/32 CAS Vipers File Submitter: dtmdragon File Submitted: 02 December 2015 File Category: What If Hangar 'What if' F/A-16C Blk 30/32 CAS Vipers Background: In the 1980's, the USAF started setting aside F-16s for the planned A-16 modification, a dedicated CAS version. In 1989, the designation block 60 was reserved for the A-16. The A-16 Block 60 was to be equipped with a 30 mm cannon. This project failed because the 30 mm gun would heat up and singe the inner components of the left fuselage. The Block 60 did not go into production and the A-16 became wrapped up in the debate about close CAS. The supporters of the A-16 project wanted the USAF to replace its A-10A Thunderbolt with A-16's, arguing that the A-10 was too slow to survive above a high-tech battlefield. Detractors argued that the A-16 had insufficient range and load-carrying capability to make an effective attack aircraft, and, in addition, it would be too vulnerable to enemy anti-aircraft fire. However the USAF was ordered to retain two wings of A-10 aircraft for the CAS mission. No order for the A-16 was ever placed. When the USAF was forced to opt for the A-10 instead of the A-16, the decision was made to retrofit up to 400 existing Block30/32 F-16C/D's with new equipment to perform the CAS and BAI (Battlefield Air Interdiction) missions, effectively killing the A-16 program. Modifications would include a GPS, Digital Terrain System, system hardening, modular mission computer, and an Automatic Target Handoff System. A prototype Block 30 was based at Shaw AFB and went through numerous physical adjustments. Official designation, was to be F/A-16. In January 1992, this plan too was abandoned in favor of using LANTIRN Block40/42 F-16C/D's. The USAF was reluctant to let the idea of a dedicated CAS F-16 go, and planned to replace its A-10's with F-16s fitted with a version of the Warthog's Avenger cannon. In November 1988, the 174th TFW New York ANG transited from the A-10A to the F-16A/B block 10, becoming the first unit to operate the F-16 in a CAS support role. During Desert Storm, their F-16A/B aircraft were equipped with the GPU-5/A Pave Claw pod on the centerline station. If the tests were successful, there were plans for a fleet of F/A-16C's with the same armament. To demonstrate the concept, the AF installed Pave Penny avionics, 30mm gun pods and European One paint jobs on 7 F-16C's. A single F-16D was given similar treatment with a Falcon Eye system as well. These aircraft flew from Nellis with the 'WA' tailcode. The F-16s from the 174th were deployed to the Persian Gulf during Desert Storm, but the project proved to be a miserable failure. Precision aiming was impossible for several reasons: • The pylon mount isn't as steady as the A-10's rigid mounting; • The F-16 flies much faster than an A-10, giving the pilots too little time approaching the target; • Firing the gun shook the aircraft harshly and made it impossible to control; • Essential CCIP (continuously computed impact point) software was unavailable. Pilots ended up using the gun as an area effect weapon, spraying multiple targets with ammunition, producing an effect rather like a cluster bomb. It took only a couple of days of this before they gave up, unbolted the gun pods, and went back to dropping cluster bombs. And so the F/A-16C plan was quietly forgotten.... BUT...... What if the project was a success? And so I give you the F/A-16C Blk 30/32 CAS Viper: 3 separate aircraft: - F/A-16C Block 30 1986- 1993 (1986 Service date makes it NATO Fighters 5 compatible, 1991 would be more realistic.) - F/A-16C Block 32 1993- 2003 - F/A-16CM Block 30 2003+ Unique CAS loadouts including the Pave Claw 30mm gun pods. There are heaps of extra loadouts if you have a look with the mission editor. All F/A-16C have the Falcon Eye FLIR pod on the nose in front of the canopy. It was slaved to the pilot’s helmet which had a helmet mounted display. Basically anywhere the pilot looked at night he would see the world in infrared. It was also the West’s first HMD with targeting information, weapons cueing, navigation and terrain avoidance ques. There are Euro-one style skins for the early F/A-16C, the latter blocks two have a mix of normal F-16 camo skins and a lighter ghost grey style like on the A-10. To install: Drop into your C:\Users\xxxxxx\Saved Games\ThirdWire\StrikeFighters XXXXX Included in the folder 'NATO Fighters 5' is a modified 1986 Red Storm NATO Fighters campaign that includes the F/A-16. It will show up as an extra campaign and not affect any of the NATO Fighters 5 campaigns. Credits: - The Viper Team for their stunning viper packs. - Ravenclaw_007 for his new weapon packs. - Migbuster fot the F-16C skin templates. - Nato Fighters Team. Enjoy, Dan (dtmdragon) Combat Ace fair use agreement applies. Click here to download this file
×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..