Spidey209

I have had a lot of success with FreeTrack and FaceTrackNOIR. I don't have any money to waste on systems like TrackIR so the open source way is the way for me. The latest and best though would be OpenTrack with a gyroscope android device\phone. Hi-fidelity tracking, no LEDS, plugnplay and go.

As a graduate of Chuck Yeagers Flight School I highly recommend the technique taught. The first thing to get right is the role of elevator and throttle at low speeds. Contrary to instinct the stick is used to control speed and the throttle is used to control descent rate. Why - because using the stick to control descent rate and the throttle to control speed gives the opposite of what is desired. The Wrong Way - Too high on approach, push on stick, plane increases speed - not what is required. Too low, pull on stick, plane slows and descends faster - still wrong. The Right Way - Plane too high, pull back on throttle - plane descends. Plane too low - add throttle, plane ascends. Plane too fast - pull back on stick and plane slows, Plane too slow - nose down and plane accelerates. Your goal is to keep the end of the runway at a constant spot on the windshield. If it moves up the windshield you are falling short - add power, Plane too fast now, pull back on stick. If the end of the runway is moving down the windshield you are over shooting - push. Aim for airspeed about 30kmh over stall speed and constant angle of approach. Use the turorials\videos to see what is should look like. Start a long way out to give yourself time to get it all under control. In reality you will need to juggle the throttle and the stick to maintain speed and angle of approach. Lastly - and the hardest for me - I have trouble telling how high off the ground I am and so I find it hard to guess where to flare. And I usually forget to hold the nose wheel off resulting in burst front wheel.

The F-15C HUD Waypoint marker seems to be bugged. If I am flying to a waypoint that has bearing 350deg say, if I fly to the left of the waypoint the caret is okay. If I fly to the right of the waypoint, past 000deg the caret flicks over to the hard right of the HUD compass tape, indicating that I need to turn right for 340deg to get back on course rather than turn left 20deg to get back on course. When in a hangar, the F-15C RWR appears to be working normally. Shouldn't the walls of the hangar prevent threat detection? or are we not fussed about what goes on in hangars?

I have the same problem with the A-10A bombing TDC. Left - Right is okay but up - down is borked. The maverick TDC works fine, just not the bombing one.

It has been a while since I did it, but # run the patch from inside the game folder, where the newinput.dll resides # run as administrator Yes, I run Win 7 64 bit with no probs now.

If you are using the in game settings to adjust your stick, I usually use 25 to 30 on the curve with no deadzone or just a bit on the rudder. In FC1 the Su-25T uses the Advanced Flight Model and it was recommended using no curve, which works for me. I believe it is the same for FC1.

I only got the dang thing working today so I haven't had a chance to run multiple games. Suggestion - make sure none of your key combo's in FC2 are disabling FTNoIR. The older version of TrackIRFixer can be downloaded from their site http://naturalpointofview.blogspot.com/p/trackirfixer.html Just below the big, bold dl link is a link to the older trackirfixer. I think you need to run it from the same folder that contains NewInput.dll i.e. ..\Flaming Cliffs 2\bin\x86\stable\

I have spent quite a few hours searching these forums and others trying to get this combo to work. In the end, the solution is to NOT USE the latest version of TrackIRFixer 1.3 - Use the TrackIRFixer1.2.0.18 version. 1.3 changes some bits in memory and just doesn't work for me 1.2.0.18 patches NewInput.dll and works for me.

I got FaceTrackNoiR to work perfectly by massively upgrading my hardware. FC2 went from 40fps ( settings Medium ) to 120 fps ( settings Max ) FaceTrackNoIR also benefited massively. If hardware upgrades aren't an option, I did get FTNoIR to work very well using these tips. # Make sure your face is evenly lit i.e. Left \ Right side not brighter than the other - you get assymetrical responses if you don't. # obviously, better lighting = better experience, but I could still play in dimlight, I just had to play with the camera contrast\brightness settings until I got a good face lock. # Play with the filtering ALOT. It took me a while to get the balance between response time and smoothness right. Of course it all changes when you change from night \ day, but it only takes a moment to correct

I can't even get the C:\FTNoIR_ED_HeadTrackerLog.txt to show up :(

I have been using FaceTrackNoIR quite successfully for a while. I still can't get it to use the FreeTrack or Fake TrackIR interface's with any of the solutions posted in these forums. It just refuses to work. I have to use PPJoy which seemed to me to be less responsive than the FreeTrack or Fake TrackIR interfaces. This is a problem because now I use Windows 7 which only allows you to run PPJoy when W7 is in driver test mode. Then a great mate gave me his Super Rig to borrow. My FPS went from ~40 fps ( medium settings ) to > 120 fps ( Everything MAX ) just to give you an idea of the improvement in processing Horsepower. So - to finally get to my point. I noticed a dramatic increase in effectiveness in FaceTrackNoIR + PPJoy. Suddenly the headtracking was smooth and responsive. I could turn the filtering way down further increasing the responsiveness. A lot of the problems people are having are just hardware not up to the task. Not saying the hardware sux, just that the taskbar is set very high.

