FalcoGer

I'll think of something. Might be a while to get implemented though.

You're not on the latest version. Use the main form's settings, then check for updates.

What do you mean? Tuning presets and setting frequencies to the presets are two different things. To set the frequency, you select a preset in the first tab, then check the checkboxes down below for any radio that you want to put a frequency in for that preset, and enter the frequency you want for that radio. That is by design, because you can't have the same name twice. It's also for a quicker lookup from the CDU. There is a M in the front because a waypoint name can't start with a number. I thought the A10 doesn't have space on the CDU. Maybe I'm blind. Edit: Look like I'm blind.

That would be nice. But it's impossible. When you add a new point to the AH64, you don't get to pick where it goes. It always goes into the first available slot. The only way to achieve this would be to fill out all 50 points and then using edit. But then you can't change the ident and it would really clutter up the list.

I wish there were some kind of indicator of which modifiers are active, especially for those "Switch" modifiers that toggle whenever you press the button. Some people might use a game pad, especially for non-flying roles (CA, Gunner, WSO, etc), and put a switch modifier on it. Then they have to mentally keep track of whether that modifier is active or not. It would be neat if there could be a tiny, repositionable text somewhere that shows up whenever a modifier is active, say in the corner of the screen. Maybe the user could choose which modifiers are displayed or not, and where they are displayed on the screen.

SCAS goes crazy if you do large stick movements. Do small, smooth corrections and trim. Alternatively hold down trim while doing those corrections. That's just the way it is. It seems a little excessive at times, but I have no real world experience, so I can't say. They said SCAS is still WIP. I also found that altitude hold seems to slip away after a few minutes and it holds better if you just leave it off. If you keep the FPM stable and aren't slipping, you can reasonably keep flying the same direction with attitude hold. Personally I don't mind too much giving a millimeter of stick input every 30 seconds and re-trimming without attitude hold, i really only use it for hovering. I can't speak about the hind, but the KA50 was designed for a single pilot, including a route autopilot. If you have a decently competent slave CPG (aka not george), then all you really need to worry about is flying and planning (with your CPG), which is fine. Let him handle all the targeting, radio stuff and navigation. If he's not shooting stuff he's going to be bored anyway.

I tried switching to external ground power before repairs. It still got broken. Maybe because repair puts it in the power off/pinned state.

When in the mission editor, you can click the coordinate format in the bottom left to change the format displayed. When doing that however, this changes the "Coordinate Display" option in the Miscellaneous options. To reproduce: Go to Options Go to Misc. Set "Coordinate Display" to "MGRS GRID" Click OK Open mission editor Load any mission or make a new one In the bottom left, click "MGRS" until it says "CCS" Close mission editor, if prompted, do not save. Open Options Go to Misc. Expected result: "Coordinate Display" is still "MGRS GRID" Actual result: "Coordinate Display" is now "Metric", when now flying any mission, it will default to the (outside of the ME useless) game coordinates system and needs to be changed manually every time a mission is loaded, or be set again in the options.

Thank you. I fixed my mistake. It seems I have made some errors elsewhere, too, that now need fixing.

@Raptor9 Should the radar elevation indicator be updated when used in AUTO mode? because it doesn't for me, no matter what altitude I'm flying at. Also what does AUTO elevation do when the radar altimeter is not available, for example when damaged, turned off or when flying too high?

What's the point of having datalink members without the TEAM or PRI option selected? PRI allows receiving and transmitting of reports and single points on the TSD page. TEAM allows receiving and transmitting of mission data, such as whole point files, routes, laser codes, text, etc. So what's the point in having net members that are neither? You can't send them anything. I can understand having someone as primary, but not in team. And there might even be some scenarios where you want someone in team but not primary, although I can't imagine one. But neither really does seem pointless.

IDK. I often get "XMIT NAK", but the other end receives, even if they're the only ones in my NET list. It seems fairly consistent whether you get NAK or no message, but I haven't found out what causes it to go either way. Whenever I tried reproducing it, it behaves as expected.

Had it happen again. This time I was in the front seat and got engine autopage because "rotor rpm low". back seat did not get rotor rpm warning. Then I got FMC Disengaged in the front, presumably because the CPG client thought the back seat was on the engine page while the back seat was not and their client just send button presses instead of aircraft states.

When pressing CAQ the TSD freeze option is automatically selected. This is normal. When CAQ is done, the TSD unfreezes. However before the last few updates, when using PAN, which also freezes the TSD and then using CAQ, the display would stay at the panned to position. Now the display FRZ is disabled when CAQ is done. To reproduce On TSD press PAN PAN TSD to a cursor selectable item (for example a TG point) Press CAQ Use the cursor to select a point Expected result: When FRZ is active before CAQ is selected (for example by using PAN or FRZ), then finishing CAQ will not reset the FRZ option. Actual result: FRZ is always reset when finishing CAQ. I'm not sure of that is correct, but I find it annoying and it was different before, so maybe it got broken? When I use this feature, I typically zoom in on the TSD on a cluster of units and then use CAQ to engage each one in turn. Having to PAN over to that area again and again makes this process much more time consuming, even when using the LAST PAN option. Of note: When using "Point" or "Route/DIR" to select a point on the TSD with the cursor, the display does not get unfrozen. CAQ_unfreezes.trk

