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?

Hmm, looks like you've got some stuff in your sig. I suppose none of that was the result of intensive academic research either...

At least zhukov032186 cherry picked something that could have helped him if it was true. As for you... I have no idea what you're trying to do.

I liked the part where you cherry picked a tiny tiny part of what he said because it was the only part that could help your agenda. But in case you actually didn't know, he was talking about how it would appear on a movie screen. "It's not gonna look right, it's not gonna be exciting, people aren't gonna understand what's going on." Kind of sounds familiar... Do you think RL pilots would train like that if they couldn't understand what was going on?

As somebody who came from WWII fighters, I feel your pain. These jets fly so fast, and have missiles that can (or are supposed to) be fired from farther than the eye can see, it's no wonder I had a hard time understanding wtf was going on. So, since the enemy is coming from so far away, you have way to much space to scan for him in. You need to narrow it down somehow. First (and always first), use the Mk. I Eyeball (look around with your eyes) to make sure he hasn't already snuck up on you. Second, check your sensors (radar, EO) in case they already found him. And finally, use your Situational Awareness (SA). Besides the Mk. I Eyeball, this is going to be your most important (and it will be your most difficult) tool to use. By being "Aware" (remembering what the briefing said about where the enemy will come from, paying attention to radio calls from friendly planes like AWACS (BULLSEYE helps here, more on that later), paying attention to where that bandit was last heading before you lost track of him, etc. etc.), you can build your internal picture of the "Situation" (where is everybody and what are they doing?). No matter how hard you think just spotting planes visually is, trying to keep your SA up will seem far, far worse. It will take time and patience to learn it. I would suggest training your use of the Mk. I Eyeball first. Don't start with a needle in a haystack, fly a mission (or make a mission if you want) where you can stick with at least one friendly plane without worrying about anything. Practice buzzing all over the friendly plane while keeping him in sight at all times. Then you should get started on SA. I know I put using sensors as the second step, but even those powerful tools can only scan a tiny fraction of our great blue playground. Give this a try: Fly around staring at your HSI (Horizontal Situation Indicator, has a compass on it and you use it a lot for navigation) getting used to the compass numbers. Then practice looking out in random directions and seeing if you can tell what bearing (compass direction from you) you're looking. This will help a lot with those radio calls I mentioned. When a bandit is close enough to you AWACS will give you BRAA (Bearing, Range, Altitude, Attitude (attitude is hot/cold, coming towards you/going away from you). Use your compass practice to quickly know which way to look. If he's really far use your sensors in that direction, adjusting for the called-out altitude at the called-out distance. If the bandits are farther from you, AWACS will give you their BULLSEYE location. BULLSEYE is a common reference point for all friendly planes. It can be anywhere on the map. Say you as the mission maker make BULLSEYE on top of your favorite city. If I tell you BULLSEYE 176 43 miles at angels(thousand feet) 16, I'm telling you BRAA from your favorite city. As long as you know where you are and where BULLSEYE is, you can figure out where the bandit is. Using BULLSEYE (I know, bullseye doesn't always need to be shouted in all caps) takes a bit more practice though. Remember: Whether you're trying to decide which way to point the radar or the Mk. I Eyeball, SA always comes into play. Boy I typed a lot more than I thought I was gonna. Hope it isn't too much for you.

Awesome, thanks!

I got that working, thank you very much! One thing though, I notice that the button function only works once I'm already past the limit. If I could trouble you just a little more, is there a way to make it so I can start at idle, hold the button down, and push through the limit that way? Gotcha, I didn't realize there would be push-through detents there. I'll probably go with that in the end, but the script should hold me off for now at least. Thanks!

I need a software detent, like the one provided by DCS F/A-18C. Using my Warthog throttle's hardware one is a nightmare because the whole thing lifts off the table when I try to use it despite how heavy this thing is. I want it like this: The throttle's full range is 0 - 65525 or whatever. I want it to stop at 50000 or so until I press a button. Then I want it to have the full range until I bring it under the 50000 limit again. Then the "detent" clicks back into place and it won't go past 50000 until I press the button again. Can anyone help me accomplish that with TARGET?

So I just recently found out about the A/B detent that you can enable for the DCS F-18. Now I must have it in ALL my after-burning jets! Sadly this probably requires use of TARGET's scripting, which I have no clue how to use. Is there anyone that can help me understand how to get my throttle axis to work like this?

I missed the "Mods" folder. You're right, I can change the settings for the F/A-18C there, but the MiG doesn't have a Views.lua file. There's a file called 03_Views.lua under Entry, but when I edit that the MiG becomes unflyable. Do you mean for multiplayer? It does work at least offline for FC3 aircraft. As I said, they are in the Server.lua file that can be edited and saved to "%userprofile%\Saved Games\DCS[.openbeta]\Config\View".

This is a serious problem for me as well. I too use an axis for zoom, and I need to specify a custom maximum field of view. I only recently discovered that third party aircraft, such as the MiG-21 and F/A-18C, can't have their view settings changed from "%userprofile%\Saved Games\DCS.openbeta\Config\View\Server.lua". Other, ED in-house planes, such as the F-15C and P-51D, are in the file and respect the edits to it. I found this thread: https://forums.eagle.ru/showthread.php?t=205338 That post is at least two months old as of now. I wouldn't want to wait two months before I'm allowed to not get headaches trying to fly my MiG-21 or F/A-18C, whether online or not! PLEASE do something about this!