Art-J

@A.F. Couldn't investigate your tracks closer without my gear plugged in, but at first glance there seems to be nothing in-your-face-obviously-wrong in breakers and switches setup in both of them. That's pretty strange indeed. I flew 109 only once in 2.9.6, but I don't remember if it was before or after hotfix. Prop worked allright, however, cold started and all... For now, why not trying the standard DCS troubleshooting drill: a) Disabling / temporary removal of all custom mods incl. the ones in Saved Games ('cause repair and cleanup doesn't affect them). Even mods which are supposedly unrelated to 109; b) Run slow repair and cleanup procedure; c) If repair doesn't help, (even though it should in theory) - reinstall the 109. Let's see what happens then. P.S. - Last minute thought - have you tried testing the prop mechanism before engine startup, as the procedure in the module manual suggests? I don't think it should matter at all, but who knows... I do it as a habit and as I said, never had prop problems so far.

Might as well check if "game flight mode" (or whatever it's called nowadays) is turned on by accident. In simulation flight mode prop automation should work the same in cold- and hot-started missions.

I don't know, but it seems to be hardcoded. Otherwise all the guys who have complained about too radical gamma changes when looking around or zooming would've figured how to tweak or disable it by now.

Mind you, It already does happen (and there have been many complaints about it), although not by THAT much. I don't think analog adjustment would be easy thing to implement, but digital one in 0.1 steps, as in options screen now, that's more realistic wish.

It's a known issue with the new launcher. Hopefully will be fixed in upcoming patch, but for the time being you might consider disabling the launcher if you don't really need it.

It's one of known issues of the new launcher and how it deals with authentication. If all your modules work fine, you can ignore it for now and wait for official fix that will come eventually.

It's a known issue with the new launcher (and not the only option that gets reset whenever you start it). The only "fix" available for now is disabling the laucher and starting the game "the old way".

Since DCS allows binding multiple separate physical axes or devices to a single virtual axis "out of the box", wouldn't it be more simple to just bind brake lever axis to both toe brakes without any extra .lua edits? True, in order to make it work, one would still need to press each of them together with rudder indeed, but we tend to do it anyway, so it's not much different from flying US and German warbirds.

^ "Gameplay" options screen, bottom of the middle column.

Most likely indeed.

For all intents and purposes they are seen by Windows as separate programs on your computer, so unless you have your own specific reason to keep both (for example updating one to the latest version while leaving the other older just in case you don't like the patch), deleting one shouldn't cause any issues with the other.

Cazub, thanks for the track. Couldn't play it as it uses Afghanistan map which I don't own, so I tried to replicate the issue on Caucasus map. I never used "takeoff from ground" option, so I thought maybe that one was causing some issues and that's why I never experienced such a problem myself. That still doesn't seem to be that case, however. During my quick test with cold start from ground at Batumi, using autostart sequence and without any controllers plugged in (just throttling up and down a little using mouse) - with or without lock enabled, tailwheel behaved normally. That brings other questions then: a) does it happen on other maps than Afghanistan? b) does it happen if you test without your controllers plugged in?

Can you post a replay track where you encounter an issue? This will help to fully understand what the issue actually is, 'cause I don't think I've ever encountered it in 109. Unlocked tailwheel not reacting to diff braking that is (If I understand somewhat muddy description correctly). Does it happen in one of campaigns (Jagdflieger one, as in OP's case), default missions or your own ones? Single or multiplayer?

Bowie, all of us have been using 2.9.6 for two weeks now and you're the only guy reporting such frequent failure issues, so it's safe to say it's not as common as you think. I've been flying Mustang, Thunderbolt, Mossie and Anton, in stock and custom missions, with random failure option enabled and haven't experienced a single one so far, which leads me to continue to believe that the option hasn't been fully implemented in all aircraft for years. But I digress... I'm not saying there's certainly no bug here. Clearly something happens in your DCS install. There must be something in your combination of mission, airfame and 2.9.6 that exacerbates the problem, but without a replay track, nobody's going to search for a needle in a haystack. We, fellow operators are more than willing to help narrow down the issue, but if you're saying "please advise" in one line and pretty much tell us to F off when 1st troubleshooting advice is given, then, well, good luck. Rules here are simple: a) If you post a track, ED might take a look at the issue, investigate and reply. The chance is small, but at keast it's there allright; b) If you don't post a track, there's an absolute, 100% guarantee that nobody's going to bother, neither devs, nor beta testers, nor users, because there is no starting point to investigate. You being a "paying customer" is irrelevant. Well, choice is yours. You do you.

^ What Draconus said. Keep in mind, however, ED stores only a handful of older builds on their servers, dating back a few months at best. If you want to go aaaaall the way back to 2.8.xx, it most likely won't be available anymore. You can try, though.

If you're not using Steam version but standalone one, you can rervert to one of previous versions, following guide posted here: Note, second post in that linked thread contains a table with previous version numbers you will need:

Launcher showing more modules available for download than you really need is a confimed 2.9.6 bug. Ignore them. Afghanistan map showing low-detail terrain everywhere if you got the free trial of the whole map instead of installing SW version first is also a confirmed bug, although it affects free trial users only (similar bug to free trial of Normandy 2). I guess It will all be sorted eventually, but for now, to get around these bugs, you're indeed supposed to trial SW version of the map. That being said, after yesterday's hotfix some users who actually bought the map now also report authorization issues, so unfortunately you have to use errr.... trial and error method to see what works for you.

Awwwww..... built a mission on Guam with parameters as above, but the hillarious megamoon was not there. Shucks . Only the somewhat enlarged standard one. There must be something else in "Paradise Lost" pumping it up THAT much. Oh well, thanks anyway!

1 screen attached below for general fisheye overview. I agree windscreen and canopy reflections perhaps might have been made stronger (?), although I haven't flown Anton in a while before 2.9.6 to remember how they were before. They do become a problem now when the sun is low and you've got it behind your back. In default cold start mission on Channel map I could barely see the runway during landing approach as the whole windscreen became only partially transparent with a thick relflection plastered all over it. Can't imagine spotting any targets in similar conditions.

What's date and time set in that mission? I'd love to experience the death star myself but don't own the campaign .

6 "ghost" Items shown in the new launcher are a confirmed bug. Ignore the launcher and check if you can install the map the old way - via Module Manager.

I've read in the other thread that it happens if you still run DCS in single-threaded mode.

Offline mode attempts throwing out code 500 error is another bug introduced in 2.9.6. Stay online then until it gets fixed.

Sounds a bit like traditional "comms" vs "push to talk" menu problem that new DCS players stumble upon on regular basis. If realistic comms is used, the former command ("\" key by default) works only on the ground/deck. After takeoff the latter must be used ("Alt + \" by default I think?). Mind you, it's called different in various airplanes, I don't own F-18 so don't know if its called PTT in that one. Of course, channels, freqs and whatnot must also be set correctly beforehand.

With them having a solid amount of experience in racing gear but no experience whatsoever in flight gear, I think time of announcement was as good as any. Early adopters would deal with the same initial issues anyway. But that's just a part of adopter adventure.