AussieFX

Can't find the trigger point in the 2nd mission. Outpost on top of the hill (can't recall it's name) I landed between the tent and AA gun - no joy. Anyone found it?

Thanks mate, I just paused it and thought I would check in to see if there's a solution. You're a lifesaver! Oops in reply to ariyaner

Yeah, same problem. Is it all the quick missions broken? It's a shame, I enjoy this bird. At least they are working on a fix.

Worked a treat. I was just about to give up on this module and all it was, was curves. Funny thing is I don't usually have curves set with the helicopter modules. Cheers!

I've had the same problem with my G940. Will try removing the curves, thanks for the tip!

The TF-30 is an interesting engine that's for sure. It seems it was one that required the right airframe and even the right inlets to perform. It's interesting reading how troublesome it was in the F-14. I would love to know when pushed how fast a TF-30 powered F-14 really was.

What is being said is we "might" be able to get the aircraft to work in Nevada without the radar if the bug can't be found soon. Not that they would stop searching for the bug in the meantime. It's just a way of getting to fly the Nevada map whilst they continue working on the fix.

Thanks for the update Nicholas. :thumbup:

Any update on progress with the patch?

Hi, since the 1.5 update and now in 2.0 my x+y axis (roll and pitch) have become ultra sensitive. To the point where it's unflyable, even the slightest twitch will send me out of control. I don't normally use curves in any modules but it's so bad in the F86 I've had to drop the sensitivity of both axis to 50% and now it feels like a flying brick. I didn't have any control problems in 1.2.x. I'm using a Logitech G15. FFB. Anyone else noticed a change, has there been a change? Thanks. EDIT my hotas is a G940 not G15...duh! Too much Logitech gear here.

Cheers. Never operated a T53, pretty much the same as most I've operated it seems (C20's, Arriel mainly) IIRC the 2 minute warmup was a company requirement. I've been wanting to shoehorn a time expired T53 into my ski boat for years. :D

How about night flying? That's where my logbook is not working.

Something wrong with your puter champ. I don't have any problems at all in LV, always stuck on 60 using frame rate control and I'm only using an old 290X with no overclock. All settings on max 2560x1440 DoF off.

I have noticed that any night flying is also not logged in any of the modules or as a total. Once the sun goes down the logbook goes off to bed to awake again in the morning. :) Anyone else seeing this?

No. Doing that will get you a molten lump of exotic metals. You need air running through the motor before adding fuel. IRL you let the engine idle for 2 minutes before rolling the throttle up. (slowly) Same with shutting down. Idle for 2 minutes. Procedure should be, gas producer to 12% before adding fuel, lightoff, keep the starter engaged until it hits ~50%, (gas producer should increase to ~60-70%[unfamiliar with the T-53]) idle for 2 minutes, then throttle to full. Beep until the power turbine stabilises at 100%. I use the home key to engage the starter, then use the mouse wheel to roll just past the idle stop and then roll it back down to idle once the motor has reached lightoff. My guess is the fire is being caused by getting off the starter too early. Something has changed WRT temperature modelling in the Huey, it seems to me it's a work in progress and this flame is the first step.