MigBuster

Looks okay - can you try changing on the SUU-16: StartYear=0 EndYear=0 Next check spelling and case - whats the LOD file called? needs to be referenced exactly

That should run it - did you manage to switch off AA? or do you not understand what I mean? Also is that a Geforce 8600 or similar?

No crikey it has no classified info in it. Its called Sierra Hotel (Flying Air Force Fighters in the decade after vietnam) by a ex Pilot C. R. Anderegg I particularly like this bit: Throughout the book I have attributed credit where it is due. However, many statements in the book are my own. For example, in the last chapter I write that the F–16 is a better day, visual dogfighter than the F–15. F–15 pilots who read that statement will howl with anger. Sorry, Eagle pilots, but I flew the F–15 for over ten years, and that’s the way I see it. (Fighter pilots are not happy unless they are stirring the pot.) And Ceasar will like this bit: Opinions, conclusions, and recommendations expressed or implied are solely those of the author and do not necessarily represent the views of the Air Force History and Museums Program, the United States Air Force, the Department of Defense, or any other U.S. government agency. Cleared for public release; distribution unlimited.

The only person who can post such information not in the public domain is Busdriver - but pretty sure he wont be, so I dont think you have too much to worry about.

Yes thats why I put it doesnt have to be the klite codec causing the problem - another codec or media player could be screwing things up. Can you switch off Anti aliasing from your graphics card settings - you are using a Geforce card yes? Right and you created a NEW shortcut to put the -nomovie switch into yes? Did you patch it to 1.013? what are your system specs - can you do a DXdiag from run and see if it brings up any errors?

Assuming its on the centreline it still has to impose a drag and weight penalty - but that still might be negligible against exercise opponents like the F-15A/F-14A

Discussion ties in with this: As the F–16 weapons school labored to get started, another squadron at Nellis, the 422d Test Squadron, was conducting a test that was a fighter pilot’s dream. The main purpose of the test was to investigate ways to reduce the radar cross section of the F–16. Radar cross section, or RCS, is the amount of radar energy an airplane reflects to a tracking radar. The more it reflects, the larger its RCS. An airplane with a large RCS can be tracked from farther away, and more accurately, than one with a smaller RCS. The test would compare different techniques for reducing the F–16’s RCS against a variety of radar systems. This meant that the F–16 pilots would fly against the pulse radar of the F–4 and the pulse doppler radar on the F–15, over some 200 test missions. For the Eagle, Phantom, and Viper pilots in the 422d, it was heaven. It was a license to fly unlimited A/A against one another in every conceivable scenario: two Eagles against two Vipers, four against two, four against four, two F–16s against four F–4s, and so on. Every mission was flown on ACMI to document performance, or lack of it. The F–16s always had to fight against an equal or greater number of adversaries; they were never allowed to outnumber the opponents. Although the test parameters were set, the pilots, like the AIMVAL-ACEVAL pilots, had considerable latitude in selecting and devising tactics. The considerations boiled down to a few key facts. The F–4s and F–15s could shoot their radar-guided Sparrows well beyond visual range. The F–16 had neither a radar missile, nor a radar as powerful as the others did. Therefore, the F–4 and F–15 could not only see the Vipers first, they could also shoot at them first. Also, the new Sparrows, the AIM–7F, on the F–15 were proving to be very accurate and reliable in shots against drones. In effect, “the F–15 was playing a whole new ball game, and they got to write the rules.”9 Without doubt, the pilots who would fly in the test were some of the best in the Air Force. The 422d commander, Lt. Col. Joe Merrick, had commanded the Multinational Operational Test and Evaluation of the F–16 at Hill Air Force Base before taking over leadership of the 422d, and he immediately surrounded himself with the best pilots he could find. Most, if not all, were combat veterans, and all were weapons school graduates.10 The F–16 pilots immediately started to look for ways to survive to the merge. They drew on the lessons learned a few years earlier by the AIMVAL-ACEVAL Air Force pilots who had found themselves in the same situation. They studied the F–15 radar and the Sparrow missile and found some small vulnerabilities, which they exploited. It took perfect timing and pilotage, but if they could confuse the Eagle and Phantom pilots and get one or two Vipers to the merge, they could fight on F–16 terms. Of course, the Eagle and Phantom pilots immediately developed techniques that countered the tactics of the F–16s, and another cycle of countering the counter to the counter began. The stakes were high. Everyone knew that the Soviets were equipping their fighters with missiles similar to the Sparrow and Sidewinder. The days of U.S. pilots having the only effective radar missile in the battle were long gone, and the F–16 pilots had no radar missile at all. Blithely flying straight into the merge from twenty miles away was a sure recipe for disaster. The competition was intense. One day a pilot brought a rubber chicken, the kind used in slapstick comedy, to the squadron, and he and his buddies stuck into the silly, limp carcass a host of small plastic models of A/A missiles. The next day they hung the bird over the entrance door to the flight room of the guys who had lost the fight. The day after that it reappeared over the door of that day’s losers. No one wanted it, and the pilots studied hard, flew hard, and schemed hard to avoid seeing it show up at their door. From this atmosphere of intense competition in Merrick’s squadron emerged a new tactical term: all-aspect missile defense (AAMD). As pilots of each of the fighter models learned ways to survive— and kill—in the all-aspect missile environment of the Sparrows and Sidewinders, they spread the word throughout the weapons school. Students then took the new tactics back to their home units. Within five years, all Air Force fighter squadrons were using AAMD as part of their daily training routine. As they honed their skills to employ their own “face shooters,” they also learned how to survive ones fired at them.11 Work done in the 422d Test Squadron was not totally original. Those who were there are the first to say that AAMD developed over several years and carried the fingerprints of dozens of great fighter pilots.12 Aggressors had been defending themselves against all-aspect missiles for years, and the AIMVAL-ACEVAL pilots brought the tactics to an even higher level. Yet several factors converged in the early 1980s that made AAMD vital to the newest generation of fighter pilots. First, the missiles were becoming more credible every day as the WSEP results revealed superb missile accuracy and reliability. Second, the new HUDs and fire control computers showed exact launch parameters, helping pilots know exactly where they were within the missile’s capability to hit the target. Additionally, the Soviets were fielding a new generation of missiles as good as—some thought better than—the Americans, giving the development of an effective AAMD added urgency. Finally, dissimilar air combat training, testing, and evaluation had matured to the point that every pilot had the opportunity to fight often against different aircraft. A feeling started to grow within the Air Force fighter community that if an F–16 pilot could beat an F–15, or an F–15 could beat a Navy Tomcat, then when the next war came, the enemy would be dead meat. By 1984 the most striking change in the battle arena was how much technological changes had expanded the air-to-air battle space. Ten years earlier, F–4 pilots had struggled mightily to get radar contacts and tried to take the first shot with a questionable radar missile. The main focus for the Phantom drivers, however, was to get to position from which they could visually engage and kill the bulk of the targets. In the mid-1980s, the F–15 could see fighter-size targets over fifty miles away and start to jockey for the first shot. Even the small radar on the Viper could see targets beyond twenty miles. The new jets were maneuvering at vastly extended ranges based on the information from their radars.13 “The tactics development from all that shucking and jiving made everybody learn.”14

