heloguy

Which files did you end up moving? I'm having the same issue.

One thing I just noticed, and forgive me if it's been brought up, but I definitely don't remember ever seeing that type of stabilator with hand holds. The hand holds only showed up on the foldable version that is more rectangular in shape. The version in the mod seems to be a melding of the two. A real small thing, though, thanks for the great mod! Edit: Nevermind, just saw in Discord that it's known, and not a priority, which is understandable. UH-60L: UH-60M:

@BIGNEWY, sorry it took this long to take a look back at this. In the middle of a move, but just gave it a shot. I've since moved on to using Chuls's BrunnerDX w/Arduino adapter so my Brunner has actual FFB effects, but when I reset back to using hardware trim with the Joystick without Springs or FFB option, low and behold, the pitch oscillations are gone. Looks like you guys have it solved! Thanks!

I'm not an F-15C RWR expert, but proximity to center of the RWR display has nothing to do with physical location of the threat on most aircraft. Instead, proximity to center usually is based on the pre-determined (ie, programmed) level of threat. For example, if a surface to air threat radar is in search mode, it will be toward the outside of the display. If that surface to air threat switches to acquisition, or track, it will move toward the center of the display. The only indication of physical location is the direction. The system can't determine the distance to the threat. In this case, the F-15C's RWR is programmed to show that the JF-17's air to air radar is a threat of the highest priority, therefore it will always populate toward the center of the display. I may be oversimplifying this, so someone who knows better, please chime in.

Well done, and thanks!

At least they ended with an exciting refuel.

I hear you. I wonder if it has something to do with the Army, or when they were developed, as H-53 engines are GE T-64s, and have no TGT limiting. They also don't have any electronic governing, so again, maybe it was something implemented later. Automatic bypass of limitation based on rotor droop may be something that needs a FADEC to implement. Maybe the simpler electronics of ECU/DECU aren't able to handle those kinds of operations.

Or, what? You don't shoot guys that appear to have manpads with a missile because it's 'too expensive?' This is ridiculous... You shoot the weapon that provides effects that meet the commander's intent. Usually, part of that intent, is that crews and equipment make it back to do more missions. The cost of munitions is pretty much never a factor in combat. At any rate, if an attacking force is going against a sea of manpads, they'll use a different way to attack the enemy until that threat is neutralized.

Actually, yeah, it does. Unless something has changed with 701s. Lockout is a mechanical bypass as Raptor explained.

Mechanically bypass the torque motor inputs and control the engine manually?

Well, despite theories of why you would go to lockout, lightspeed included, I'm only curious if it will be modeled. By no means was I talking about using it on a regular basis. Only in the emergencies it's prescribed for.

No, I didn't. You did. As a helicopter pilot for 15 years, I understand what the limits in the book mean. I also understand that in an emergency, you do what you need to do to ensure crew survival. The limits in the book protect components from failure before their scheduled time before overhaul. They aren't the point of failure. There is a safety margin built in by those limits. If you exceed them during normal operations, you'll probably be fired. If you exceed them in an emergency, you will be investigated, and potentially fired. But if you saved a crew from death, or an airframe from destruction, you probably did just fine.

This is true. In normal operations. But if you have put yourself in a situation where your rotor is drooping, and collective reduction is not an option, manual operation of the power levers (lockout) may be the only option to make the situation survivable. Every engine is different. The limits exist so manufacturers can guarantee time before overhaul (TBO). Not because if you exceed them you’ll have an immediate failure. On the other hand, if you fly around with the engines in lockout, power levers maxed, rotor RPM through the roof, not only are you doing it wrong, but no one will be surprised when you do smoke an engine, or seize a transmission.

You could use the realistic way with any controller. You’d just need to press a button to let it go back past idle for shutdown.

I’m really talking about the situation where if you just go with the initial drooping rotor, you’re going to crash anyway. Then, again, bill me if whatever little power it has left is enough to prevent that. Acknowledge that the main reason for lockout is in case a DECU fails.

It's definitely true that you don't want to exceed the aircraft/engine limits in most situations. If a drooping rotor is in between me being alive, or that engine being torched, though, bill me.

It would be nice to be able to do it the way it actually works, though, for those that want it.

I think the problem someone might have with this is that you don't have to press the IDLE STOP REL button to advance to idle. Only to go below idle when you're shutting down, so it's not realistic to how the aircraft is actually started. You should be able to pull the trigger, wait for N1 to rise to the appropriate percent, and then simply twist the throttle until you are past the idle stop to introduce fuel. Small difference, but it might matter to some.

That's the way I understand it. Just wondering if it will be modeled in DCS.

Hi @Chuls, I tried your link from Discord, but it I get a 'not found' error.

Any chance for an updated Discord invite?

Little fast for AR in a helo. In a 60, 110kias is standard.

I'm not a 64 guy, but I know what lockout is. I see the lockout label on the power levers. Will this function as it does in the actual aircraft?

Do you have to use Ketegys mod? Whenever I try that mod, I get random crashes to desktop in VR.

I don't think anyone is asking to remove the current throttle functionality. An option under the special tab, just like say, force trim, that allows the entire throttle axis to be controlled by a controller axis, with the caveat that it will not move past the idle stop unless it registers a button press for it (much like it does now).