Made a thing to help putting stuff that is ordinarily in the DTC into the aircraft automatically. You can save and load JSON files, too. It did do points before, but now it also does some AH64 specific things. The stuff it does includes: XPNDR settings Comm preset data (C/S, Unit Name, Primary Selection, Frequencies for all radios) Preset Net members Modem settings (Protocol, retries count, can't do auto reply because it's a toggle in cockpit) Tuned presets ASE Chaff program & Autopage setting Weapon settings (MSL Channels, gun burst count, rocket quantity) Laser codes

I use the warthog hotas, too. I don't need a modifier at all. I have a modifier on EAC, but that's to switch to pilot controls. Everything you need when not flying can be done without a modifier. On the stick: FCR mode: Trim Hat FCR zoom: DMS WAS/Target store: TMS (store is down) Slave: Masermode swich Laser 2nd detent: paddle LMC: CMS depress TADS FOV: CMS Cued search: Pickle Trigger: Trigger zoom: pinkie On the throttle: Sight select: coolie hat FCR Single/continuous: air brake aft/fwd Sight TV/FLIR: boat switch fwd/aft IAT: China hat fwd/aft LST: A/P mode select (using _OFF bindings for LST off) TDC slew: microstick Cursor enter: microstick depress NVS select: pinkie switch polarity switch: pinkie button

I see. Yes, it seems the MGRS coordinates are off by around 220m. It seems there is a bug with converting coordinates from L/L to MGRS in the AH64. The correct coordinates for N 42° 10.7600' E 042° 29.7200' are 38T KM 9315 7272 (38T KM 93146 72725) With L/L decimal minutes and 2 digit precision there should be a maximum of ~16m difference, and MGRS with 4 digits groups is 10m accurate. There shouldn't be a discrepancy of ~200m. And if it were INU drift, both numbers should be off, not just MGRS. And again 200m is way too much for a modern laser ring gyro system and military 1m accurate GPS updates.

@NeedzWD40 Just checked. 38 T KM 93141 72729 = N 42° 10.7623' E 042° 29.7161', using a non DCS system. The coordinates are correct and not "off". Powered by the coordinatesharp library, using the ellipsoid earth model for added precision.

the top left corner of the map displays your mouse coordinates. the coordinates of the selected element pop up in the bottom left corner. If you're talking about the MGRS being only groups of 4 digits, that is normal. The AH64 uses 10m accurate grid coordinates, not 1m accurate coordinates like displayed on the map. you can just truncate the last digit off each of the group of 5 to get the 4 digit number used in the AH64. There could also be some drift in the INU. But the easting is perfectly correct, the northing 49336 on the map is off by 200m from what the aircraft displays (4913[0]). My bet is that the mouse position is not exact. Use the window in the bottom left of the map screen to get accurate coordinates for selected objects on the F10 map.

When in a multiplayer scenario, and you request control as CPG, and you find yourself in a situation where the pilot can't accept or deny, the blue box with the text that you have requested controls does not go away. For example the aircraft gets destroyed. To make it go away, you have to request controls in the new aircraft and then the pilot has to accept or deny it. To reproduce PLT and CP/G join aircraft (set to Pilot responsible or Always ask) CP/G requests controls PLT does not accept or deny Die (Apply mountain or ocean to face at high speeds for example) PLT uses Briefing screen (LAlt + B), and select Fly to get a new aircraft CP/G will still have the "Requesting controls" message forever until he requests controls again and is denied or permitted by the pilot.

In the mission editor there is an option to determine who can take control of the aircraft at which time. The options are: Pilot responsible, which is the default, where the pilot can take control without asking, but the CPG needs to ask and the pilot has to click the accept button CPG responsible, which is the reverse Equally responsible, where either can just take control without the pop up box Always ask, where the pop up box always appears for both This option is a user preference and has nothing to do with the mission or the aircraft itself, and thus should not be in the mission editor. I find it frustrating that whenever the CPG needs to take controls (for example in a training scenario, or when the pilot is not good enough to salvage a situation like a missing tail boom or broken tail rotor), the pilot, currently using his hands in a difficult situation has to grab his mouse and click the accept button. Mission makers have enough to do already, and I have not yet seen a mission where they have set anything but the (IMO poor) default. This pop up box is especially annoying in VR, because it might not even be on screen. Because this is a user preference, and not an aircraft specific thing, I wish for it to be moved to the special options, and removed from the ME. In a multicrew scenario, whoever has the pilot slot, that person's option then should apply. For example the pilot has selected Pilot responsibility, and CPG has selected Always Ask. Then the Pilot responsibility option would be used. Alternatively each crewmember can have their own option that apply only to them, while the other crewmember has their own option as well, or two options: Require confirmation before other crewmember takes controls? No (default), Yes Or As PLT, require confirmation before CPG takes controls? No (default), Yes As CP/G, require confirmation before PLT takes controls? No (default), Yes For example the pilot has set it to ask, and CPG has set it to don't ask. Then when the CPG wants to take control from the pilot, the pop up pops up. When the pilot takes controls back, the pop up does not show up. You should have verbal communication anyhow, through DCS's new VoiP system, through SRS, or through any other voice communication software, or even just shouting across the room. Because of the fact that you are most likely communicating anyway, the default should be set to "equally responsible". Whatever options you want to put, just make it a per user setting, not a mission editor thing.

As for WP saving/loading, you might be interested in the tool I have made until ED creates their DTC implementation.

Missile types are restricted by your selected sight. TADS: Both are allowed HMD: Only SAL FCR: Only RF

@NightstalkerNOR I created a tool to help with configuring stuff like that.

The tree survived.