331Killerbee

Reasearch is the Key.....If it wasn't for Fubar512 pointing Me in the right direction on Ground Radar Info, I'd be lost. There's alot of Sites out there with good Information on Aircraft ECM Jamming Equipment and Pods out there. Good Reasearch produces Good Mod results in this Game..... 331KillerBee Not that I know of.....Although AI has been upgraded over the Years, It's still limited in what it will react to....There is no "Automatic Release" Mode for CM that I know of....

Yep.....Took two Weeks. One for SF2V. Another for SF2E....That's all Aircraft, Ground Radars and External Pods.....There's alot of them.... 331KB

AI ECM works as Fubar512 has stated. Once an Aircraft gets "Painted" it turns on either Onboard ECM, External ECM Pods or both. If One has set the Frequencys of the Radars and the Bands that the Pods or Onboard ECM is set to Jam in Game, Things get pretty interesting. BTW, One can find Radar Bandwiths in the "Knowledge Base" thanks to Fubar512 and other Contributers. I have this done in most My installs. In Linbacker II Campaign of SF2V, I sometimes have a EA-6A or EB-66B included with a Strike Package.......Once the Flight gets "Painted", The Jammer turns on it's "Music".....I watch the SAMs fly by with no threat. Does the same to FireCans. But Visual AAA still remains a Threat. 331KillerBee

In Your "Effects" Folder, You should have a File named "ShipSmokeEffect or ShipSmoke". Open it. In these Lines below, Make these Changes and see if You get a better Result. Entry in existing Effect .Ini: EmissionVolume=0.500000,0.500000,0.500000 Change to this: EmissionVolume=0.200000,0.200000,0.200000 See how it changes from there and tweak it to Your likeing. 331KillerBee

Hokum, I was TAD to Yeovilton in 1982 with RNS 8, 800, 801 and 809 Squadrons. I helped install SEAM Boxes on the Sidewinder Systems prior to the Falklands War. 331KillerBee

Since I'm leaving on a long Trip for a couple of Months Friday, I'd thought I share a Story to all of You about the Harrier Hovering that might interest Yall'. Being in VMA-331, We were the first Combat Squadron to stand up with the new AV-8B. One of our first Deployments was to MCB 29 Palms, CA. It was for a CAX (Combined Arms Exercise). CAX 2/86. A CAX has all the Elements of a MAGTF (Marine Air Ground Task Force). It has all the Units from Air, Ground and Supporting Arms involved. One Day, durning the Deployment, The Grunt Units assembled at the Flightline at the tempory built Airfield constructed at the Base for Air Operations. They were there to see a Demostration on the New Harrier and it's Capabilities. The Runway is 2500 Feet in Length. For the Hover Demostration for the Grunts, Two Harriers approched the end of the Runway at an Alitutde of about 250 Feet off the Deck and started their Hover. As both had achived Hover, One Aircraft rotated 180 Degrees in the Hover. Now Both Aircraft proceeded to position themselves 10 Feet Nose to Nose at about 250 Feet off the Deck. Then they proceeded to fly Nose to Nose in a Hover the length of the Runway. One Aircraft in foward Hover, One backward. That wasn't the amazing part. The Amazing Part was the fact that both Pilots did this Hover down the Runway with their Hands on the Canopies......... It's one of those Days in which I wish I had a Camera with Me........ Semper Fi! 331KillerBee

