To: devnull (Falcon3 Mailing list) From: devnull (Falcon3 Mailing list) Reply-To: devnull (Falcon3 Mailing list) Sender: devnull (Falcon3 Mailing list) Errors-To: postmaster@onion.rain.com Precedence: bulk Bcc: falcon3-outgoing Subject: Falcon3 Digest V4 : I72 Falcon3 Digest Volume 4 : Issue 72 Wed Sep 29 07:46:33 PDT 1993 Compilation copyright (C) 1993 Jeff Beadles Send submissions to "falcon3@onion.rain.com" Send add/drop requests to "majordomo@onion.rain.com" Archives are available via ftp from onion.rain.com [147.28.0.161] and mirrored on cactus.org in /pub/falcon3 Today's Topics: Trimming jjsterre@acs.ucalgary.ca Mig 29 Traumas :-( MORGAN@WVUGEO.WVNET.EDU Re: Need a virtual IP (Instructor P cisko@d0tokensun.fnal.gov (Greg Cis Bornstein's Book in Boston? "Dean Redelinghuys" From: gem@usl.com > Subject: Need a virtual IP (Instructor Pilot)... > 1: Dodging missiles before the merge. I try to position myself > (as per the manual) such that they are coming in at 45 degrees > and turn into them, and this seems to work for the all-aspect > heat seeking missiles, but I can't seem to find the best distance Well, radar missles are though, when coming at you from in front. I had thought I had all the missles figured out ( SAM's (Radar & IR) and AA Radar & IR). I am pretty much able to survive ALL of these. Then an ex-net buddy of mine, [ who has since told me to soak my head :-( ] pointed out that Radar missles coming from in front are darn near impossible. He was right. I haven't a sure fire method for dealing with this. The best method does seem, to not let the bogey fire a missle at you. Not very encouraging... > 2: I seem to have little trouble getting "behind" the MiG, although > I usually end up inside him and "above" him (if he looked out his > cockpit during his banked turn, I would be above one of his shoulders), > and can't seem to slide out to his turn circle to truly get on his > six without giving up too much distance (I am using padlock mode), > so I think what I need are pointers on flying a lag pursuit curve in > padlock mode (correct me if this isn't what I should be trying to do). I fly all of my BFM in padlock. With qualifications... I generaly use padlock more or less when my target is in front of my plane. If I am in a BIG fur ball, (where each is trying to get on the others 6) I use track view. No matter how use to padlock I get, it still is somewhat dis-orienting. The external view brings back some of the orientation (at least for me). When ever I use this method, it always works. :-) > > 3: And finally, once I get onto the MiG's six and start closing > to gun range he points his nose up and spirals away from me in > a turning climb until I lose too much energy. I am trying what I This could mean that he "Is feeling your heat". This is the classic way to dis-engage a fur ball you are loosing (well the classic way may not include the spiral). The most important part of BFM is knowing when to dis-engage!!! Dis-engaging a loosing battle is easy (in theory) all you do is go to [AB-5] and climb at a 25-30 degree angle. Of course if he locks on you & fires a missle as you are dis-engaging, then this method may not work so well. > Forget checking 6, I have a hard enough time keeping track of 9 through 3 > Sounds like a reasonable precaution!!! Greg "JAGUAR" Cisko _________________ __ \ * (0 ___ / | $ *@ (BOOM!) -===|============ @ @#$% <-<<< - - - - - - - [==\__| \| / ^& *( ------------------------------- From: "Dean Redelinghuys" Subject: Bornstein's Book in Boston? Greetings to the list. I have a question mainly for anyone in the Boston area. A friend of mine will be there for a few weeks (about a month or maybe slightly more) and I've asked him to get the Falcon 3 Official Combat Strategy Book for me. 1. Where would be the best place to get it in that area? (street address please) 2. Would it be cheaper if he mail-ordered the thing from SH? Thanks for all the help. Dean Redelinghuys |------------------------------|---------------------------------------| | Have another day. | redel@odie.ee.wits.ac.za. | | | | | ``There are no weird people | Postgraduate Student | | in this world - some just | Electrical Engineering Department | | require more understanding | University of the Witwatersrand | | than others'' Tom Robbins | Johannesburg South Africa | |------------------------------|---------------------------------------| ------------------------------- From: rm09@orzspr.op.dlr.de Subject: Campaign Squadrons There's been quite alot of traffic lately covering corruption of campaigns after switching Squadrons and when playing Falcon and MiG alternately. With the upgrade to Falcon 3.02, SH fundamentally changed the method used to store the `profile' for campaign missions, with the introduction of the file `mission.sav'. Previously, the mission profile for the selected squadron (say, the Fighting Tenth in Kuwait, campaign files squad0.*) was written to the file squad?.mis (squad0.mis in example) after the sequence `NEXT MISSION' - `LOAD ARMAMENT'and `TAKEOFF' was completed - so the mission profile was directly linked to its squadron by filename (same squad0.squ, squad0.cam and squad0.mis filenames). With 3.02, the mission profile is written when `NEXT MISSION' is selected, but to the file `mission.sav', (though on `TAKEOFF', the squad?.mis file is still generated). mission.sav is not specific to any particular campaign, but a generic storage file for the mission profile. What this means is that if you create the squadron Fighting Tenth, theatre Kuwait, then fly a mission, debrief and accept `NEXT MISSION', the profile for the upcoming mission (all the allocations for object types in the mission) will be written to `mission.sav'. If you now go back to the War Room and select another squadron, the profile read from `mission.sav' is not correct for the new squadron - when you hit `TAKEOFF' the symptoms vary from the expected computer controlled aircraft not turning up, to complete failure. To overcome the problem, backup your campaign files from the dos prompt, before you switch squadrons (or programs), as follows: 1. After selecting `NEXT MISSION', complete flight planning and go through to `TAKEOFF'. Once in the cockpit, ESCape and mission Abort, then ESC back to the War Room and finally the dos prompt. Make certain to complete the above routine, otherwise the mission profile in `mission.sav' will not correlate with that stored in the squad?.* files. 2. Copy the `squad?.*' _AND_ `mission.sav' files for your campaign to an appropriate sub-directory (I use \falcon3\`theatre'\day[1...?]\mission[1...4]). If you're not certain which `squad?.*' file (range from squad0.* to squad5.*) to copy, you could use a little utility called F3Supply (freely available from onion.rain.com via ftp and co-incidentally written by me ), to identify your squadrons. 3. When you want to switch back to your saved campaign, finish your mission planning as in 1 and backup the files with step 2. Then, just copy your original `squad?.*' and `mission.sav' files back to the \falcon3 directory, overwriting what's in there. You can freely change squadrons, fly old favourite missions, exchange missions, etc. without problems. I haven't confirmed this yet, but maybe MiG uses the same `mission.sav' file for its profile - it would certainly explain the co-incidental problems. The same solution should also be effective. Check Six... Ian "Terminator" Kent ------------------------------- [[ End of digest Volume 4 : Issue 72 ]]