Heretic

Note to self: Fly closer to the ground more often or get better contacts. Note to self: Never ever call your wingman for help when being chased!

Rocket jump? Also, congratulations on your low flying skills! (And greetings from 70kms farther westwards! :D)

Did the terrain get bump maps? Also, do any terrain mods from WoE work with SF2:E? I need more trees and houses.

Happens to me way too often in BF1942:FH. Hectic approach, bomb release and *boom*, back to the spawning screen. xP Nice NF-104 mod. Wish they had it in "The Right Stuff". Oh, and speaking of "I'm taking damage!"...wingie got toasted by this Fishbed's comrade. Taking revenge on Paran's newest ride... ...and since I believe in "two eyes for an eye"... The last pic was a gun kill at Mach 1.2 with a gunpod. Is that even possible IRL?

I know that missiles were developed for combatting bombers, yet I think that they are best used against fighters. Unless, of course, if there are nukes involved, then the bomber gets priority. I spend most of my time in the Harrier campaign which takes place in 1978 and features the "little less useless" -7Es and -9Es. While still not the best weapons I find them useful enough against Fishbeds and Frescos (~33% hit probability), so I really rather waste them trying to blow those PITA fighters out of the sky instead of those bombers just to make sure that the other guy won't harass me the next time. Maybe I should simply try to send my wingie against the Beagles while covering him from fighters. He's mostly just lurking around, unsuccessfully firing Sparrows against fighters and getting shot down anyways. Well, I'm gonna try deflection shots from their 3 or 9 o'clock next time I encounter them.

Weirdly enough I've encountered this behaviour more than one in 083006 patched installs. False interpretation or pure luck (for me)? As for my arch nemesis, I'll put the Il-28 on the top of the candidate list. I'll tell you why once you've stopped laughing. Done? Alright, here it goes: It's the fraking tail gunners. They're better shooters than any fighter jock and since an Il-28 normally isn't worth a missile shot (nope, not even a Sparrow!), I'll only waste 20mm shells on them. This means that I'll have to close in to gun range, which is leaving me on a diner plate for the guy in the back. And since Il-28 mostly come in packs of at least this means that there are at least four 23mm bolt throwers pointing at me one of which is eventually going to hit me. The best counter tactic is throwing your crate around until they run out of ammo or rely on very difficult attacks from the side. But this is usually too time consuming. I want to blast pesky MiGs out of the sky and not waste my time trying to reenact WW2!

Hi all, don't mind me, just joining in. Favourite aircraft (and accompanying tune): Although I'm preferring the "fighter" over the "bomber" in "fighter bomber". The campaign is JSF_Aggie's Harrier campaign, the Rhino version is a DF-4D (with RWR mod). "Break, break, break!" The Parani airforce should re-read their MiG-25 operations manual. There's just no way that a Foxbat which is dogfighting(!) at 10000ft(!) gets overshot(!) by a F-4(!). Leave your valuable Su-17s grounded and send Fishbeds in to do the dirty work instead. Great plan, Paran! *Frrrrrrrrrrrrrrr* *Bang!* Aerial kill #8... ...and #9. Saved my wingman's butt in the last second with a textbook gun kill (more luck than brains) from this PFM which had been harassing me a few minutes before. Fortunately, I was high enough for a (controlled) flat spin which threw him off my tail. /eyecancer delivery mode

Great idea for a campaign! Looking forward, especially since I'm an "SFP1 only" guy as well. Some Helicopter action would be great as well, like early Mi-24s and Mi-8s for Paran and ex-US Army UH-1s and AH-1s (or a Bo-105 (if there's one for SFP1) instead). A cool feature would also be some of the parani aircraft still sporting their "first hand" colors. Like east german camo (if this is a early 90s conflict) on the MiG-21s (bis) and MiG-23s... P.S: Make sure to include the "Desert Target Zones 1.1" mod as well - for more targets and SAMs.

