Raspberry

This is all based on my observation, so someone please correct me of I'm wrong, but: As far as I can tell auto-reverse just automatically applies MAX REV once you touch down, regardless of your IRL throttle position. It may require weight on the nose gear, but I haven't actually tested that. The reverse detent setting controls the point in your throttle axis where the throttle transitions from idle to reverse (so if you have a throttle with a physical reverser detent, you can make sure the in-game throttle matches it). IE, if it's set to 0.2, the in-game throttle would transition into the reverse range when your IRL throttle is at 20%. If it's set to 0, your in-game throttle won't go below ground idle. Disabling ground range prevents the in-game throttle from going below flight idle, regardless of whether you're in the air or on the ground. Vice-versa for enabling it, so if it's enabled, you can go into reverse thrust in-flight.

I ran into this issue last night too, but only once. Most of my flights were fine, but one time the parking brake just wouldn't release, whether the brakes were held or not. After 5 minutes of trying various sequences of wheel brakes & parking brake handle movements to get them released, they eventually did, but I didn't do anything the time they eventually released that I hadn't already tried multiple times in the preceding 5 minutes.

I've settled on just setting the reverser detent to 0 and using auto-reverse for now, but an Elite Dangerous type option to toggle the throttles between applying forward thrust or reverse thrust would be a significant quality of life option for anyone whose throttle doesn't have a physical detent (or who have one, but don't want to have to install/uninstall it when switching between modules).

I can't seem to get the plugin to remember my install directory. Clicking Update after entering the correct directory populates the lookup list with my modules, and I can get what I need for whatever button I'm working on, but then it reverts back to the default directory the next time I open the lookup.

I just found this thread after experiencing the same thing flying online last night. Unsure what the actual weather settings were, but the METAR in the briefing said scattered clouds at 900', and those clouds were full of rain, so definitely CASE III conditions. If the carrier happened to be in one of those clouds, you just couldn't see it at all, but on the Inbound call it would still report visibility 10SM, CASE I expected. At one point I flew right past it at 800' trying to attempt a recovery despite the conditions, and still couldn't see it. Ended up having to just loiter until it got to a patch of clear sky large enough to fly an approach in.

Just wanted to take a second to thank you for this. I've been using this mission for a while now to get a couple of friends into DCS, as they slowly free trial aircraft two weeks at a time, and it's been absolutely perfect for it.