FastCargo

Also, like the famous 'F-22 in the F-18 sights' photo, context is everything. There is no information on what was going on in those pics. Now, I'm NOT saying they weren't valid 'kills', but until you know the full story, you don't know dick. FC

Sure it can...Google 'F-15 ACTIVE'. http://www.wikipedia.org/wiki/McDonnell_Douglas_F-15_STOL/MTD FC

Trust me, it wasn't magical...it was practice, and putting the aircraft in preset parameters to make the drop work. Also, for all intents, you were aiming with a shotgun, not with a sniper rifle. The idea was to put the center of your stick on your target...so you could have slop in your equations. Here's an interesting article...take a look at the CEP numbers: http://goliath.ecnext.com/coms2/gi_0199-5320632/Radar-bombing-during-Rolling-Thunder.html http://findarticles.com/p/articles/mi_hb3101/is_2_53/ai_n29269246/pg_4/?tag=content;col1 CEPs were regularly in the 3000 foot range. FC

I remember doing almost the exact same spin recovery procedure in the mighty T-37...pretty docile spinner if I remember correctly. Fun stuff! FC

If you can see the stock weapons, but not the modded weapons, your weapondata.ini and weapondata.dat files are being saved in the wrong place. Both files should end up in the Objects/Weapons directory. FC

I am the creator of the moving map display for the F-15C. If you look at the cockpit.ini file, this is the reference: That is as much control as I have. You find something different, you let me know. FC

What makes this so hard to believe? Perhaps you should remember the story of Gordon Cooper. That aside, lets talk about a few things. First, I didn't drop bombs, I dropped 'sticks'. We bombed areas, large targets, runways, etc. We dropped entire bays...or had other weapons where accuracy to 10s of feet was irrelevant. However, we frequently practiced with single bombs, even BDU-33s (which looks slightly wierd...dropping a single coffee can out of a intercontinental bomber). And we found we were simply better than the computer...on average. There were several reasons for this: 1) In a perfect day, in a perfect test situation, computers could do it better. However, there was rarely a perfect day where everything was running at 100%. Even slight degradations in perceived inputs could result in significant errors. For a cold war computer, with less computing power than your cell phone, designed to drop weapons with yields in the kiloton range, this wasn't an issue. There were times in terminal manuvering phase that the computer simply couldn't keep up with the calculations....vs a good OSO who had already anticipated the changes would and get the weapon out on time. 2) OSOs and crews in general did this stuff in their sleep. We constantly competed against each other, and kept trying to find ways to make the other crews buy beer. You would be surprised how good you can get when you get free beer. I knew guys who would consult with MX to determine the exact amount of time it look for all the relays to fire after the button was pressed. One guy in particular even went so far as to determine how far the button had to be pressed...that's a little hardcore... 3) The 'fat finger/GIGO' factor. This still is a problem today of an error creeping into the computer by accident. The computer is dumb, and simply drops when the conditions were met. Verses an operator who could look at it, realize it wasn't right based his old school calculations, and drops on time. 4) If no one has figured it out by now, low altitude level bombing of a point target is highly inaccurate on the best of days...even if everything is 100%. All the possible interactions the weapon had after it was released meant that you always had a fudge factor. Even an article either you or streakeagle posted talking about the accuracy of radar bombing talked about the accuracy using radar was quite good...if you were using a full set of weapons to bomb an area. Accuracies now were simply not feasible back then. FC

Dude...you really gotta just let this go. I did this for real...the challenge was in everything BUT letting the computer drop the weapon for you. It's just not that interesting. You want to give yourself a challenge? Do the math at the front end, then try to hit the parameters while you're trying to survive in order to get that shack...especially in a non-fighter type aircraft. FC

Sacrilege!!! I was never a BUFF guy! FC

Read my previous reply for the probable answer. FC

