Frederf

ACM specifically doesn't utilize TMS left for anything so that interrogation is possible. Remember that AIFF interrogation is valid against both air and ground targets. You can TMS left to interrogate in A-G/FCR GM. TMS left interrogates with very few exceptions: WPN SOI, RECCE, or TGP After receipt of a DL TOI (displays DL CAS or DL SEAD) Even if the FCR is off or standby the AIFF will still interrogate. TMS left in ACM should interrogate (and not drop lock).

I had a similar issue when setting a height of 100' with radar altimeter off. George crashes into the ground because the terrain is 1100' elevation and he was trying to fly 1000' under ground. An AGL/MSL hint after the George UI would help to know when he's referencing height and when it's altitude. Additionally when flying near the ground George shouldn't be reliant on any instrument as reference. If he can look out the window he can fly 100' AGL.

This was the first mission that I tried with AH-64. At first I expected a command post truck to be parked at the base of the dam due to the intel images having a "CP" marked there. Destroying the Dog Ear the convoy moves on. Disappointingly the FARP never materializes. The action at the town is quite convincing but takes a looooong time to happen. I sat and watched and it took 75 minutes from mission start. I haven't experienced the rest at all beyond that. Enemy forces are good, threatening but mild, a bit too easy to see but that's good as a practice for me. I would like to see some kind of interesting weather. 20C 760mmHg gets old. I do notice significant winds. I hope Paris gets some visual landmarks. The low texture terrain makes it difficult to judge landing. I was flipping back and forth from F10 to try to hit the invisible FARP pad (should be hidden?) and crashed.

I read that the IDM works over each crew's radio selection for IDM so it looks like the pilot and CPG can IDM over different radios. I have no idea how that works.

LRFD 1/2 does a triple shot similar to an Abrams. There might be a certain logic where it compares the ranges from the three pulses and takes an average, rejects some, warns about backscatter, etc. that isn't present at the other trigger position. LRFD 2/2 does continuous ranging/designation. I suspect there is some value being lost compared to the canned triple shot logically although obviously it's critical to lase continuously when designating for weapons or when constant range measuring is required. One aspect to consider is that a lot of vehicles have laser warning equipment and lasing carelessly has tactical implications. I have yet to find a practical reason why in DCS you can't be just fine with second detent only. Weapons 1/2 does fire by consent. If I only had one weapon trigger I would bind it to this and just live without override capability. I'd rather have it prevent bad launches than allow good ones. Weapons 2/2 overrides consent to fire regardless.

What other platforms is the AH-64 able to interact with datalink-ly (with and without intermediaries)? For cooperative (Apache-Apache) Hellfire attacks can the laser prompt timer be communicated electronically to the designating platform?

What about the specific glide behavior to increase loiter time for reacquire or flex logic? A loss of track HARM should neither go ballistic nor resume destination travel unless the TI/GS setting inhibits these features.

I believe it is in radians where 2pi = 360°. One radian is 57.2958° so .448 is 25.66851°.

The control naming is inconsistent. Sometimes "Switch A/B" toggles between A and B on each press context and sometimes it does A on press context and B on release context. I liked it when they wrote press-release as A (B). The throttle is of the "A/B means A (B)" type which works well for Thrustmaster Warthog and similar devices that have a button in off and released when moving to idle. Looking in the input lua observe: value_down = 1.0, value_up = 1.0, name = _('Power Lever (Left) - OFF/IDLE'), --a switch that does something on down and up contexts value_down = 1.0, name = _('VHF Squelch Switch - ON/OFF'), --a switch that does a toggle only on down contexts And you see that both have a something/something format to the label. It's really helpful to be able to look in \Mods\aircraft\AH-64D\Input\AH-64D_PLT\joystick\default.lua for example and read the text to see what the command actually does when diagnosing issues. And of course if you really need to you can write in your own that act how you want them to.

I show with just the tip rails at 13,3 klbs the F-5E-1 with J85-GE-21 on JP-4 fuel can do on standard day about M1.4 at 25 kft pressure altitude. Your speed is about the MIL thrust maximum. Weight and drag can have a significant impact so I dunno.

Some people like to see the switches animate when they press them on their $1000 controllers. I mean the switch will still go into DVO position in the real aircraft so mimicking that function physically is just good simulation (including simulating an operator putting a switch in an undesirable state). Maybe some day they'll make an AH-64A (or some future version that re-utilized those functions) and the assets are already made. Keeping duplicate switches (e.g. missile advance) can have value even if for organizational purposes or to model damaged states. As for LHG and RHG enter, I think I found them acting different (selecting TSD points with cursor) but it might have been a controls issue on my end. I'll keep a lookout for it.

