Jump to content

Sundowner

+MODDER
  • Content count

    2,162
  • Joined

  • Last visited

  • Days Won

    122

Everything posted by Sundowner

  1. Cockpit background comms sounds. View File This is a little in cockpit sound mod I've been using to replace the stock sounds, I feel it adds a little extra immersion by adding background radio comms to the cockpit environment.. With the appropriate comms you can set up virtually any aircraft from any nation to play background sounds in the language of your choice, this pack uses RAF/US comms but other languages can easily be added by the end user following my examples. Sorry , but reading the readme is a must with this mod. You WILL need to BACKUP some of your files first. !! Submitter Sundowner Submitted 02/22/2017 Category In Game Sounds  
  2. This bird took forever to get airborne with this little lot on board.....
  3. tsr2_2017

    It appears I missed out some sounds from the pack..... Just add to your Sounds folder... Sounds.7z
  4. View File tsr2_2017 TSR2...........The Alternative Story 6 April 1965 was set to be a sad day for the British aircraft industry, the cancellation of the TSR2 was imminent, the costs were spiralling and the project was slipping further backwards, the project had its supportures but its biggest enenmies were those in power. But, on the morning of the 5th April something nobody saw coming happened, something that if it turned out to be true could save the entire project and thousands of jobs in the UK avation industry, indeed ministers in parliment were astonished to say the least, if the project was killed off now the British public would be furious , questions would be asked and answeres would be demanded, the government had some serious decisions to make, and quickly for the offer was for 24 hours only ! So what had happened ? Well at 9:45 GMT the British Aircraft Corporation were thrown a lifeline, an American company had stepped in with an offer to see the project through, they were willing to finance all that had been spent on the project so far, this would mean that all the British tax payers money was safe, they were willing to pay back to the British government what they had spent on development costs so far. In return they wanted the British to basically start again with the project financially, they would work with BAC to carry out further development and testing on a 50/50 cost basis , supplying their own expertise as an aid to the programme. So, essentially the TSR2 project could be saved, from now on the cost would only be half of the projected costs , somebody wanted in on this venture badly, but who and why ? April 6th was the day the axe was supposed to fall on the TSR2, government ministers shuffled in their seats as the announcement was due to be made, silence fell , the announcement was short. "The TSR2 Project WILL Continue", there were gasps of amazement amid cheers of joy. Over the next few hours many questions were asked, some answered, some not, but the main one was WHO ?? Enter onto the scene one of the worlds if not the worlds most famous aircraft manufactures, Boeing Yes, Boeing, the company famous for its outstanding range of airliners and bomber aircraft. Boeing saw the potential of the TSR2 programme and whilst traditionally being a manufacturer of large designs it wanted a smaller tactical bomber/attack aircraft than its previous offerings. The war in Veitnam was looming and rather than starting from scratch the wise men at the company saw that the combined companies that make up the British Aircraft Corporation had the expertise to pull the project through , they just needed access to more money, money Boeing were willing to commit. Boeing would not only help financially, they wanted to help solve the current issues and take development further, indeed they wanted to market the project world wide ! The flight testing carried on at quite a pace, problems were found and solved, with there not being as much red tape and politics to go through as previously progress was finally being made. To get things moving and keep politicions quiet the first batch of the BAC/Boeing Thunderstrike GR1A as it was to be known entered service with the RAF on December 1st 1966 and the RCAF taking its aircraft the following year. Only 100 of this version were produced 60 for the RAF and 40 for the RCAF. The GR1A was hurried into service so that the BAC/Boeing designers could address some of the types more seroius problems. From day one the TSR2 had been dogged by the extremely tight fit of its engines, airframes were matched to engines and a single engine removal to take 60+ hours, obviously this could not continue, there was no way the airframe could be widened externally, the only sensible answer was to get rid of the bombay and move the engines slightly closer together, the airframe was strengthened for under fuselage pylons and a fixed 700 gallon tank in its place also doubling up as a heatsink for gearboxes and the like, this was a trade of in all directions but as the original design required a removeable 680 gallon tank in the bombay and an optional 1000 gallon panier tank it was considered the best way forward. The next issue was with the main gear, right through the testing phase it had proved troublesome and prone to slapping when the first wheel made contact with the runway, numerous fixes had been tried but even now the in service GR1A's were still having issues. Again Boeing's design team came up with the solution, it was stunningly simple ! They got rid of the tandem swivelling upon retraction complicated system for a more conventual single leg with a pair of wheels attached to it, the same alloys as used on the B52 main gears were used as it was considerably stronger the the British equivalent. The improvements implemented over time were immense , just about every single part of the aircraft and its systems were changed in someway , only the basic shape of the original TSR2 remained the same. Even while the original GR1A's were being delivered the next model was starting to enter the production phase, this time the aircraft had gained two 30mm Aden cannon under the nose, the original proposal for a side ways looking radar had been abandoned soon after Boeing got involved [this was now installed into the reconnaisance pod] so the cannons used up the space that had been gained by its removal. The next design change was probably the most ambitious , Boeing wanted something that was never on the cards for the TSR2 project, they wanted a navalised version , something to compete against the RA-5C Vigilante, the British design team were astounded by this, but Boeing who had several aircraft for evaluation and flight testing had now got their own production line running, with all this extra capacity anything could now be possible ! The modifications to the bombay area and fitting of under fuselage pylons had inherantly strengthened the whole underside of the aircraft, a "full strength" arrestor hook had been installed from day one instead of the original proposal for an "one time" emergency type, the fin was essentially cut in half to make it fold for carrier stowage. Production of all the navalised versions was to take place at Boeings own plant, initally the US Navy were very reluctant to even trial the idea of a British jet on their carriers, but Boeing's persistance paid off and the Navy placed orders for two versions ; an all out attack variant and a dedicated reconnasiance platform. For the Marines it was a no brainer, the aircraft was perfect for their "in country" mud moving roll. It should be noted that all these US aircraft and indeed the Export version that followed all used US built Pratt and Whitney engines, US sourced ECM and countermeasure systems and carried either two Browning 20mm cannon or the 20mm Vulcan "gatling gun" Export customers for these US built versions included Isreal and Austrailia among others. Meanwhile back in the UK the RAF versions continued to flourish, changes were generally small and more inline with keeping up with current upgrades to software and such, the biggest problem was with there being so many versions in service at the same time, engines grew ever more powerful even though the design had never been short of power, a dog fighter it was not but down low at high speed nothing came close. The terrain following radar was a world beater, the ride was stable down low and the wide angle HUD made sure "head down" time was virtually not needed. South Africa, India, Saudi Arabia and Canada were among the UK spec exports. Once the Royal Navy accurired its Malta Class carriers it too became users, these carriers and these aircraft being the biggest the Royal Navy had ever operated. The one thing that did come about from the navalised versions was the fitting of cannards to the nose section , roughly in line with the pilots position. These were fitted to cure a nose down tendancy in certain circumstances when taking off from a carrier, infact several US Navy aircraft were lost and all remaining aircraft were only to be flown by senior pilots with 2000 hours or more. Two small pitot tubes were positioned in front of each intake to limit the angle of the canard if the airflow became close to intake surge limits. Pilots reported a general feeling of more stability under weapon launch conditions and the RAF's GR7 version came with them as standard fitment........if only they had been discovered earlier. The GR7 was basically the RAF's ultimate Thunderstrike, the original internal ECM fit was very limited in effectiveness and difficult to upgrade so after many years of trying different configurations of US built pods the design team at BAC eventually came up with two purpose built pods which could be installed onto the wingtips replacing the two IRM stations, the pods could be removed in less than one hour making upgrading easier and as a bonus they were more aerodynamic and didnt use up a valuable wing pylon. The complete number of versions and operators as well as actual combat accounts would be the topic of several volumes, far too much for this brief account of an aircraft which was destined never to be if it was not for a last minute gamble from Boeing. After a total production run from the two factories of 4500 aircraft I think it is safe to say the gamble paid off. TSR2_2017 As you've probably already realised the TSR2 is a bit of a favourite of mine, So.....what's new this time you ask ? More versions, more stuff remapped, more model tweaks, new cockpits and still more to do. Half the fun is seeing if you can find what's changed from the previous releases [if you had them] This is one aircraft I will probably never stop tweaking so I thought I'd better get what I have so far realeased. For those of you that already have the older version I can't stress enough that you should move them somewhere safe in case you dont like these. Just letting them overwrite is NOT a good idea as you will screw up both sets. Installation is just a case of copying everything FROM the TO_MOD_FOLDER TO your modded game install. Just remember this is a What If, I'm not really concerned about what would have been feasable and what would'nt, we will never know so I've just gone on what I would like to see. Enjoy Sundowner [Ant] 17/09/2017 .......NOT TO BE USED IN ANY PAYWARE OR RE-RELEASED WITHOUT MY PERMISSION.... Submitter Sundowner Submitted 09/17/2017 Category What If Hangar  
  5. F-4K_TMF_OCT26_2015

    Version

    441 downloads

    This F-4K from the Mirage Factory will replace all previous versions as so many changes have been made since the last release......please read the readme. BEFORE downloading this file you will need to have the ThirdWire F-4K DLC installed as this mod aircraft uses the TW cockpits, if not it just wont work. All markings except serial numbers/letters are painted on......if you don't like this style of skinning then don't download it. Tested on a fully merged July 13 install. Please be aware that this is a Mirage Factory product so no modifications to be uploaded without permission please.
  6. Some days you cant even get off the ground.....
  7. Some sad news regarding a former modder

    Blimey, I worked on lots of stuff with Mike, although we never met in person he was a great bloke. RIP Mike
  8. It's not too hard to get it working in SF2
  9. ..........or maybe they do........
  10. I'd really like to know what all these different Object Type and Shape boxes actually mean or do, then how the hell do you work out the texture co -ordinates ? I've read the Terrain editor thread and so many others sooooo many times over the years but no where does any body explain what these things actually do? Go on, somebody make me feel really stupid now.
  11. Now, where have I seen something like this before ????
  12. When they become invisible it means that you've reached the max amount the game will allow.
  13. Hmmm, I must be doing something wrong because I dont have the planing map options dialog.
  14. Well, best get posting then....... Heading down the Mu Gia pass....... Joy ride.....
  15. There are multiple models, all based on a basic 300 series fuselage but then we did some others with bits added here and there.....well all over the place really, I'm pretty sure there's a shorter version......I'd need to do some digging but I will have all the original max files somewhere.
  16. Interesting twist to this, just as a trial I moved ALL the TOD's out of the terrain folder but left GroundObjectDetail=3 as is. Back in game we had clouds back down to 5500-6000 feet again. I then put back just ONE TOD that contained trees........clouds now back to 12000 feet again. Like I say this stuff is beyond me but maybe if Mue or Stary were still about they might be able to shed a little light on the subject. Single TOD being used.
  17. Just resurrecting an old thread here, quite by accident last night I noticed that the clouds are now linked to the GroundObjectDetail= setting, I know its probably been known for ages but it appears that any setting that uses the Terrain TOD's shoves the cloud base up to 10-12,000 feet where as no TOD's at all let it back down to about 5,500 - 6000 feet........has there ever been a workaround for this ? I do know it's to do with Z buffers and things way over my head...
×

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..