First of all this has been discused to death. As a person with first hand knowledge of the Harrier. I can tell you this. A "B" Model (Gr5-7) will take off VTO with a Combat Load with Empty Tanks. Durning OPVAL of the AV-8B with VX-5 at NAS Pax River, MD. It was done sucessfully a dozen times. But as Migbuster has stated, The Engine requires so much Water for this type of Operation. Just about every time it's done, The Engine has to be changed. The requirement to change an Engine in a Harrier contails alot. It means that Aircraft is in a "Down" Statis until the Change is made. But is a Capability. USMC Harriers have the ability to operate from "FOB's" that are just alittle larger than the size of a Tennis Court. The main reason One doesn't see Harriers do it. Or do it "Slicked" or with empty Tanks is COST. It cost for Engines to be reworked, Changed and the "Down Time" of the Aircraft factor in. The Rolls Royce Pegasus Engine is an expensive Componet of the Platform. The Engines from the "A-C" Models had to be sent back to the UK to be reworked back in the Old Days. Empty Tanks save Weight. The old "A-C" Models had to have a bolt-on IFR Probe Installed. Later on the "B" Model, The Marines required a Retractable IFR Probe. It's still Removeable, But comes as a part of the Airframe. The old "A" Model IFR Probes where an after thought. MCAS Cherry Point, NC has a Hover Pad that is made of Concrete in the Middle of the Base where two Runways intersect. VMAT-203 is the Harrier Trainning Squadron and is based there. The now operate AV-8B II Pluses and TAV-8B two seaters. They conduct Hover (VTO) every day at the base. It's part of the Trainning of every Marine Harrier Pilot to become familiar with this Operation. Also, VMAT-203 is the biggest user of RR Pegasus Engines in the Marine Corps due to this Trainning. Engines are changed every Day at 203. BTW, The TAV-8B has the same Engine as the AV-8B and can Take-Off Vertical. I wounder how much the extra Ejection Seat, Cockpit, Airframe Strech weighs? Engines are frequently changed aboard Ships (LPH-LHA-LHD's) because of high Stress these Engines go through durning STOL and VTOL Operations. The advent of the Ski-Ramp by the Brittish have helped eliminate alot of the Stress on Harrier Engines. This is in STO Operations and have been taken up by the Marines since the Falklands in 1982. The Marines deployed their first Ski-Ramp in Combat durning Desert Storm. Many in the Avation Community say that Landing a Aircraft on a Carrier by a Naval Aviator is the most Hair-Raising event one could do. Especially at Night. I differ from that Statement. I say, a VTL by a Marine Harrier Pilot at Night aboard a LHA or LHD is it..... It's bad enough that Hovering in normal conditions is Work Overload in the Cockpit. As one Pilot has described it as balancing a Elephant on the end of a Needle. Now, mulitply that by adding more Weight with External Stores and You have a Recipe for alot of Problems. The "B" is "Fly-by-Wire". The old "A's" were not. Conclusion: The early "A's" could do it, But the Gun Pods were empty of Ammo, Drop Tanks Empty. No other Ordnance. The only exception would be the Addition of LAU-7's on the Outboard Stations, Empty. No AIM-9's loaded. The Early Pegasus just didn't have enough "Emph!" (Thrust) in it...... AV-8B's could do it under Load, But You'd be changing the Engine after the Mission/Sortie is done. Water Injection Cooling is the Key. Durning Hover, The Water does two things, It boost Combustion and also Cools the Engine under high Stress use. One more Factor is that the Water Tank on the "B" is only so big. You need the Water to sustain Vertical Flight. Once the Water is gone, Thrust is reduced, Engine could seize up and Your Aircraft could fall from the Sky. Be Sure to throw Your Wallet out the Cockpit if You don't know where the Ejection Handle is..... An AV-8A/C can do it slick. No Ordnance of extra weight what-so-ever...... An AV-8B can do it........But is RARE. Semper Fi! 331KillerBee T/AV-8A/B/C Harrier Ordnanceman VMA-231 1979-80 VMAT-203 1980 VMA-542 1981 VMAT-203 1982-84 VX-5 1985 VMA-331 1985-1992

6th SOS CO's Aircraft....."Spad Dad".... 331KillerBee

ThirdWire's SPAD with some Decals on it...... Semper Fi! 331KillerBee

I've seen this happen also. Can't be of any help as to the Reason for it happening. It's a YAP Product. You might want to ask their Customer Support why the Model is faulty. You paid for the Product, They ought to help You out with this Problem. At least have some Answers for why this is happening. As a Commercial Product, One would think that YAP has tighter Quality Control than this for the amount of Money that One has to invest to get a complete Copy of their Product. 331KillerBee

Wpnssgt, This Link should help out..... http://en.wikipedia.org/wiki/United_States_Navy_Fighter_Weapons_School 331KillerBee

Heck Ed, Your as Old as I am. You know that Statement could apply to the GOP since the 1950's. Not just Ole' Tricky Dick. I find it funny that the GOP's Political Tactics today have there Roots in the Democratic Party with the conservitive "Dixie-Crats" of the 50-60's. The late Senator Jesse Helms of North Carolina was a prime Example. His abrasive Tactics of Campaigning and Stances on Issues has been taking up by the GOP since the 80's. Helms was a "Dixie-Crat" Child of the 50's..........

EzLead has got it.......That's the way I handle USMC VMCJ Squadrons that operate 3 to 4 different Types of Aircraft. I also use it later for VAQ-33. They operated 4 to 5 different Types durning the same timeframe.

You go WRONG. As Fubar512 stated, The Effect seems to be showing a Cluster Bomb Effect. Either the Effect is tied to a Cluster Effect via the WeaponsData.INI (That can be editted by the Weapons Editor) or You have a corrupted MissileObject.INI or the Entry missing in it. (It ties the Effect to the Weapons in WOX Titles) If You are sure You've placed the EE3 Effects in an "Effects" Folder of Your Install, Then I'd check those two .INI's. CAStary's EE3 has both a Ground and Aireal Nuclear Explosions. I'm running EE3 in My SF2 Installs and have run it in My eariler WOX Titles no matter what Patch ThirdWire released for that line of Titles. BTW, The "Nuclear Fusion or Fission" Fubar is talking about deals with Warhead Types in the Weapons Editor.