Some of the HUD and radar files may be located in the flightdata or missiondata CAT files located in the Flight folder. Look in the avionics.ini file for the Netz to find the names of the files you need. Those files must be in the Cockpit folder to work. And a note...we cannot help you correctly if you do not provide all the information needed. ANYTHING other than a dead bone stock install requires we know the details of the mod...otherwise, it wastes everyone's time...including yours. FC

Could be it throws the CG farther forward than the original designers anticipated. FC

First, stop yelling. Second, start here: http://combatace.com/topic/43234-how-to-make-a-sf2-aircraftweapon-useable-in-gen-1-thirdwire-sims/ If you cannot understand the statements at the beginning, start here: http://combatace.com/topic/26293-basic-directory-structure-of-a-generation-1-thirdwire-sim/ http://combatace.com/topic/25845-basic-definition-of-terms/ http://combatace.com/topic/26456-acronyms-for-the-thirdwire-series-of-sims/ http://combatace.com/topic/32706-using-skypats-cat-extraction-tool/ http://combatace.com/topic/9323-adding-weapons-to-sfwovwoe-a-tutorial/ http://combatace.com/topic/33279-septoct-2008-patch-weapons-issue-fix/ FC

The amount of the map that shows up in the cockpit is hardcoded in the LOD and cannot be changed via ini (as far as I know). FC

Increase the resolution of the map the terrain is using. Either located in the terrain CAT file or in the Terrain directory for 3rd party terrains. FC

Too many zeros... FC

Okay, the fact that you are getting the stock weapons means that your modded Weapondata.dat file is not placed at the right location. Where is the modded weapondata.dat file? It should be in your Objects/Weapons directory. Confirm that it is the modded weapondata.dat file, not the stock file...sometimes the weapondata editor will save the modded weapondata.dat file in an unexpected location. FC

Okay. Well, I just reinstalled my Oct 08 bone stock install on a Win7 64 bit computer. It ran just fine, all modes seemed to work just fine. Have you tried to reinstall a stock WOI install to see if that works? FC

Wait...you changed the Avionics from 60 to 70? The STOCK F-16A from WOI is Avionics70 from the start. Are you sure you aren't talking about the Mirage Factory F-16A? FC

You shouldn't be seeing any issues then...unless the stock model is broken or it got modded in someway. FC

Doesn't WOI come with an F-16A Netz as a TW model? FC

Ahhhhh yeah...sounds tasty!

Testing...testing... FC

Story of Commander Hubbard's MiG-17 kill in Vietnam: http://books.google.ca/books?id=-v7HMpRYYXUC&pg=PA149&lpg=PA149&dq=Ray+Hubbard,+F-8,+Crusader&source=bl&ots=3wBs5pxjuA&sig=3Cuv5IPufL7NOcm0inFK7IuGnvM&hl=en&ei=9apLTJzeKcTtnQe_iYGwDQ&sa=X&oi=book_result&ct=result&resnum=4&ved=0CB0Q6AEwAw#v=onepage&q&f=false If the link doesn't work, it's page 149 in the book MiG Master: The Story of the F-8 Crusader. Also this link: http://books.google.ca/books?id=87Eceo17wfIC&pg=PA107&lpg=PA107&dq=%22Ray+G.+%22Tim%22+Hubbard%22&source=bl&ots=hhF_0C16qV&sig=1902_X-34Gba98OS-WbaMb1iBt4&hl=en&ei=Lq5LTOqWOtKInQeupumvDQ&sa=X&oi=book_result&ct=result&resnum=1&ved=0CBMQ6AEwAA#v=onepage&q=%22Ray%20G.%20%22Tim%22%20Hubbard%22&f=false Page 107 in the book "F-8 Crusader units of the Vietnam War". Sounds like he has at least one confirmed kill and may have gotten a second that he wasn't credited for. http://collections.naval.aviation.museum/emuwebdoncoms/pages/doncoms/Display.php?irn=16041150&QueryPage=%2Femuwebdoncoms%2Fpages%2Fcollections%2FQuery.php.orig Portrait of LCDR Hubbard. Anyone know any organizations this person can go to to ask about LCDR Hubbard? FC