Your axis may not be outputting the full 0-100% range. Looking at the axis tune can let you see what the axis output values are and the tuning itself with deadzones and saturations can usually ensure complete coverage. The idle-off transition is limited to a very small window around 0% axis.

Is missile advance device agnostic (collective, RHG)? I noticed there actually isn't a separate control for the RHG. I found out that LHG cursor controller enter and RHG enter aren't the same logic which I want to know more about. Doesn't look like WAS-ATA, CAGE, HDD have any function in this variant. You think VIDEO RCD might have a use later?

I'm remaking the reWASD profile in Joystick Gremlin/vJoy (and alternate windows controller so LT and RT are on separate axes) which should make it possible to bind button presses similar to how the Warthog trigger works. A major benefit is that I'll be able to use 64 DX buttons output so I won't be doing keystroke emulation at all. The downside is I won't have rumble support and haven't even begun to figure out double taps (although long presses seem to be well within vJoy's capability).

Nope, the issue is still there. In real life the calibration saves the angle of calibration whatever it is. When the calibration is only 500' ahead of you (e.g. on the ground) the baseline distance between the pod and missile seeker and the resulting calibration is "cross-eyed" and won't work right in flight. The DCS calibration is magically correcting the sight line calibrations be absolutely parallel (harmonize at infinity) regardless of how far away the actual calibration target is. Right now when TGP is looking ahead the missile seeker is looking at an angle 0.0000° different. But because the missile is displaced say 5' to the right (for station 7) or 12' to the left (for station 3) relative to the pod the missiles will be looking at a point right or left of the target by that many feet. But at 30,000' distance a 5' to the side is an angle of 0.0095°, essentially zero, and to our human eye it looks exactly the same direction. But take that same perfect infinity calibration against a tank parked on the runway 500' away and suddenly that's an angle of 0.57° which is very noticeably off. If the pilot makes a calibration at 500' then it should work for a target 500' away and be wrong at 30,000'. If the pilot makes the calibration at 30,000' then it should look wrong at 500'.

The view limits are set in a different file. I don't know if they are IC protected or not.

Quick question. How else is RHG "ENTER" button different from LHG "Cursor Controller/Enter" button? I was struggling to use the TEDAC and I figured out that the RHG enter button is not an exact duplicate of the LHG cursor-enter button. In most things they are interchangeable but not all as I found out.

I'm talking about the TEDAC left trigger. It's an Xbox controller mapped with the LT axis broken into zones I, II, III. Zone I is blank, zone II is keyboard something, zone III is keyboard something-else. So the zone III to zone II transition is being seen as releasing second detent and pressing first detent. When I bind it up to Warthog trigger 1 and trigger 2 (buttons 1, 1+6 respectively) everything works fine. I tried to set zone I as 'A' and zone II as 'A+B' to keep that same scheme. But it looks like there is a gap between the zones so the 'A' is being interrupted and reapplied.

Yes but when I move my controller through its range it pushes the first detent on half action, second detent on full action, and first detent when releasing.

The issue is if I have 'A' and 'B' to first and second detent then when I advance the trigger to 'B' then release back to 'A' I get a distinct first detent action.

What does the first stage trigger do in reality? I'm also trying to figure out how not to actuate the first stage LRFD trigger when releasing the second stage.

What is the indication that alignment is satisfactory or complete? I've just been using when the TSD chart layer is visible but that seems unscientific.

The actual solution, at least the one which will work at the moment to the desired end state, is to unmount the tanks from the station, fuel internal, and then remount the tanks as they come in their full state. This achieves what the user wants just not in an exact recreation of the process that would happen in reality. A system which replicates how this is done in reality could be tricky. Some aircraft have a centralized fueling port that can fill externals using the main system and some need the tanks themselves topped off directly. The F-16 I believe is the former type so possibly the best way is some sort of checkbox to continue filling to all external capacity. Otherwise having the ability to modify stores at the stations directly without re-initializing them would dovetail well into the upcoming armament dialog which would be effectively the same thing without having a special case solution.

SRS causes the cold start AH-64 (cold start) to have its master volume knob graphically initialize to the maximum value while the logical value is minimum. This desync is removed when the knob is moved by the user.

Conflict with mods it appears. Playing 20 questions with it now to narrow down which. EDIT: It's SRS