Caesar

Thanks for the info eightlein, I did get the Valusoft version off of Circuit City; I'll be sure to get the patches. From what I hear, I'm guessing I wont have to modify the timeline to fly my favorites (such as the Tomcat) in the options.ini; or not as drastically as WoV. A question on terrain: does SFP1 have more available maps/different sized airfields, or do I just get them from such fine sites as CombatAce? Thanks again! On a side note: I'd suppose you're right about the AIM-54>MiG-17 bit...but I figure I might as well exploit every advantage I have

Hey all, Well the topic pretty much says the question: is the MiG-25PD WoV compatible, or only SFP-1? I ask because I know that almost every plane runs on either or, but I haven't had any luck running the Foxbat; the game just crashes. I suspect I might be doing something wrong. Basically, I unzip the folder, dropping it into the Objects/Aircraft folder, and put the pilot files in Objects/Aircraft as well, not the Foxbat folder itself. Is there something I missed/screwed up? Thanks in advance!

Another thing is, can you select the mission type? For example; my Tu-16 wouldn't work until I added a primary mission compatible with WoV. ANTI_SHIP was the only listed primary role for the Tu-16 in its DATA.ini file, so I added STRIKE as well, which allows me to fly strike missions with the plane. Formerly, I couldn't get to the hangar screen. After I added STRIKE and made the min base size MEDIUM, I could fly the plane just fine. Idk if this is the case with the Tu-22, but it's something to look into.

Well, your Phantom near-death-experience would still rank very high amongst anything I had done, actually. A lot of my close-calls or misadventures usually involve me landing a beat-to-hell Tomcat or using a plane to which I am not accustomed to. Sometimes it's just a matter of trying a manouver you're used to being able to pull in another plane. The F-102 backflip, for example was brought on by me putting the F-102 into a hard, sustained turn. I had not noticed how quickly the F-102 bled speed; I thought it would hold at least 150kts for a while, but I went from about 600kts to 50kts very quickly. The plane went nosedown and I couldn't pull the plane out of it. That's when I selected full burner and deployed the gear. This, as we now know, was the wrong decision, as I should have punched out...but it's a lot funnier that I rode it and flipped over myself and got some good shots in it too. That's the moment before impact. Going M1+ at 500 feet or less on a runway strike will also usually end in a good story...though the odds of surviving it are low. Your bridge incident is just the first of many that will happen eventually.

Ah, haha, that is pretty amazing, and congratulations on surviving it! Scraping off the stores was going to be my second guess, because believe it or not, I too have scraped off the stores; though never in such a way as you have, I've done it once out of necessity, once out of ignorance. Looking at your altitude, though, I had assumed you weren't low enough to have done that (or rather, you hadn't been moments ago.) The first scrapeoff I had was preformed in my main profile (Caesar), which I use exclusively for the Tomcat. I once knocked off my port AIM-7 when preforming a one-and-a-third-wing, one-engine, two-of-three-gear landing. During a mission, a MiG-23 hit me with an AA-8. I actually shot him down after the fact, but the port wing was blown off 1/3 of the way down (i.e. I lost 2/3 of the wing), I lost the left engine, the left gear, the airbreaks, the tailhook and fuel in the left wing. With a lot of rudder and smart flying, I brought the plane back to an airstrip, where I jettisoned the external stores, fired both AIM-9's just to get them off the plane, but couldn't do anything about the -7, so I just prayed it wouldn't go off. I landed the plane, and the -7 scraped off without exploding and the plane screeched to a halt. This mission was a success, and I survived the landing, so I was a pretty happy camper! The second time, under my USAF profile, I began a strike with a B-58 Hustler. Pulling back way too hard on the stick for the bomber, the massive fuel tank scraped the ground and got knocked off...that put a real wrench in the mission! Among other quirks, I've backflipped an F-102 (I've got three or so screens of this one) when I had a low-altitude stall and in a desperate attempt to survive deployed the landing gear, went full burner and tried to get the nose up as quickly as possible. The main gear hit first, the aft gear hit second, but as the aft gear hit, the nose of the -102 was well on its way up and the other gear "finished it off." The plane backflipped all the way over itself, and landed nose-first in the ground, and that was the end of that, as they say. Again, an amazing feat! I'd say you showed that bridge who's boss.