This was probably down to limitations of radar tech (mechanically steered) and processing power - there is nothing but chatter to state tricks like these have been tried against the F-22 AESA APG-71 in exercises by aggressors and do not work any more - nothing concrete. Did those F-15Cs still have the older APG-63 non AESA sets? Problem is they never reveal other factors in exercises that may totally influence the outcome!!

Can you now see the SUU-16 in the weapons editor list when you open it up? If so can you check #23 on here which applies to SF1 http://combatace.com/topic/44026-converting-older-planes-to-work-in-sf2-a-basic-guide-by-migbuster/ Nation and service date are basics to check

RIP Billy

Could still be a codec though - doesnt have to be K-Lite - assume you looked at this?? http://www.lead-pursuit.com/FAQ_01.htm I hear the Intro video music, but no movie shows. Sometimes I also can not get into the User Interface - the parachute icon shows, but I need to press CTRL+ALT+DEL to close the program. What is wrong? You might have installed a 3rd party video codec packages. They can cause all possible issues and problems. For example, the K-Lite video codec package is known to cause problems with Falcon 4.0 Allied Force. If you have this installed, do the following: Open Klite Codec pack > Configuration > Fddshow > Video decoder configuration and change the MP42 format entry to disabled by clicking on libavcodec. As a result the standard MS codec will play the AVI movies and FDDshow is not used for this type. Falcon will run fine with movies then. Also try changing graphics card drivers and seeing if your monitor needs drivers also. If you are on Win 7 or Vista run it as admin via the compatibility tab - Ideally install it outside of program files - in fact might be best to just patch it to 1.013 if you have not done so.

Glorious work - well done

Respect

Happy Birthday KB (belated) :drinks:

hmmm - well I would start by looking at the texture.ini for the skins in case they are now overiding the campaign data ini: [TextureSet] Name=Soviet Silver Nation=Soviet <--------does SyAAFCamo have Syria here?? StartDefaultDate=1 <---------Could this be the cause? Specular=1.000000 Glossiness=0.500000 Reflection=0.800000 DecalNumberRandomize=TRUE Also check that the MiG-21PFM actually has a SyAAFCamo skin with it in the objectdata cats

Good luck with this one to all affected - lets hope it dies out a bit.

Because it could be a major selling point of another game.

Thats not the default location for the mod folders in Vista/7 Are they mod folders or is that where you have installed the core game folders to?

Did you actually set the exes to run as admin in the compatibility tab?

Maybe thats why Israel replaced the radars with Ballast

Hope he got out okay - no word at all yet............ http://www.bbc.co.uk/news/uk-england-14602900

I think there was a collision in 2010 during practising but both pilots were okay.

Oh dear - bit more work needed then

Crikey - not from what I have observed - in SF2 they are really dumbed down compared to SF1. Which model of SAM in particular and what are you doing to beat it? SAMs will change course - they are guided and it depends on the model of SAM and countermeasures you employ as to whether you stand a chance of survival. However as in real life once you have defeated the radar lock from the ground (e.g Fansong) or its gone past you the thing is defeated - this is NOT "hollywood-esk" at all. Do you play with a TrackIR? because without that its difficult to get a 3D perspective on things and assume its doing something totally different to what its actually doing.

Havnt used that for years - cant you just do a file->open? You need to open MissionData.cat in C:\...\WingsOverVietnam\flight The extracted file would then need to go in C:\...\WingsOverVietnam\Campaigns\Linebacker1\ example: [AirUnit046] AircraftType=A-6B Squadron=VA196 ForceID=1 Nation=USN DefaultTexture=VA-196 <----skin it uses! StartNumber=50 BaseArea=Yankee Station CarrierBased=TRUE CarrierNumber=65 BaseMoveChance=0 RandomChance=100 MaxAircraft=16 StartAircraft=16 MaxPilots=16 StartPilots=16 Experience=100 Morale=100 Supply=100 MissionChance[sWEEP]=0 MissionChance[CAP]=0 MissionChance[iNTERCEPT]=0 MissionChance[ESCORT]=0 MissionChance=0 MissionChance[CAS]=0 MissionChance[sEAD]=80 MissionChance[ARMED_RECON]=0 MissionChance[ANTI_SHIP]=0 MissionChance[RECON]=20 UpgradeType=NEVER