Mar

I apologize for implying that you were trolling The Falcon. You write English so well but with such subtle differences. It got me confused! Your last few posts helped me understand what you are saying better, thank you. It seems we agree after all!

Think harder about my question, "What is wind?" From the aircraft's perspective, there is no such thing. From the aircraft's perspective, the only thing that is "felt" is wind "gusts." This is because a gust or burst of wind does not last long enough for inertia to be overcome. Let me try this example: Imagine you are drilling through the earth and suddenly the earth's direction of rotation changes. You would feel the change up until your inertia catches up with the new direction, and then it would be like nothing happened. The earth's rotation is a constant "wind", yet you would continue drilling in the same direction relative to the earth. Here's another one: Imagine a floating island with a car on top. The island floats towards the East, and the car drives towards the North. To the driver, he is driving North, but actually he is driving North-East.

This looks like quality trolling to me now which really has absolutely no place in the bugs section. However, I will make one more post that I hope will help anyone who is genuinely interested in learning how planes fly. Horizontal wind has nothing to do with climb rate. The only things that can affect climb rate are drag, thrust, gravity, and vertical wind (updraft/downdraft). In the example given by bbrz, the reason the aircraft would be lower over the obstacle in a tailwind condition is because it has less time to climb before reaching the obstacle due to higher ground speed which is the only thing the wind is affecting. The climb rate is exactly the same. Things going from side to side do not affect things up and down. And remember, the only things that affect indicated airspeed are drag, thrust, and air density. Wind cannot change neither drag nor thrust, and we're not talking about changing air density. As wind hits the aircraft from behind it is met with the very same opposing force as static air is met with, and since drag does not change the aircraft is propelled at the very same indicated airspeed, only ground speed has changed.

So "I'm wrong", and, quite separately, things going from side to side affect things up and down. Ok. Good luck.

The Falcon, imagine for a moment that there is no earth or even any other aircraft, there is only air. Now tell me, what is wind?

It's under "PC Hardware and Related Software". Here you go: https://forums.eagle.ru/forumdisplay.php?f=144

Don't forget to mention that you switch to it by setting the CNI knob (near the IFF knob, closer to the throttle) too in the backup (left) position. This also sets the IFF to backup controls just below the CNI knob.

I managed to put together a temporary workaround after four hours of screwing with it. Using AutoHotkey, I can translate Lcontrol+Lshift+Lalt S to Rctrl+Rshift+Ralt S (this does work in the game), and so on, with this script: edit: better version ; Lctrl+Lshift+Lalt S <^<+<!s:: Send {blind}{lctrl up}{lshift up}{lalt up}{rctrl down}{rshift down}{ralt down}{s down} KeyWait s Send {s up}{rctrl up}{rshift up}{ralt up} if (getkeystate("lctrl","P")) { Send {lctrl down} } if (getkeystate("lshift","P")) { Send {lshift down} } if (getkeystate("lalt","P")) { Send {lalt down} } return ; Lctrl+Lshift X <^<+x:: Send {blind}{lctrl up}{lshift up}{rctrl down}{rshift down}{x down} KeyWait x Send {x up} Send {rctrl up}{rshift up} if (getkeystate("lctrl","P")) { Send {lctrl down} } if (getkeystate("lshift","P")) { Send {lshift down} } return ; Lctrl+Lshift R <^<+r:: Send {blind}{lctrl up}{lshift up}{rctrl down}{rshift down}{r down} KeyWait r Send {r up}{rctrl up}{rshift up} if (getkeystate("lctrl","P")) { Send {lctrl down} } if (getkeystate("lshift","P")) { Send {lshift down} } returnBut I still have yet to hear whether or not this problem only affects me.

Did not solve this problem. :( Thanks tho.

You're right, I missed the part where you said it works in 2D but not VR. Deleting input folder probably won't help, sorry about that. Sound like ED broke something again, big surprise.

Can anyone just quickly try binding these to something to see if they work for you?

You're in game avionics mode. The F-16 does not have controls for game avionics mode (F-16C_50_easy) yet. Go to Options > Misc > under Overlays > uncheck Game Avionics Mode.

Try backing up and deleting your input folder (%userprofile%\Saved Games\DCS.openbeta (or whichever)\Config\Input), and then rebind and test those controls. If it works after that, something about those controls changed with the update (the names, codes, whatever) that won't match up with your saved configs. In that case it would be a safe bet to redo your entire control set the way you wanted it from scratch instead of restoring the backup (in case more stuff changed).

All of them. Like I said, I don't have anything else running that would intercept keys. These combos do work in other games I play. In the controls menu in DCS, pressing these combos will jump to what they're assigned to. But they do nothing in the game. Rebinding is not an option, I have too much else bound already.

I have found (edit:) five key combinations that are ignored by the game. Lctrl+Lshift X Lctrl+Lshift R Lctrl+Lshift+Lalt S Lwin X Lwin G do not work in my DCS open beta. I don't have any other programs running that would intercept those combos. The exception is windows itself which uses the Lwin combos, but I'd have thought DCS would take precedence. Can anyone else use these? Am I missing something?