kgillers3

So a. I don't think you're supposed to be posting those. B. If you would learn how to read that chart and understand what it's telling you you would understand he has up to 100% tq available to go however fast he wants up to 100% tq if the engines can produce 100% tq

that's not how it works, max range = the max fuel economy you can get per mile. If you go over it you burn more fuel for a little more speed. You become less efficient up to the max power you can pull which is the fastest you can go. With your conclusion I would assume you don't hover at all loaded in the aircraft. Especially OGE. You were pretty jerkish too him for not understanding what fault was occurring. I snipped his eng page before the error. If you would reference the manual you were quick to point out specifically chapter 5, maybe peek at 9. It's possible in some conditions to not have 57% tq I guess but unlikely he would be doing anything that limited. 122 kts true is well within the operating limits of the aircraft for most conditions. Sure in some cases you may burn a little extra gas, but you're not breaking the helicopter. within 30seconds after this fault occurs he gets engine 1 and engine 2 and high rotor overspeed's. I think the rotor is first if I recall. But just prior to the fault everything is within continuous operating limits.

don't need it and it's about 110 temp and pa dependent, gwt as well yes.

... whatever you say. What's max range.

nice dude

The setting I was referring too. If it is in automatically jumps over you can inadvertently go into lockout.

120 is fine. So I couldn't hear the game audio too well, but, there are a couple of things that could have happened. I'm ruling random decu failure out because seems odd that RNG would hit you with both engines. I don't know how you have your options set but it looks like to me that you accidently went into lockout, you never checked your rotor (pulled in collective to keep your rotor and engines within limits), your engines either destroyed themselves or hit the overspeed shutdown. Which you weren't prepared for so you never entered into an autorotative state and dumped your collective resulting in loosing all of your rotor rpm which is why all your screens shut off before you hit the ground. I'd check the main options special page to see how the lockout is set on there. The only other thing that it coulda been is a governor fail on both engines simultaneously, which is super unlucky. Possibly a bug on how those conditions presented themselves but again IDK random failures do random things. But to me it looked like you went into lockout which means the engines went ungoverned and ranaway driving both up with the rotor until they died either from overspeed shutdown or ate themselves.

HDGHoldExperiment.trk First, no re trim just releasing the pedals, as you can see it's beyond the ability of the system to hold that heading from cruise trim to hover trim, next retrim for hover, changing power settings with no pedal inputs, pedal turn right while sliding right, arrest slide, pedal turn right, slide left, I think here it didn't want to re activate all I did was pressure counter to the turn. Towards the end of this, I press and hold force trim release and you can see heading hold kick off with a slow right turn with my current pedal input. Towards the end I relocate to the bunkers, I think I retrim prior to beginning but I'm not sure, then same deal, no pedal inputs changing power settings and speeds then i do two sliding turns down. I hope you find my inputs helpful for a solution for you having a good time in the module. Good luck.

The way the system works is by breakout values, so you would have to re trim so the game/program understands your pedals are at the new "center" position. This should only affect your heading hold, the rest of the sas functions will remain in operation. Unless they tweak it in software for your specific use case, you would need the x to match your pedal inputs, and when you start your turn you would have to remember where that new neutral position is. However, I'm assuming without springs you don't necessarily worry about heading hold unless you're specifically retrimming. If you do I don't know maybe they have something to bridge the gap for a person like yourself and the logic of what they're trying to recreate. to be clear this is referencing the heading hold only, not the overall stability system.

sometimes you gotta tap it back and forth back to the neutral position, do you have a deadzone? If it detects it pushed out past the breakout it won't reengage

So, just played with it, I'm able to get heading hold to reengage without retrimming, so once you have everything set, start your turn by applying pressure, the apply a little pressure opposing the turn and relax and see if it reengages for you. I can provide a track of my inputs if that helps Haven't really messed with it since the update apologies for the poor information initially

Ensure your sight select is HMD(lower left hand corner C-HMD), then use those up down buttons, if they don't do anything press the asterisk ( * ) for ~2 sec then hit them. If your sight select is TADs they are modifying the TDU

They're experimenting with velocity hold per the latest update, heading hold automatically engages when the aircraft is appropriately trimmed for the conditions is the easiest way to say it.

Att enables all the hold modes and it’s based off the speed of which you re trim the aircraft. so you’re “autopilot hover” or position hold will come from that att button and the fmc will adjust based off how you trim it. However there is no position hold yet, velocity is 5-40, >40 is attitude hold, <5 is position hold (hover hold). All from the att button.

Retrim will reactivate heading hold. I have not been able to have it reactivate as I expect it but the scas is wip especially the hold modes.

Retrim

So I know I personally ran into issues where I thought I bound things in the front seat and actually bound or re bound them for the backseat. The other thing I think I can think of is verify that your force trim release / u is bound appropriately with your modifier. I just tried it out and it was working appropriately for me after I took the controls. I hope this helps, good luck.

I'm using this name the next time someone asks me about them though.

You’re in the wrong seat. you have to be in the front seat, then verify laser is on, and you must sight select tads. Hellfire can only be fired as a remote from the back seat, I guess you can have George lase something and you was hellfire and fire but I think he stops lasing you’re also going to have to bind all your front seat keys if not done so wpn > util > laser and aight select tads from the front seat.

Check to make sure you have the Laser powered on via Wpn > Util, also ensure your sight select is TADs. Just a shot in the dark.

I'll give this a go as well, maybe I'll use NVG's more, thanks!

Tail rotor is connected to main rotor. When you push pedal changes tail rotor blades collectively. Increasing the tq. Left pedal in this case also can droop your main rotor when your power limited. Now I’ve never been on the ground at flat pitch and dumped a bunch of right pedal in so idk what would happen with the tq. trim ball is changing because your tilting the helicopter in roll axis by changing the thrust from the tail rotor. If your tail wheel was unlocked you’d see it tilt still but just not as excessively. Hope this answers your question @Caldera

As soon as you sight select tads your acquisition source option for tads goes away because the LOS is where the tads is looking, that would be my guess what is occurring, you're in the front seat, select acq tads but your sight is HMD (your helmet), you're telling the system you want to use the tads as a sight so you sight select tads and the acq source option in the front seat now goes away and Tads is no longer an option for something to look at.

lol

glad it helped, just keep with it and keep saving nr, like I said as is it’s not the easiest thing to auto but you can auto it. just keep playing with it and have fun. @bradmick