Frederf

Post #4 details how it used to work. It should still be there somewhere but I don't know where exactly.

Track provided AH64 Master Volume Knob Initialization.trk

Yeah "starts" but it's a blend of the new input. The tau time was 1.3 seconds or something on the Ka-50. You could even go into the lua files and adjust it to your liking.

The old trimmer mode in other helicopters had a blending time. Does or does not this "instant" trim work with a blending over time or is it literally zero-seconds-instant?

How about a check of the attitude of the airframe taken from the outside? The GC might be correct relative to the ZSL/AD just the airplane is riding nose high.

Assuming the generator produces 400Hz naturally and disconnects under 306 Hz that's 76.5%. I'm a little confused that it says under freq protection doesn't work in flight but then describes the flight under frequency protection limits. The other is <100Vac (normal 115) but that doesn't function if under freq protection is which it wouldn't be (unless it is). If potential vs speed is linear (looks like other generators are about so) that would be 87% which is roughly what the ground under freq ratio is. I don't see any particular requirement for electrical power to operate the flight controls. Aerodynamic and hydraulic RPM relationships would be my primary and secondary concerns.

I was looking for electrical generator disconnect conditions. The only one I could find was a >1s while in the flight condition below a certain RPM. Depending which part of the system the generator is on (probably rotor side) that would tie the fate of the generator power to rotor RPM. Hydraulics I don't know if they are on engine or rotor side but traditionally hydraulic pumps are quite non-linear (lose 10% RPM lose half power type behavior).

Yes, classic initialization bug. When you get in the cockpit it looks like the MASTER knob is at maximum... it's not. The graphics for the knob show it fully CW but the value of the knob's position is fully CCW. It's not that it "activates the squelch" but that the knob was at the zero volume position before you touch it (despite looking otherwise) so there was static non-squelched signal present the whole time, just at zero volume. The moment there is any adjustment to the knob the graphical position and the logical value synchronize.

The GC is placed in a fixed location on the HUD, the ZSL. It shouldn't change regardless of alignment, etc. as far as I know anyway.

LMC deals with relative motion; helicopter, target, or both. There is also an optical image object tracker.

Chart scales have an associated chart imagery layer slot associated with that scale. Some of the slots have chart imagery loaded and some do not. You can adjust the map range to chart scale association to use a chart scale with imagery. To change the displayed scale for a certain map range: TSD displayed MAP (B4) select Range (R1, R2) set desired range scale TYPE CHART (L2) verify SCALE (L3) select Option (L3-L6, R3-R6) select desired scale MAP (B4) deselect Whenever the map range is changed the associations will revert to the default. Caucuses has the following scale imagery: 1:5,000,000 1:2,000,000 1:1,000,000 1:500,000 1:250,000 Syria has the following scale imagery: 1:1,000,000 1:500,000 The scale menu realistically won't show or choose chart layers with CADRG graphics that it doesn't have loaded so the blank layer issue won't happen in reality. I also think that the scale association is memorized when changing range settings but I'm not sure on that.

Thank you for this. Does DIR/LO/HI change the flight profile for LOBL launches or are all LOBL launches the same flight profile regardless of trajectory setting? Does an e.g. LOBL/HI fired missile fly to a particular point if LOBL laser is lost mid flight? LOAL/DIR assumes the currently active sight point (HMD, TADS, etc?) as the missile launch target and LOAL/LOHI assumes the ACQ point? Is there any warning or indication that one is inside the minimum practical range for shaped trajectories?

What happens with this option on and off? I never thought about using the "request control" function in single player.

Here's the same idea displayed as controller buttons on the TEDAC grips. I think I'm going to use this one to help me "think Army".

Narrow field of view. The Maverick has two zoom levels and the missile works better in the narrow (zoomed in) one.

Gotta calibrate your missile to your TGP for auto handoff to have a chance. Then on use make sure to have NFOV on the missile. Even then the TGP will track much farther away than the missile. Don't expect more than 5nm on average missile vs point target.

The IAT isn't in now I don't think. It should have it at some point. The controls would be IAT-OFS on the LHG and the A-O-M and W-A-B switches on the RHG. Edit: AOM sets LST option

Certainly. It can have five shift layers and lots of contexts for each button to the point that the human brain can't hope to remember it all. The goal is to put things in logical places so first guess is right.

This is my old WIP picture. I'll make a better one in due time. Color coding is black unshifted, green LB shift, red RB shift. I just realized this moment that I can bind Xinput buttons as well as keyboard emulation so I have gone in and used all possible Xinput output instead of some keyboard macros. This will reduce the number of keyboard macro commands by 14 which is always a good thing. AH-64 TEDAC XboxOne Frederf.rewasd

I intend to share both TMWH scheme picture and script (and input lua if desired) plus TEDAC picture and reWASD profile. I bought the base software plus one $7 upgrade for a needed feature. The whole product comes in cost units as you add feature packages which I'm sure you can add as needed. Minimum cost is two units and maximum six with all four upgrades. My profile needs three. I forget the name of the upgrade needed.

OK, it locks out the temperature protections but the speed protections remain in place. That makes sense. I would have guessed off to reset too but looks like idle is enough. Someone jockeying throttle manually would probably be midrange. One could possibly manage to dip to IDLE in flight long enough to reset (especially one at a time) but hard to imagine a situation. Perhaps inadvertent lockout engagement and/or misidentification of which throttle was needed to be locked out. Is lockout recommended for SE flight or is it expected that SE one remains in fly range. Is lockout for failures or issues with the TGT limiting functions?

Looking at the TM there's no special condition for chop that I can see plus it should have a voice message and EUFD annunciation as well. I got the emergency jettison button to work (removing cover first which isn't animated). I don't think chop is currently implemented.

In my case yes as the three zones are set to none, keyboard insert, keyboard home. This would cause the zone II to zone III transition to release insert and press home and then do the same process in reverse on the zone III to II transition. Potentially this causes the release to activate the first state lasing sequence. I also get the rumble feedback in both directions. However now that you mention it I have edited the profile such that zone II holds insert and zone III holds insert+home both. This should cause the first stage to be held continuously across zones II and III. This should behave more like DCS expects and not produce a first stage laser event when releasing the trigger.

I'm using reWASD which has a nice feature that you can associate rumble events with bands on the trigger axes. I put a distinct rumble at first stage and second stage trigger so there is no ambiguity when I hit each.

When lockout logic is selected how long does it persist and how is the logic deselected? You mention that the engine could shutoff in lockout for self preservation. What are the limits in fly logic and lockout logic?