FastCargo

I've heard the same thing from some buds who are former F-14 pilots. The Viper is simply vicious in a close fight. I'd imagine a Mirage 2000-5 would be about the same in close. During Red Flag, the M2k5 pilots were pretty much even in close in fights with the OPFOR Vipers. Which made for some funny ACMI reviews...'Wagon train' dogfights... FastCargo

Oh THAT's awesome! My wife would love that billboard. Hey, she loves Bambi...with just the right amount of demi-glaus. FastCargo

Download it from Thirdwire directly. www.thirdwire.com FastCargo

Addons complete...just need to make a readme (installation will be not be as easy as your normal drag and drop) and upload. Also, for those who haven't figured it out yet...these are modifications of existing aircraft...not new aircraft. FastCargo

Uh yeah, it was a nuclear bomb and a fuel tank. FastCargo

Make sure these lines are in your aircraftobject.ini: [Control070] Name=ANIMATION_1 Type=SINGLE_EVENT [Control071] Name=ANIMATION_2 Type=SINGLE_EVENT [Control072] Name=ANIMATION_3 Type=SINGLE_EVENT [Control073] Name=ANIMATION_4 Type=SINGLE_EVENT [Control074] Name=ANIMATION_5 Type=SINGLE_EVENT [Control075] Name=ANIMATION_6 Type=SINGLE_EVENT [Control076] Name=ANIMATION_7 Type=SINGLE_EVENT [Control077] Name=ANIMATION_8 Type=SINGLE_EVENT [Control078] Name=ANIMATION_9 Type=SINGLE_EVENT [Control079] Name=ANIMATION_10 Type=SINGLE_EVENT That fixes the problem. FastCargo

Actually, I don't think a dedicated discussion would do much good. First, statistics can be misleading, especially by those quoting them. Certain things aren't subject to debate because there are hard numbers for them (unclassified). Things like gimbal limits, FOV, etc. What is subject to debate are reliability numbers, rejection capabilities, most of which are classified, and therefore, speculative. And in the real world, depend on a multitude of factors (target and shooter factors, MX issues, updates, etc). The ONLY way to get reliable info on such things would be to test fire HUNDREDS of missiles in dozens of situations to get weighed averages. That ain't going to happen. I find debates like this are along the lines of 'Which is the best blah, blah, blah'. Ultimately all sound and fury, signifying nothing. FastCargo

Knew a pilot who actually practiced this back in the 'Chrome Dome' days in B-47s. That's one thing I wish we had in SF, weapons that don't detonate right when they hit the ground... FastCargo

Or you could use D-Fend, which makes DOSbox much easier to use... FastCargo

Yo! Ex-SIOP warrior here... SAC was good for the SIOP...but not so good in the post-Cold War world. The mentality was too inflexible for implementing post-Cold War conventional bomber operations. FastCargo

One thing I need to clarify. My mod is for the visual part of the pylon only. You still need to make the weapon stations where your weapons (not the 'pylons') will hang from as per Capuns tutorial. http://forum.combatace.com/index.php?showtopic=24863 FastCargo

Okay, two disclaimers to the method I'm going to show here. 1) It does not work for moving pylons...so you still can't fix the Tornado Sidewinder stations... 2) You can't mount the pylons at angles...it always assumes zeros on all angles. 3) It MAY increase your vulnerability to weapons fire...MAY. In addition it has the same limitations as the 'weapon station' methods (will be color of the bitmap assigned to the pylon LOD file, does not change with aircraft skin change, etc) It's actually very simple. Make a new pilot position. An example from the A-4L_data.ini. First, determine what you want to call the new mounting area...for the A-4L, I decided to call it the AvionicsHump Second, add this line (as an example) to a component section (Nose, Fuselage, etc): SystemName[XXX]=AvionicsHump Now, go to the Pilot section and add the following: [AvionicsHump] SystemType=PILOT_COCKPIT <---- Will always be this Position=0.0,3.82,0.825 <---- Coordinates where you want it to show PilotModelName=A4LAH <---- Model name of the pylon/hump/canard SeatModelName= SeatPosition= MinExtentPosition=0.0,3.82,0.825 <----- I suspect these lines define the 'hit box'. So I made the lines MaxExtentPosition=0.0,3.82,0.825 <----- equal the position to minimize the hit box (hopefully make it zero) CanopyNodeName=Fuselage <---- Section of the aircraft to 'attach' the pylon/hump/canard to...the idea is that if that node is destroyed, the addon will vanish SeatID=2 <---- Used to determine which pilot model 'disappears' when in cockpit view. Make sure it's something other than SeatID=1 Save the new data.ini. Make sure the LOD of your hump/pylon/canards is in the Objects/Aircraft directory. That's it. Advantages of this technique: Idiot proof...you can't unselect them, you can't jettison them, they will ALWAYS load with your aircraft. Don't need to make weapondata.ini entries (no fake weapons). As a bonus, no other aircraft could use them either. Tested on my fake Su-33 and A-4L...works beautifully and I haven't seen any issues so far. FastCargo

Actually, i've found a better way to add pylons...will reveal as soon as I get time today. FastCargo

I prefer "The Venture Brothers"... Brock Sampson rocks! FastCargo

Airbus (or any modern airliner)...no question. Plenty of extra fuel, accurate autopilot approaches (if necessary), plenty of excess extra thrust if you lose an engine, cleared down to 600 RVR, 2 man crew great for busy times during peak arrival periods. Sorry, but when you're number 10 for the approach, the last thing I want to be in is an aircraft that's min fuel as soon as you takeoff. Especially in the NorthEast... Hey, pulling Gs, looking good, doing formation, etc...the T-38 is a great aircraft. Instrument flying on the other hand...it's primitive compared to the modern airliner. FastCargo

Blackhawk, The Groundobjectsdata.ini became obsolete when one of the more recent patches came out since Ground Objects are now arranged like aircraft. FastCargo

The X-29 was built from F-5 parts, not the F-20. FastCargo