Well, I'll take a shot. It looks as if your plane got hit by something. Noting the holes in the starboard intake, and it looks like your wing may have been damaged also, I'll guess that you had a near-miss with either a SAM or AAM, which damaged, though did not destroy your plane. In the process, a lot of the ordinance was lost. That's my guess.

Almost all add on planes and skins for the planes are compatible with both SF-P1 and WoV. In other words, almost every plane you see on this site (in the Strike Fighters section) will work with Wings over Vietnam, though some modifications have to be made in the date range of WoV itself to make them available if they entered service after 1973 or if they left before 1968 or whenever the time span default is in WoV (I can't remember, I modified mine a while back.) There's a few threads on modifying the dates on these forums, it's not a big deal; it's in the main directory Options.ini file. Similarly, to fully utilize the planes, you should get the latest Weapons and Effects Packs.

Did you check the aircraft's hardpoints in the data.ini? I haven't tested out either plane, so I don't know what it's capable of, but the hardpoints/weapon pylons might not have the ability to carry the class of weapon the Firestreak is. For example (yet again...from my Tomcat): [MissileStation1] SystemType=WEAPON_STATION StationID=11 StationGroupID=4 StationType=EXTERNAL AttachmentPosition=-3.05,-0.60,-0.450 AttachmentAngles=0.0,1.0,0.0 LoadLimit=500.0 <==================Another factor AllowedWeaponClass=AHM,IRM,LGB,BOMB <======Look at this AttachmentType=NATO,USN <===============And this ModelNodeName=LeftsupM PylonMass= LaunchRailNodeName=Rail_Side_Left01 MissileRollAngle=90.0 MinExtentPosition= MaxExtentPosition= Under AllowedWeaponClass, this particular hard point can carry Active Homing Missiles, InfraRed Missiles, Laser Guided Bombs and normal Bombs as annotated AHM,IRM,LGB,BOMB. (I added bomb capabilities to my 'Cat by adding ,LGB,BOMB to AHM,IRM.) The line below it "AttachmentType" means, I believe, that the plane can only carry weapons affilliated with either NATO or USN. If the Firestreak is a SAHM or AHM or IRM or whatever, and that isn't listed on the hardpoint, it can't carry the weapon, similarly, if it is not under the right nation affilliation, it cannot be carried even if it fits the hardpoint class; it is for this reason you won't find an F-16 loaded with AA-2's or a MiG-25 with an AIM-120, unless you modded the nation's attachment type to also carry SOVIET for the F-16 or NATO/USAF/USN for the MiG. Remember also, weight and weapon diameter come into play. While an F-14 can carry an AIM-54, an F-16 can't because the missile is flat out too big and too heavy. For that matter, an F-14 can't carry the 10mT nuclear pod because of the same reason. If the planes in question were designed to use the Firestreak, there shouldn't be a problem, though specific hardpoints might not be able to carry it; you can't load an AIM-54 on an AIM-9 rack or vice-versa. Specific racks can carry more or less, and this can usually be seen on the LoadLimit line. If the Firestreak is too heavy for a specific point, you could still allow the point to carry whatever class of ordinance it is, but it still won't show up if it is too heavy or too big. Hope this helps.

Ah, all right, thanks very much. I changed the data...but won't be able to test it until after classes oh well. Thanks again!

I'm not sure how you get it to unlimited, but if you want to be able to support all aircraft over all their date ranges, go to your main WOV folder, open options.ini and replace the [singleMission] [DogfightHost] and [CoopMission] ranges from their initial settings to something bigger. I have mine set to 1930 start and 2021 end; this allows me to use any plane over any span that I've yet found. If WWI planes get released, shift the start date to 1910 or so. For a brief example: Part of options.ini [singleMission] AircraftType=F-14A MissionMap=VIETNAMSEA MissionType=SWEEP MissionTime=RANDOM MissionWeather=CLEAR AirActivity=NORMAL AirDefenseActivity=LIGHT LoadMission=FALSE LoadMissionFilename=Carrier Take-off MissionYear=1991 StartYear=1930 <============MODIFIED from 1968 to 1930 EndYear=2021 <============MODIFIED from 1973 to 2021 Also, individual planes can be modified as well. My Tomcat, in its F-14A_DATA file starts in 1970 (first flight year) and ends at 2006 (this year, the last -D models will retire) from 1973 and 2004 (I think to be absolutely accurate, it'd be 1972-2005; VF-1, -2 and -124 equipped on 14 Oct 1972, and the last -A squadron retired in early 2005 if I remember.) BUT, I could mod it to fly from 1930 to 2021 so it could fight any fighter at any time. Another example: F-14A_DATA start [MissionData] NationName=USN ServiceStartYear=1970 <====MODIFIED from 1973 to 1970 ServiceEndYear=2006 <====MODIFIED from 2004 to 2006 AircraftRole=FIGHTER AircraftCapability=DAY_AND_NIGHT ...etc. My Iranian 'Cat goes from 1977 to 2021 (as an estimate) by making the start and end years 1977 and 2021 respectively. It's as simple as modding the years. But as stated before, I don't know how to make the years unlimited...just finitely big. Hope this helps.

Something else I also thought of. Different planes can only be used in different roles, unless you modify them in their own data files. Your weaponry is also not selectable in MP, it uses the defaults, so if say you wanted to do a strike with a Tomcat, you'd have to add strike to its primary role and make an air-to-ground loadout. Similarly, if you wanted to use an attack plane like the Skyhawk for a MIGCAP (I don't recall if it can???) you'd have to add that to its primary roles. If you select one group to strike, usually the other is forced to escort also, so only planes with escort ability can be selected for the strike's escort; i.e. even if a plane has MIGCAP but no escort ability, it won't be selectable. We had this problem when using the A-10 initially, until we figured out which roles it supports, and which it didn't. Factor this with the time scale, and it can get confusing. Just stay vigilant, and I'm sure you can get it working. This should help- The start of my Tomcat data.ini [MissionData] NationName=USN ServiceStartYear=1970 ServiceEndYear=2006 AircraftRole=FIGHTER AircraftCapability=DAY_AND_NIGHT Availability=COMMON Exported=TRUE ExportStartYear=1977 ExportAvailability=VERY_RARE PrimaryRoles=SWEEP,CAP,INTERCEPT,ESCORT,STRIKE,CAS,SEAD,ARMED_RECON SecondaryRoles=RECON NormalMissionRadius=1233 MaxMissionRadius=1730 Ceiling=16764 MinBaseSize=MEDIUM CarrierBased=TRUE So, the plane is selectable from 1970 to 2006, and can do a Fighter Sweep, MIGCAP, Escort, Strike, Close Air Support, SEAD and Armed Recce To match the call for Strike, CAS etc. here's some of my additions to the armaments in the F-14A_LOADOUT file Loadout[05].WeaponType=Mk83 Loadout[05].Quantity=1 Loadout[06].WeaponType=Mk83 Loadout[06].Quantity=1 Loadout[07].WeaponType=Mk83 Loadout[07].Quantity=1 Loadout[08].WeaponType=Mk83 Loadout[08].Quantity=1 Loadout[09].WeaponType=AIM-9G Loadout[09].Quantity=1 Loadout[10].WeaponType=AIM-9G Loadout[10].Quantity=1 Loadout[11].WeaponType=AIM-7M Loadout[11].Quantity=1 Loadout[12].WeaponType=AIM-7M Loadout[12].Quantity=1 [Attack] Loadout[05].WeaponType=Mk83 Loadout[05].Quantity=1 Loadout[06].WeaponType=Mk83 Loadout[06].Quantity=1 Loadout[07].WeaponType=Mk83 Loadout[07].Quantity=1 Loadout[08].WeaponType=Mk83 Loadout[08].Quantity=1 Loadout[09].WeaponType=AIM-9P-4 Loadout[09].Quantity=1 Loadout[10].WeaponType=AIM-9P-4 Loadout[10].Quantity=1 Loadout[11].WeaponType=AIM-7M Loadout[11].Quantity=1 Loadout[12].WeaponType=AIM-7M Loadout[12].Quantity=1 This allows for MP and especially AI planes to be armed for strike/attack missions. I hope this extra info helps as well.

It certainly is, but a lot of the planes here are from different time periods; therefore to use them in MP, you might have to modify the date range in your options.ini in the main WoV directory. For example mine is (abridged): [singleMission] AircraftType=F-14A MissionMap=VIETNAMSEA MissionType=SWEEP MissionTime=RANDOM MissionWeather=CLEAR AirActivity=NORMAL AirDefenseActivity=LIGHT LoadMission=FALSE LoadMissionFilename=Carrier Take-off MissionYear=1977 StartYear=1930 <--------------------Modified EndYear=2021 <--------------------Modified [Multiplayer] SessionName=MySession SessionType=0 GameType=1 Password=Caesar's Game MaxPlayers=4 Connection=0 PlayerColor=2 [MultiplayerOptions] PortID=2400 LobbyLaunched=FALSE [MiscOptions] DisplayUnit=0 ForceAIPilot=FALSE Shadow=0 [DogfightHost] MissionMap=VietnamSEA MissionYear=1972 Loadout=1 StartTime=10:30:00 StartTimeDeviation=240 RespawnTime=30 RespawnDistance=4000.000000 MinHeight=2000.000000 MaxHeight=5000.000000 HeightDeviation=1000.000000 ContrailAlt=7000.000000 ScreenshotsDelay=60 StartYear=1930 <----------------------------Modified EndYear=2021 <-----------------------------Modified WeatherType=SCATTERED [DogfightPlayer] AircraftType=F-4E TextureSet=DefaultTextureSet PlayerService=USAF Squadron= [CoopMission] MissionMap=VietnamSEA MissionYear=1983 Service1=USN Service2=NVietnam Mission1=CAP AircraftType1=F-14A AircraftType2=FA-18a AircraftType3=MiG-21MF AircraftType4=Mirage5BA ContrailAlt=7000.000000 ScreenshotsDelay=60 StartYear=1930 <-----------------------------Modified EndYear=2021 <------------------------------Modified WeatherType=SCATTERED Note the StartYear and EndYear have been changed from 1968 and 1973 to 1930 and 2021; this will allow for you to run any plane that I know of in the flight sim; F-4F, A-6M2, F-86, F-14, F-15E, etc. If you want, you can also modify the start and end years of the planes. For example, I modified my Tomcat years to 1970 start and 2006 end (from 1973 to 2004). Just a precautionary note, I think all the installs need the same start and end years...though I'm not 100% sure on this...it would help anyways so everyone can play within the same date range. Hope this helps.

http://forum.combatace.com/index.php?download=917 That's the F-111 package on this site. As for frame rates, I'm not sure, it depends on your hardware, how many system processes you have running, etc. Prior to my upgrade about two weeks ago, I was running an ATI Radeon 9000, which handled WoV pretty well at 800x600 or 1024x768, but I had to run most things on medium rather than high settings. Thanks to my major overhaul, this is no longer a problem . Hope this helped!

Hey all, I'm writing this one to get an idea of how successfully you other WoV/SF pilots have been able to pull off missile evasion without countermeasures. It was getting kind of frustrating engaging MiG-29's in the Tomcat, Eagle, Hornet, etc. with a roughly 1% hit probability using S/AHMs, so I went ahead and ditched its chaff/flare ability by setting the quantity to 0. Of course, this is a bit unfair for the bad guys, so I was thinking about entirely ridding of cm's, or maybe lowering the number on both friendly and enemy planes. This'll also make LANs more interesting. As for myself, in an older flight sim, Fleet Defender, I wasn't all too bad at dodging missiles when I ran out of chaff or flares, but I've noticed that the missiles in WoV/SF provide much more of a challange for one reason or another; I can do it, but not consistantly. Any of you all good at dodging without cm's? I'm just trying to get an idea of whether or not I should ditch the cm's entirely or if that's plain out dumb. Forgive me if it takes me a while to respond...I'm on dialup until I return to college in a month... Thanks, "Caesar"

I would, but it depends on if WoV is compatible with SFP1, and if you can wait a month...I don't have broadband back home, so my online gaming is restricted to playing when I have free time at college.

Hello, all. I was wondering if anyone could field this question for me: what are the engine thrust units in the aircraft data files? To clarify, I'm trying to set up a "what if" situation with the F-14, that being, what if the advanced experimental F401-P400 engines for the original F-14B in 1973 had been employed. When looking at the engine's thrust, however, I found the units not to be in pounds or kilograms or newtons. Can anyone tell me what the thrust is rated in in WoV/SF? Thanks in advance.

Oh, thank you very much. I must have miscalculated a ratio. When I tried to figure the units I compared to pounds and got 5.444, which is why I had assumed they weren't Newtons. Thanks again.

Well, that's polotics for you. I'll always hold "Duke" in high regard when talking about air combat or our American aces, but man, did he screw up on this one. I can't say I've ever met him, I'm a bit younger than you guys who flew over there, but from what I had seen and read, he seemed like one of the good guys, charismatic, and concerned for the nation and its defense. It's really sad.

Hey all, I was wondering if anyone else ran into this problem: I was flying the Tomcat against MiG-29 Fulcrums last night, and when I fired my AIM-54C's, they would briefly track, then blow up a few miles off my nose. If they got close to the Fulcrums, they would loose track during terminal guidance. This didn't happen once or twice, but every single time I fired a -54C. I was well above the Phoenix's Rmin, so I know the missile had time to arm and track. Normally, the -54C is not an easy missile to fool eihter; powerful internal radar, ECCM suite...so I don't understand why they seem to work against every other fighter/attacker/bomber/etc, but not the Fulcrum. Any ideas? Thanks

Oh, okay then. Well, guess I'll just hope for a patch! Thank you all for your input and time.

Makes perfect sense: they work but too damn well. I think I'm gonna see if I can modify that at all...probably not, but it'll be worth looking.

Out of a question, then: I'm running WoV; does that also have the over-power chaff issue that's in SF? The -29 engagements would be pretty good evidence to say it does, but I thought other a/c i engaged had chaff/flares and I did not get the same problem. Similarly, has anyone tried to modify the chaff/flare power before?

I went through the data file for the MiG-29. The real -29 does have ECM but it's not powerful enough to fool a Phoenix over and over (I can bag 'em constantly in Fleet Defender!); that having been said, the MiG-29A for WoV/SF doesn't have anything listed in the ECM section, though it does have flares and chaff. Maybe the problem's there? I'll check it out. Thanks for bringing it to my attention.

Oh well, I guess I could try to tweak the Phoenix, maybe that'll do something. Thanks for the input.

You're probably right, it just happened again around 10:50 tonight! I engaged a bunch of Zeroes...and lost 2/3 of my left wing when I passed too close to one. Apparently he died, and I got about 50 screenshots of my remaining flight, and subsequent landing with only one wing (or one and one third of a wing, actually). Not the first time I had to land a damaged 'Cat, but certainly one of the most difficult!