Despayre

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?

Wait... There's a manual?! - says 99% of DCS players...

I think that would be very hard to determine. Soo many variables that change... AI will do the same thing every time... 2 humans, not so much, even if both were equally skilled. As a baseline, if the hits against the AI go up, it's reasonable to assume there would be some corresponding (although not exact) increase against humans too, who, sometimes, are less than perfect, unlike our future overlords.

I think the best solution is to rename the WSO MFCD's... WSO_LEFT_OUTER_MFCD WSO_LEFT_MFCD WSO_RIGHT_MFCD WSO_RIGHT_OUTER_MFCD Never have a problem ever again, nor with any other module, current or future

Were the contacts on radar at the time? Were they identified as hostile, or just targets? (those are 2 different locking asks for Jester, asking for enemy lock, when they are only targets, won't work). Also, inside 20 miles is when I start thinking about switching to PAL mode anyway, usually quicker. Additionally, I've seen AWACS targets on my radar that Jester hasn't seen yet, I don't recall being able to lock those up either, but that's only if you're using an AWACS that you forgot to mention.

Is it possible to do that for switching between the front and back in the F-15E? We'd need a different variable, not unit_type I wouldn't think.

Actually, it's the well known category of "absurd", much like your claims here.

Can we use something like this to have separate sets that work, for both the front seat and the back? IE, I'd like to export 2 MFD's from up front to a second monitor, full size, but in the back, I'd like to export all 4, and still have them fit on the same second monitor, obvs, they'd need to be resized too.

Tacan - STEER CMD TACAN (Category: PDCP) A/A - Display mode air to air (Category: PDCP) A/G - Display mode air to ground (Category: PDCP) Dest - STEER CMD Destination (Category: PDCP)

Who do I report this to? My car doesn't teleport... obviously, since it was never a feature, it's a bug. I'd like it fixed. Even more annoying, my car isn't even in Beta! What the hell Toyota?!

The F-15E doesn't even allow exports yet. Hard for a 3rd party to write for something that doesn't exist yet. Pace yourself. Legit question on the AH-64 though.

Is that Shift-3 on the UFC?