Lt. James Cater

You have to wonder about anyone ripping Thirdwire games. Hell, they are easily the most affordable series i've ever seen. I even picked up WOE at Frys for $10. Next month should be getting both WOI and First Eagles.

Doing this stuff, your first mistake will most likely be your last!

Given a choice, i think i'm better off saving for a few weeks and getting TrackIR.

I know someone discussed it some time ago but i just can't seem to find it. The last time i flew Thuds in WOE it kept tasking me for intercept missions and such that were not remotely what the plane was supposed to do. Someone else had the same problem months ago and a solution was provided but i just can't remember exactly what was the answer. It involved deleteing something in a file. Can anyone clue me in?

Every version of the 105 was deployed as a strike aircraft of one form or another. The D, F and Gs were the models used in combat as mostly everyone here knows. Speaking of which, I nailed a MIG19 a while ago in WOE to make it my second ever kill while driving a Thud!

Yo Wrench, when i go to the objects folder and go through the aircraft i've yet to see anything like the info everyone posts here. All i find is the configuration settings. Personally, i think that if it is so basic, no one should ever have to ask for assistance in matters such as this and we shouldn't need anything like an extractor. No complaints, but this is not as cut and dry as it seems.

It'd be really easy if i knew how to find the data.ini in the first place. At the moment, Wrench's advice is the best thing i have

Thanks for the advice, Wrench. I really like WOE and have only minor quibbles. Having to click back and forth to avoid unusual missions in a Thud is one. As of this post i've started another WOE campaign and i'm in an F-105 again. SAMs might not be the problem like WOV, but i recently had everyone in my flight shot down while disengaging from an CAS mission. On the last strike a Mig19 managed to put a few holes in my plane before i went low and got away.

Thanks for the heads up concerning .dlls. Good thing i just looked but didn't mess with them. I can't find the .ini for the life of me. I can see the configuration settings easy enough, but that's it.

I hate to bug everyone but it's my first time messing around with DLLs and i want to make sure i get it right and not screw things up. For starters, when i open a DLL i use notepad and everything looks like gibberish with a "Can not be run in DOS mode" the only thing that makes sense. Can anyone point me out towards some page where i can at least guess at instructions? Wrench's reply is the solution. I now have to work through the problem and i'm flying blind right now.

Thanks for the info. I'll see what i can do after i get out of work tomorrow morning. I have to catch some zs now. As it is it looks like i'll have to download somehting to properly work in those files.

You consider the "SAM Launch" call unhelpful? Annoying yes! But i consider long term survival withought it doubtful.

Reading the manual is the first thing someone should do. Going out practicing and having "i wonder what will happen now?" moments is just as valuable as far as i'm concerned. Instinct helps a lot. The first time i used an F-4 the roll tabs made sense as soon i changed direction. Also, i tend to rely on the MK1 eyeball for judging distance in A2A. Perhaps i should use the range bar, but i'm too used to keeping focused on the target.

Don't sweat all those technical details found in the manual. My advice would be to download "The Range" with the link supplied above and test out different things there. Once you choose the weapon and the sight adjusts, knowledge of chosen weapon, the circumstances, and common sense will be all you need to factor in before delivery.

I built countless models back in the day and none are even remotely close to what this guy does. Excellent work!

It all depends on certain conditions. If you are flying a mission in lousy weather, a Maverick might not be the ideal weapon for taking on SAM sites. Recently, i used an F-4E loaded with 2 Standards and 2 Shrikes. While my wingman went after the target i was up over the cloud deck at about 33,000ft, throttled back and listening to all the inbound flights as well as studying the scope to determine which and when certain sites needed to be dealt with. One Straight Flush on my wingmans egress route was taken out at a distance of 22 miles from 25,000ft. That you can't do with a Maverick.

Hey Dale, thanks for starting this thread. I've been meaning to find and download it but it kept slipping my mind. Earlier i did and it's already bought benefits in the use of Snake eyes!

A while ago i loaded WOE onto my ancient and junkyard bound Dell 4400. To my surprise it worked and with damn good performance. With my usual settings i had a bit of slowdown but a dropping a few things such as object details down to medium and it was good to go! PS- ! always use mirrors and far horizon.

I have my own version of that one... While flying F15s, my wingman got shotdown by a Blindfire tailgunner and so i got ticked off and decided to get revenge. Closed in for a gun run, missed, tried again and was promptly shot down. I wonder what kind of medal that Gunner got?

Experience has taught me is that ECM allows you to pretty much disregard SA2s fired further than 15 miles as long as you are not heading towards the SAM site. SA6s still have about roughly an 85% chance on you though. When one of those is coming up, head for the weeds!

I'm looking for info concerning others' experiences with this missle. In WOE, two campaigns have come to an end due to this SAM. In both i was carrying ECM pods but obviously it did little good since i was shot down. Worse is that my squadronmates got the chop too. One i was actually keying in orders to send him home when he was hit. The range, height and bearing to the site were so similar in both cases that i figured i'd come here and ask if anyone else got nailed hard by this SAM and can ECM help defend against it. For some reason it seemingly has my number and i wonder if the ECM is having any effect. In both campaigns i was flying F-4s successfully until going on deep strike missons.

In my latest campaign, the SA6 is now the official bogeyman. Dring my last mission my wingman got blown away and i had to do no fewer than 5 approaches to a runway target to keep from getting hit by a SAM6. Judging from what i was hearing , AI planes were getting cut to pieces by the SA6 while i was trying for a bomb drop.

The stock campaign setting is alright. Imagine having to deal with wanting extra aircraft with you on a deep strike but not having enough drop tanks to go around!

Best way to go about it really. On my stick one button is for air to air, another is for air to ground. Beats the heck out of having to hit a key at a crucial moment.

The one thing that keeps coming up in the comparison between the two aircraft is dogfighting capability. I don't know about anyone else here, but whenever i drop my bombs on a target up in Pack 5 or 6 my natural inclination is to get the hell out of Dodge as fast as possible. Sticking around to go mano a mano with MIGs is something that never even remotely enters my mind. SAMs and AAA are bad enough to face on a daily basis. Get cute with MIGs enough times and you'll end up on the wrong side of a gunsight sooner or later. Why bother decreasing your odds of survival by spending even a second longer than you have to over enemy territory?