FalcoGer

I installed DCS on a 256GB M.2 SSD, but after buying 2 additional maps, the space quickly became too small. I then made a directory junction As admin: New-Item -ItemType Junction -Path "F:\Eagle Dynamics\DCS World\_downloads" -Value "C:\Games\DCS_Links\_downloads" and also one for /mods/terrains/ I tried installing Syria and Siani, and the installer reports that there is insufficient size on F:, however there is sufficient size with the directory junction in place. Installing syria, then siani separately works just fine. However, during any update after that I have to uninstall and reinstall them one by one, which is quite annoying. It would be really nice if the installer could detect if the files are installed on another drive and check the correct size requirements for each drive used.

Don't have it. Can't test and don't have the files for the input stuffs. It's modular enough. Feel free to create a pull request.

If neither pilot can get to the power levers, why would they be able to get to the chop button, which is much smaller and also guarded? Wouldn't that be even harder to action?

No. the new line can be placed anywhere in the exports lua file.

Did you edit/create the exports script and placed the lua file into the exports folder as well?

You are right. It's not useful to have them both be the same. But it can't be separated because I can't figure out which one is currently selected because it's a toggle and I can't access the display graphics or DCS's memory in any (legal) way.

This is labeled fixed. But just yesterday george as pilot was reacting to VRS by just raising the collective until torque was 160% at which point I had to take over myself.

I wasn't talking about taking fire, but having an engine fire. Identify affected engine Throttle affected engine: off Affected engine fire button: push Fire extinguisher primary: push consider dropping external stores if engine fire persists, discharge secondary fire bottle land as soon as possible

I'll look into that. That is a bug.

The project gets build by automated github actions. I doubt their toolchain is compromised. I didn't build the executables that you are getting myself. Other than that, the source code is available. While I can not 100% vouch for there to be no exploits possible that could lead to malicious behavior, I can guarantee you that no malicious behavior is intended. The only difference between 0.6.10 and 0.6.11 is some text changes for the AH64 point ident descriptions and the version number. All of this is well documented in the github history. You can and should always upload suspicious programs to virustotal. The program does make a web request (to check for updates), which may lead to some false positives or weak results (like 'suspicious') for some obscure virus scanner vendors. Here is the analysis of v0.6.11 on virustotal. One or two positives are not something I worry about, especially from vendors I never heard of anywhere else, especially for unsigned executables.

You can already do that. You just have to enter the coordinates manually.

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