Despayre

I had the same issue after the update... Using "\" brings up the menu, but it doesn't work. Now I've found that I have to bind "MIC switch FWD (Call Radio 1 Menu)" to bring up the menu. Never needed that keybind before, would have been nice if it was mentioned somewhere...

Then stop being ridiculous? "I really doubt Enzo was misremembering." Why? Do you know him? You've listed the speeds yourself above, he either misremembered, or lied, take your pick, but to argue that he must be right because you "don't understand why he is not telling the truth" while ignoring, math, physics, SME's, and documented specs followed by 2 pages of ppl here patiently explaining why your view does not line up with reality, and you keep coming back with variations of 'But a human wouldn't lie about something that happened years ago, so they must be right'... ya actually... tiny bit offensive.

Don't be ridiculous. Everything they did was real. Everything they said was not, and no one has to explain it to them, because I suspect both of them are much better at math than you appear to be, despite the fact that several people have explained it to you, and have even told you how to check the math yourself.

That's a standard loadout for me... never had an issue with splashing off the cat, other than when I wasn't paying attn.

Why? People misremember what they did yesterday, all the time, and that's when they aren't paying attention to 50 other "life or death details" at that moment. Also, you seem to be discounting various other reasons to exaggerate\obfuscate performance, such as classified specs, or deliberate misinformation, exactly like what was done with the MiG-25 Foxbat; the US thought it was a much better plane, (until they got ahold of one).

I don't think there's a binding for those.

Pretty sure that makes the Phoenix go active the moment it leaves the rails too. Dammit, beat my by || <-- that much... lol

Hey hey hey! That's not how the internet works! If you can't argue about it for at least another 10 posts anyway, are you even trying?!

1) Add night vision goggles to helmet instead of sunvisor 2) I believe means you can't use a Stored Heading alignment, you have to wait for a full alignment 3 and 4, not sure.

There are some planes I have to invert, and some I don't, but this sounds like it might actually be a physical controller issue. Have you checked with Windows calibration to make sure that the pedals do actually send the correct input, and that it has nothing to do with the game itself? Also, what plane are you using to set them up? (I checked on the F-15SE)

I have the exact same pedals, and I don't have that issue. They start off at negative 100, and when I push on either, they slide up to zero, and then keep going to positive 100. I have no changes to the default settings, am not using curves or anything else, my axis tune looks completely vanilla. I've noticed a lot of planes have 2 sets of wheel brake options, one's for an axis, one isn't. You're using the setup under "Axis Commands" for this, ya?

The exact way OP suggested, with one of the many rotary dials available on Winwing and other HOTAS'. Rotary encoder is perfectly straighforward with that method, it's the exact same way we dial up and down the lighting, set course headings, and a few other things. A POV hat doesn't work, that's a bad idea for that implementation as well. Next/Previous is, as I already said, not as good. It might be better than nothing, but it's not as good as, or better than, OP's suggestion.

It would be another option, but that's not nearly as fast as dialing to the right position would be. I don't think the 2 options are equivalently as fast.

*yawn* For those just getting here... here's where this thread is at... "tracks don't work, tracks don't work!"... Given inarguable proof tracks work from multiple users... "You got lucky, tracks don't work, tracks don't work!" ... Come on dude, move along.

Hmm, I went through a few pages of search results, but didn't see it... although I suppose, the more times it's mentioned, the more likely it might be to happen... (but I'm gonna run outta gas long before it happens anyway ).

I find those lights either too small to see, or perfectly placed behind the crossbeam of my planes. Would it be possible to create something like the FLOLS overlay so I can actually see the lights?

Ya, that volume starting at 0 thing caught me a few times... also, can't adjust the ICS in SRS, even though the volume knob moves in DCS.

Who do I contact to get my 5 bucks?

So is the lack of a sense of humour... or did the little smiley face not give you any contextual clues at all?

This seems like the problem. That should not be possible. On any multi-mon system I've had (I have been running multi-mon setups since XP) once Windows knows where the monitors are, and you change them, and apply changes, the same mouse movements should not still be possible... but from way over here, I don't have any more info to give you, but I'd bet 5 bucks that this is somehow the source of your problem, not DCS.

Futureproofing.

I don't know the exact boundaries of the upcoming Kola Peninsula map, but it's not impossible that part of it covers Zulu +1 (the vast majority of the peninsula is not, however).

Problem 1 - Windows setting, turn off taskbar on all monitors except primary. Problem 2 - If the images look right, it's not a problem, move on. Problem 3 - from the screen you took a screenshot of, you can literally grab the monitors with your mouse and move them onscreen to the correct positions. And yes, I read this part: 3) The order of the displays in Windows from left to right is 3-1-2, with display 3 being the main display. See screenshot widowed display setup. 4) arranging 1 and 2 in windows doesn’t have any effect. In real life the physical units are still arranged the same way compared to the main 4k display. I have to swap displays 1 and 2 physically, before they align in windows. I don’t understand this. it is as of windows always looks at the physical port and ignores the number. I don't know what's gone wrong to make that the case here, but that's not usually how Windows works, so my best guesses are either you have a non-standard monitor installation somehow, are using some drivers that Windows doesn't understand, or your X,Y values in DCS are not calculated correctly. What type of connections are your 2 smaller monitors using? are there any USB conversion adapters in play here?

Well now I know what I'm doing this afternoon... Tnx!

Where's the .miz file for that?