Luzifer

Of course it wouldn't have to be modelled that precisely – I don't think many people would complain if the vapor is a bit too strong here and not quite enough there. DCS already knows fog, clouds and other atmospheric effects. It would be enough to just massage up that data to get a ballpark figure for the required pressure drop for condensation at the plane's position. Well, it sounds easy, at least…

Were the old wingtip trails dependent on environmental conditions at all? If not, that's what I would want to see, i.e. no wingtip trails even in hard turns in bone dry air, and wingtip trails (and over the wing vapor clouds please) even in level flight in humid conditions, e.g. under overcast raining clouds.

This is a very common beginner misconception. In a stable flight condition you don't adjust speed with your throttle, you adjust speed with your pitch and associated trim. With throttles you adjust the rate of descent. That isn't particular to landing, it goes for in-flight trim too. Once you have your plane in landing configuration on final you set the speed with pitch trim to the desired approach speed (as directed by AOA indicator for example) and then use throttles to adjust the descent angle so that the plane will come down at the start of the runway. Unless you are throttling up or down a lot, your speed will stay the same. (If you do throttle up or down by a large amount, your speed will eventually be the same again. It's just that inertia will cause some oscillations around the set speed. You would handle the stick and adjust pitch to prevent oscillations, but not change trim if you want to end up at the same speed.) I don't know what you're trying to get at here. You have to flare, otherwise it's going to be a hard landing. Of course, you mustn't pull the nose up until the tail strikes the runway. That's what these limits are about. Um, if your velocity vector is above the horizon you're gaining altitude which isn't very conducive to landing. I think you mean the nose. Where your TVV is pointed relative to your nose is related only through many variables.

The ejection handles do not react to mouse clicks, you need to use the keys (or button, if you assign it to the joystick somewhere) three times.

Die Lizenzen sind sprach- und versionsübergreifend. Egal wo der Schlüssel gekauft wurde, kann man den auch für das DCS World Modul verwenden (außer es ist eine BS2 Upgrade Lizenz, dann muss auch BS1 gekauft und installiert sein).

Also, you can't expect damages as a rule. Modern electrical systems aren't as dirty anymore and modern electronics are better protected against spikes and surges (not just planes, just look at the protection that is required for suppliers of electronic devices in cars). Quite likely pilots are still being taught to turn off the avionics prior to engine start Just In Case™ and so that they intuitively do it when they find themselves in that vintage Cessna or something.

It sure is odd. For me, I think it happened after some update. I read around here that invisible cockpit means that the module isn't activated, but I had no idea why it wouldn't be. Reactivating fixed it for me, as far as I remember.

In the Windows start menu maybe, otherwise it appears by holding down shift while double clicking the multiplayer shortcut. The FAQ is at http://www.digitalcombatsimulator.com/en/faq/activate/ . You need to deactivate your license key then activate it again.

I had that happen, I think unbinding the license (for DCS:A-10C) in the license manager and then entering the license number again fixed it for me.

No, you simply change the assignment in DCS options. If you have the options for key assignments open and can't find the right line (there's lots...) just press the button and it will jump to the line that this button is currently assigned to.

It's a F2P title with paid DLC. Nothing out of the ordinary. That might be more difficult. I don't think there would be technical difficulties with including DCS World in Steam (apart from FC3). It's more that ED doesn't seem motivated at all to do that. They appear to be beefing up DCS World to be its own mini sale and distribution platform so that they don't have to share profits. Understandable in their position, but a bit of a shame too. A Steam sale is where I learned about DCS:A-10C since I wasn't following the combat flight sim world too closely at the time (ended up buying it in a store since that was still cheaper than the sale, but anyway...).

I have checked it again and found that I see no problem in the Windows 7 Game Controllers settings, just in DCS. I don't remember why I thought that. However I think I remember reading that users of Microsoft FS also have these issues...

None that I know of (other than the workaround of slightly stepping on the pedals to get the brake unstuck). But I haven't been looking hard either. I don't even know if the pedals use a Saitek driver or the standard Windows one and who to blame. All I know is that no matter how hard I tried to trigger the problem, they work flawlessly in Linux, so the hardware is fine and Windows software is to blame.

As mentioned, it isn't the .exe name but the name the client software registers uses when registering itself with TrackIR. And that is Black Shark for DCS:World for one reason or another. Still you won't get different profiles for different modules because they are all DCS:World (so it's always the Black Shark profile). Apart from the non-obvious choice of Black Shark for the DCS:World profile name there is quite likely no bug to be found here.

Oh, that is too bad.:( I don't understand how it can be so hardcoded that it can't be changed though. Even if they are rendering them as lines there is a way (at least in OpenGL) to set their width, including to less than 1.0 if they're antialiased. They are really an eyesore, so it's a bit ironic that they are so proudly highlighted as a scenery feature in the DCSW overview video. Especially when the view then pans over a spot where two overland lines cross at the same height so that the wires literally cross. :lol:

I have that problem with the Saitek combat pedals too. It does show in Windows, not just in DCS. It happens when you release the brakes fast. Wiggling a bit makes it update again. It is some sort of weird Windows driver problem.

I would love to see the power lines look more realistic. Everytime I see them now, I can't help being amazed how ridiculously thick the wires are. If there's a bunch of them close together, you could almost hide a helicopter behind them! They really should be rendered with a much smaller width, so that at a distance they would blend with and only darken the background. After all, this is what they look like in real life up close: Photo 1, Photo 2. It would be really nice to see this fixed. As it is right now, the wires are one of the most unrealistic looking features of the scenery.