Yeeehaw! I was just about to install SFP:1 again anyways!

Mostly campaigns.

I've got a problem with JSF_Aggie's DBS: 1972 Campaign and Major Lee's DBS Terrain (patched to the SP4 version). SFP:1 has the latest patch (083006) and weapons pack (030706) installed. I can't use any of the USN and RN aircraft in the campaign, since their carriers appear to be non-existant. I crash everytime because I simply seem to spawn in the air. I've triple checked (according to column5's tutorial) if the carriers are properly installed, I exchanged the Kitty Hawk (which works fine in the Burning Sands 1983 campaign, btw) with Forrestal-class carriers and with the Kitty Hawk from Burning Sands 1983 (which AFAIK is the one from WoV). Nothing worked. (Campaign.inis were edited appropriately,too). All carrier based units are stationed correctly on the carriers and the carrier stations are there, too. Anyone?

Uptate and solution: I've tried the Tarawa (for fun) and it worked. I've tried the Coral Sea and it worked. I've tried to put the Forrestal into the Coral Sea's file structure and guess what...my plane spawned on the cat instead of the icy waters. The only thing left to do is to pick a suitable, good looking carrier for the campaign.

While waiting for Aggie having time for me, I played around a bit on my own. Apparently, I got the Ark Royal fixed. Works now...even with wingman spawning and stuff. And I think that my wingman spawning on top of me could be a decisive factor for me blowing up and thus sending the whole carrier to kingdom come. No proof 'though. Replaced the old Forrestals with the new SP4 updated versions from Capun's site - no success with those (yet)'though.

Yeah, already put the carriers into the new format and it still doesn't work. I could get in touch with JSF_Aggie for some exclusive help 'though.

I don't get it. I've got five different installations of SFP:1 and each of them crashes during loading at 30%. I've tried to look for solutions here and at SimHQ before, but none worked. My system: Athlon XP 2700+ Radeon 9700Pro (Omega 26.75a (Catalyst 5.10)) 768 Mb Ram Windows XP SP2 w/ DirectX 9.0c My Strike Fighters installations: - Operation Tainted Cigar - Taiwan Straits 1958 - Korea 1953 - Burning Sands II Each installed as required in the readme and based on a fresh 3.2 installation with the latest weapon pack. Plus a fresh 3.2 installation without any modifications. I can't say that I'm new to SF, but this has never happened to me before. Could it be the GFX drivers? Or SP2? -Edit: My SF version is an european one, say I installed every SP from 1 to 3.2.

Gave SFP:1 a new try and got the problem fixed. The cause have been bad force feedback drivers fot my Thrustmaster Top Gun Fox 2 Pro Shock (worst...product...name...ever! *pant* *pant*). Updated them and SF worked. Weird.

Sorry for the long delay. It still doesn't work, even after re-installing Windows. Strange stuff.

You didn't read the entire thread, did you? ;) I said: It always freezes after applying SP2. But it can't be a bad patch, since it also freezes after applying SP2, downloaded from a different location. Plus, it can't be the GFX driver, since this freeze also occurs with the new Omega 25.83.

10.11.02 That's an US version, isn't it?

Maybe. But I don't want to revert back to an older driver, since the 5.10a is the best Radeon driver since the 4.12. I'll just leave SF untouched for now. The upside of this is that Falcon 4 will get some well deserved attention after a looong time. ;)

The guys at Thirdwire don't have an idea either. This is so weird...

Downloaded it twice from different locations. No success.

Yep, I did. - Edit: Deleted everything, rebooted and re-installed SF. Stock: Works. SP1: Still works. SP2: Freeze. - Edit: Re-downloaded SP2. Still no success. I don't f+cking get it. I've used Strike Fighters since it came out and I've never had problems with an un-modded installation. What the heck is wrong? It has to be something Windows-related since the only major change I've made was installing SP2. The GFX card driver is ruled out by now,since an SP1 installation works just fine. But from SP2 on, nothing will work anymore.