Happy Birthday!

Here's some Info: Operation Shed Light 1966 Ground target marking, which was a key tactic for day time strikes, was investigated. Project 2531 was to investigate target marking munitions, and looked into warheads for the Mk 40 2.75” rocket motor, using a variety of chemiluminescent materials. These were to be loaded with compounds developed under the US Navy's Target Illumination and Recovery Aid (TIARA) program. Initially they used modified M151 high-explosive warheads, but found the amount of compound that could be contained provided poor results. The Shed Light Task Force noted that a lighter case for these compounds was in development. A combination of red phosphorus and a flare was investigated in an attempt to provide a system that could be used at night or during the day. Types of Flares used since Operation "Shed Light" 1966: (1) LUU-1/B,5B,6D target marking flare Designated for a 30-minute burn time on the ground, providing a colored flame. LUU-1 burns red, LUU-5 burns green, and LUU-6 burns maroon. (What You need made) (2) LUU-2 parachute flare The LUU-2 provides up to 4.5 minutes illumination of 2 million lumens. The flare consists of a cylindrical aluminum container enclosing a timer, parachute, and candle. (What We have moddeled now) (3) LUU-19 covert flare The LUU-19 has the same physical dimensions of the LUU-2, and provides up to 5 minutes and 1,200 Watts/Steradian of IR illumination of the target area for NVG capable attack aircraft. (Need to make it too) 331KillerBee

Mike, You talking about a Ground Contact Ilummination Flare? I'll make one up. 331KillerBee

FC, You'll want to consider doing the .LST Files also. My reasoning is this, .LST Files control a certian action by the Game. For example, Numbers.LST is the Numbers List in the Skins Files that control Numbers being displayed by the Decal System. There are other Lists Files that control Actions and random Actions like the Names.LST in the Flight Folder. .LST are just like .INIs but act and do Actions in another fashion, They are normally opened and editted by Windows Notepad. So Encoding for them is just as important as an .INI. If anyone has unpacked a SF2 Install, like I have. They'd noticed that not all .CATs have been converted by ThirdWire. The ones that have been done are the .CATs that involve Objects. If one looks at the sheer number of .CATs involving just Objects for all three Titles for SF2, One can understand the work involved by ThirdWire in doing such Conversions. The other .CATs which are the MissionData.Cat and MissionText.Cat, FlightData.Cat and FlightText.Cat, Also the Terrain.Cats have not been converted by Thirdwire. With the resent Comments by TK and ThirdWire, with the Announcment of SF3 in the Future, One can only conclude that the other .CATs will be converted as Time and Project Funding permit. More than likley done via a Patch. I've been running My Installs after doing such Encoding Conversions with these Benifits: 1) Uniformity. It makes for a cleaner Install. 2) Game Engine runs smoother with less Bugs by the Game Engine. The Game Engine doesn't have to switch from one Encoding to another to read various .INIs. 3) A minimum FPS Gain. (Depending on System and Hardware) 4) It make me ahead of the "Ball Game" as far as the Path that ThirdWire is heading with this line of Titles. Again, This Conversion doesn't inprove Loading Times. Loading Times are so dependent on the Terrain Files. Heavly Modded Terrains will Load slow. The more the .TOD files are Modded and the addition of more Objects added to the Terrain will slow down Loading Times. It takes Time for the Game Engine to render out all of these things. I've have been running this Conversion now for a Couple of Months on all three of My SF2 Titles. I have not run into any adverse Effects to doing this Conversion. Actually, I've had smoother and Improved Gameplay of all My Titles with Bugs kept to a minimum...... 331KillerBee

I see a Difference between these two Entries..... F-16A_Blk10-NDC/SkryStrap/d/dnrnum F-16A_Blk10-NDC/d/daf Is the "SkryStrap" Folder there?

331KillerBee's "Rule of Thumb" when Dealing with Decals.... DecalLevel=0 NationID, Controled by the Number of the Nation in the Nation.INI. DecalLevel=1 SquadronID, Controled by the Number of the Squadron in the Squadron.INI DecalLevel=2 Aircraft Number, Controled by the Number.Lst File in the Skin Folder. The Game Engine always starts with "000" no matter what the Actual Number is. Example: If I had Aircraft Nose Numbers from 1 to 5. The first Nose Number .TGA would be Nose Number 000 with a "1" on it. DecalLevel=3 Kill Number, Self explanitory. Controlled by the Number of Kills in the Pilot's .Plt File in the Pilot Data Folder.

