Art-J

A third command is missing from that description, which stops at weapon selection step. Now pressing the actual "Weapon Release" button should follow. Did you forget to write about it, or to use it? It's RAlt+Space by default.

We have TrackIR on ;). On a serious note, I don't know about salvo selector being bindable or not - never felt need for operating it with anything but mouse, but weapon release on joystick certainly works allright. What happens when you go to controls menu and press that 8 or 9 button of yours? It should automatically go to and highlight the "weapon release" row. If it doesn't, that means you haven't actually bound that command. Unless you're suffering form the old bug of D-25 not being able to read D-30 commands on first DCS mission load, but that's another issue altogether and I suppose you would've noticed none of your custom commands work anyway. Warthog HOTAS here, by the way, used without TARGET or any other external software.

^ It's always set to zero in cold start missions. So, @jfri, in all three variants of the -47 the procedure is the same: armament switch to guns & camera, then rotate gunsight rheostat clockwise.

Icing in DCS is simplified and based on altitude, not clouds. Also, carb icing in warbirds is not simulated, only pitot one (although there are currently reports investigated, about 109, 190 and Spit pitot heater switches working in reverse, or not working at all. Not sure if Mustang is affected).

In that case go to special options tab and double check if assists haven't got turned back on automatically - I've read that can happen sometimes after the game update. I just tried Instant takeoff missions for Mustang and Spit, in both game and simulation flight mode. With assist off the rudder certainly didn't move without my inputs, so the option seems to be working OK in the latest Open Beta and so it should on your PC as well.

I don't experience it in my own custom missions. Which ones did you notice that problem in? Keep in mind that mission parameters can override your preferred settings. For example both Fw-190s training missions used to have takeoff assist forced ON (I suspect they still do) even if you turned it OFF in special options.

It's a problem affecting both takeoff and landing. Difficult to get the front wheel smoothly off the ground (contrary to notes in real life flight manual), and difficult to keep it from slamming down at touchdown. Almost as if there was too much weight on it, or stabilators were not producing enough lift in these transitional phases. It's always been like that, however, since module release 9 years ago, and countless posts were written about it. No point in beating a dead horse. I don't expect it to be ever changed, but truth to be told it's not a critical problem either.

Got permanently removed in January 27 OB patch. At some point they were considering removing Flight Mode as well, 'cause to be honest, they don't develop it and support fully in all modules. It's still there for the time being, but be prepared to encounter unfixable problems with it.

I've got trims bound to keys, not switches, but the rudder one works as intended, and described in the manual: Key for rudder trim right -> wheel rotates CW -> tab goes left -> rudder goes right -> plane yaws right. Key for rudder trim left -> wheel rotates CCW -> tab goes right -> rudder goes left -> plane yaws left. That's how it should work if game flight mode is turned off. If it's on, the trims would be animated, but the plane would not react to them.

Control inputs shenanigans are caused by folder structure in the Saved Games, logbook doesn't interfere with these. You just have to make sure that you've got two config folders for both Mustangs present and that content in both is the same. You'll be fine then. Follow this thread for details:

1) Would be nice if quick mission generator remembered the last map selection and AI density selection used in previous DCS gaming session. That used to be the case in 1.2.xx era but changed to current annoying implementation somewhere along 1.5.xx for undisclosed reasons; 2) I also wouldn't mind getting back to P-51 spawning on the ground WITHOUT light rheostats cranked to 100%. It doesn't make any sense and wasn't like that before one of the updates a couple of years ago.

Yup, either PJ uses some wildly off-the-scale Reshade settings, or Spring season (not modded) in this video. Updated screens in the 1st post show how the Summer textures actually look like now. After a short test flight yesterday I like where this is going. Maybe the trees could be somewhat darker, as they were in N1944 edition of the mod, but given the tech limitations Barthek is facing, we already have a noticeable overall improvement.

Used to have DCS on a separate SSD drive years ago, but after running out of space I've got it now on the system one, 'cause it's the only one big enough. I'll probably switch to a more "PC-hygienic" solution suggested by BM above in the future, during the next overall PC upgrade. With that being said, referring to the original question, I've noticed no noticeable difference in performance whatsoever.

There goes my Friday evening... Can't wait to try it out, thanks!

P-47 and 109 feature a cockpit vibration effect once you get really deep into the knock territory. No idea if "realistic", but a useful visual clue no doubt (for these who don't check the temps on instruments often enough). They're the only modules that have it, though.

As far as I know, patent issue is no longer an issue, fortunately, but mainstream manufacturers are not really in hurry to start working on FFB stick designs again. We're all a minuscule market compared to racing sim enthusists after all. Some small-scale production, "boutique" solutions start popping up, though. VP Force Rhino comes to mind as an example.

There are some hints about making the system work in 109 forum, but I've never tested them: https://forum.dcs.world/topic/318770-homing-navigation-device/?do=getNewComment

I'm asking because if it's on, no trims in any DCS plane will work. They'll be animated, by they won't affect the airplane's flight physics. If you've got it off now, you can assign trims to anything you want - they'll work OK.

Can't do it in D30 "early" as it had three separate levers to release ordnance from hardpoints. Can do it in normal D30 and D40, however, by selecting all three hardpoints on relevant selection & arming panels below instrument one and then dropping all three bombs with a single button on top of the stick.

Well, "cheat" in a sense that IRL you have to ident and mark position yourself, while here the game magically does it for you. But that's a dead-horse argument, discussed on this forum ad nauseam. These who want to use it - use it, these who don't - don't.

By good old dead reckoning and being familair with the terrain - that's the hard way. There's a bit of a realism-cheat available, however. Once you bring the kneeboard page up with a map on it, you can make the game mark your current position on the map for you. Haven't used the function in years so I don't remember the deafult keyboard combo for it. Might have been Ctrl (left? right?) + down cursor, but you'll have to confirm it in the controls options.

It doesn't, neither do German fighters. I don't remember if it's been covered in one of these numerous threads you've started, but do you have game flight mode on by mistake?

Nah, it's still there allright, both on ED shop and Steam. Never owned it though, so I don't know how bad the situation is with the support. The question is - should the issue above be reported here or in NS430 forum section.

...or at least it should, but seems to be somewhat unreliable. @AngryViper.101 you might take a look at page two of this thread for possible workaround for the problem:

Not confusing really. Both maps are supposed to cover in high detail different areas with different airfields, as noted in the FAQ thread.