Change to a different target, or blow that mo'fo up

There is no "bug" with the maverick's slewing AT ALL! The problem is caused because the slewing uses acceleration so when you first start to slew the cursor is moving at zero speed. If you are slowly yawing or pitching the cursor cannot keep up with the change in angle until it speeds up enough to overcome the pitch\yaw angle change. So what is happening is you are slowly pitching down and you want to move the cursor up. You hit the hatswitch up "unlocking" the cursor. The cursor up speed is initially not fast enough to overcome your pitching down so it takes off in the wrong direction i.e. down. When it accelerates to a high enough speed to overcome the pitch down motion it then starts moving in the correct direction i.e. up. Solution - hit "attitude hold" when you are slewing the cursor. It will lock on faster so you don't need to hold it for long.

My only kill to date is a hasty 9 shot on a friendly. I wasn't expecting the HUD to start flashing ( <<<==== RTFBriefTard ) and I paniced. I also got into a knife fight with a Mig-29 in my F-15. He bugged out and I closed in for the kill only to see him pull further and further away. Thats when I noticed the ground was moving slower and slower even though I was at full afterburner!!! Check fuel gauge, sure enough, it reads E=Ediot. Technically a loss, but I landed some hits, so it feels like a win.

Practice flying sideways. Once you can do that, throw in a bit of rudder to keep the nose lined up with a point on the ground. Once you have that sussed you just have to adjust the radius of the circle to counter balance dropping the nose to actually nail something on the ground.

So, the "Funnel" is the chopper version of the "Cobra" . Looks cool but results in RL may vary! It was a useful technique in BF2. Good for getting those baddies hiding behind trees.

I can accept that vulching is bad online ettiquette BUT ... ... is it bad ettiquette load up a bunch of runway cratering bombs and take out the opposing side's airfield?

GG, the only time I want you in the centre of the HUD is to fire a missle, on the basis that any direction change in the beginning of the missile's flight will have a more drastic effect on it's energy. It just so happens that with Snake method you conveniently cross across the HUD every pass. Snake method would be "more" effective against an unknown TWS ET shot because at least you are maneuvering ( vs F-Pole method ) You mention a very important point, the unexpected, unknown TWS or ET shot. This discussion has been about a Head to Head with a known incoming missile. An Ace would avoid this situation like the plague and work towards a shot that the victim doesn't see coming. A topic for the advanced class. Q How do I avoid an incoming Missile? A Don't be there in the first place.

Just a question\comment on the snaking method. It is an attractive option because you keep pulling the centre of your view instead of leaving him out on the gimbal limits where he may drop off and break your lock. It also lines you up for a direct shot as he sweeps across your HUD I am instinctively wary of this method because the missle will also follow a snaking path. Anyone who studies sine waves will know that there are portions of the missile's path where it is not maneuvering and is heading straight for you i.e. not bleeding energy. Turn right\left 40deg and maintain constant angle against the missile will cause the missile to continously bleed energy. Q Which method will leave the missile with the least amount of energy at the convergence point? p.s. The year is 2010 and my work colleague has just put a "Spice Girls" album on in the warehouse. Do I have grounds for a complaint?

A nice philosophical summation A.S. Unfortunately it is a bit lacking in detail for us nOObs who require a much more prescriptive approach. e.g. STEP ONE Wait until bandit launches STEP TWO ..... p.s. The Greek plates ... Aussie Big Boots .... was a bit of inter-cultural teasing i.e. a joke or two. Here's another! Q Why do all the trees on the East coast of Australia lean out to sea? A Because New Zealand sucks!! Q What is geographically wrong with Australia? A It is above sea level!

My dad, his best friend and six others went to the Ukraine and bought one of these. After a few weeks of repairs and fitting extra fuel tanks they set out to fly it back to New Zealand, a trip covering nearly half the globe. They got as far as Alexandra before seasonal weather forced them to leave the plane in storage and come back for it 6 months later. Unfortunately Dad was broke so he didn't make this part of the journey but IIRC he joined them in Sydney to make the last leg of the trip. He co-piloted it at a few airshows before it was sold. It was cool to see such a massive prop driven plane near hovering in a mild headwind. He died of cancer not long after so I always get a bit "emotional" when I see the An-2's lined up at the airfields in LO.

Awesome vid Funkster, I have read much in the forums about missile performance being under modelled. A single long range stick seems ridiculously easy to dodge. Are we meant to be playing with the missile slider set to 100??

Fantabulous stuff DoctorK!!

LOL!! GGT I tend to concentrate on the things I think are A) getting me killed the most B) Preventing me killing the opposition. To date A and B = Can't find the buggers.

Wink at each other??