DecalLevel=2 for Numbers.....DecalLevel=0 is for Nation ID such as Igsigna's....

The Pod..... The Sensors...... 331KillerBee

ADSIDs The ADSID, or Air Delivered Seismic Intrusion Detector, was a family of sensors that were released from aircraft as the name implies, and fielded in versions I, II and III. Sensors dropped in each area of operations were factory-built with a fixed-frequency on which they transmitted. For any of the area-designated frequencies, they had to be ordered by unique FSN (Federal Stock Number) to match the assigned frequency channels. Nomenclature Model Variant Type Length Weight ADSID I (N) - - - - - - normal - seismic - 31.00 ins - 26.0 lbs ADSID I (S) - MA-36 - short - seismic - 20.10 ins - 13.7 lbs ACOUSID II - TC-415 - ****** - seismic-acoustic - 53.14 ins - 38.8 lbs ACOUSID III - MA-31 - ****** - seismic-acoustic - 47.63 ins - 37.2 lbs ADSID III (N)- MA-33 - normal - seismic - 37.66 ins - 37.2 lbs ADSID III (S)- MA-37 - short - acoustic - 20.10 ins - 13.7 lbs MODS 81 mm - mortar - ****** - seismic - 33.00 ins - 9.6 lbs It is estimated that some 36,000 ADSID and ACOUSID sensors were produced by just one of the contributing manufacturers involved. Sensor design consisted of a series of common modules, using the latest Integrated-Circuit chip technology of the time to keep costs down. The electronics design centered on a concept of interchangeable subsystem circuit boards - 'Common Modules'. Common Modules were cylindrical, sealed in hard foam potting compound, and connected to each other with circular connectors around the outer circumference at the ends of the cylinders. As with the GSID, the same adjustments - Gain, Code, Real-Time, Inhibit, and Disable - could be programmed into the ADSID modules. A 'Common Module' existed for each of the following functions; Transmitter, Encoder, Command decoder, and Command receiver. RF alarm messages were modulated with a combination of 19kHz, 25kHz and 32kHz pulses, which provided up to 27 codes (IDs) on a single radio channel. The transmitter radiated two watts power on one of 40 channels in the 160-175 MHz-band FM/VHF radio spectrum. Presets If switched to the RT (Real Time) mode, the sensor would transmit alarms at a maximum rate of 1.4 per second. If the sensor alarmed constantly in the RT mode, minimum battery life was at least 48 hours. If switched to the INH (Inhibit) mode, the sensor would transmit alarms at a maximum rate of one every ten seconds. Minimum battery life in this mode was 45 days. In spite of rocks, trees, rice paddies and other inhospitable impact sites, 80% of the ADSIDs were found to be operational after air delivery. Application The ADSID III shown in the photograph above is typical of the devices dropped from U.S. aircraft along roads, rivers, and jungle trails in Southeast Asia. They were dropped in sequential 'strings' along a predetermined target line in a series of from 4, up to 10, 12, 15 or sometimes more, depending on the priority of the target area. With their flexible spring-steel antennas, they were designed to bury in the ground and blend into the surrounding foliage by resembling tree branches and plants. All devices transmitted alarm data for only a short distance. They were continuously monitored twenty-four hours a day by U.S. Air Force crewmen flying unarmed, propeller - driven electronic surveillance aircraft orbiting overhead at 20,000ft. Initially, Navy OP-2E Neptune aircraft performed sensor air deliveries at very slow speeds from altitudes as low as 500 feet, making them easy targets for enemy gunfire. The pilots of VO-67 at Nakhon Phanom AB knowingly expected that they would incur as high as an 85% casualty rate from such operations, but volunteered to fly them anyway, and many crewmen were lost. During later operations, sensors were hand-dropped from CH-3 Jolly Green Giant helicopters by personnel of the 21st SOS Dust Devils (Special Operations Squadron) and later, delivered by Air Force F-4D Phantom-IIs. 331KillerBee

The Word Cage or "Caged" refers to two instances. One, For A2A and A2G Missile's Guidence and Control Sections (G&C's). If the G&C of the Missile's Seeker is "Caged", It means that the Seeker is Locked looking straight ahead. "Uncaged" means the G&C is active and Looking for it's Target in the Seeker. The Missile's FOV is unlocked. "Caged" as referenced to Gunsights means that there is no "Depress" or Adjustments. Straight ahead. What You see through the Gunsight is what You get. Any Gunsights that are not Lead Computing and don't have a Bombing Depress are "Caged" Sights.

Dang Fubar! I had no Idea that Your Birthday is a Day after Mine. Well, Happy Birthday! May the Party continue! 331KillerBee