Sgt_Baker

The further you delve, the more complex it gets, but this is what you're looking at there: https://en.wikipedia.org/wiki/Military_grid_reference_system Each super-square is 100,000m on a side (54 Nm, as Cibit said). Figuring out the rest should be pretty simple. :) Edit: You can also specify that DCS use MGRS throughout via the Misc. tab (I think) of the settings screen.

...including the upside-down rendering, should you be using a reflector.

I've noticed similar oddities - principally a single-frame flash of the theatre map from the mission editor when clicking "Start Flight" - even if I've not edited the mission. No biggie, but detracts ever so slightly from the required "slick" feel. :)

There is no longer an option in DCS for /turning off/ Aero. "Aero" refers to the technology whereby everything you see and touch in Windows is rendered by DirectX, whether a game or a normal desktop app. Windows 7 onwards use that system by default, hence ED having removed the option to switch it off.

So you need to know how to convert latitude and longitude to miles? Am I getting that right?

Yes. The plan is to introduce said support to Windows, Android and iOS in that order. Why iOS last, you may ask. I've worked on iOS apps in the past, and it was... erm... I don't like corporations telling me what to do and how to do it, while paying for the privilege. :D

Exactly that, yes.

Absoutely! Those plans were on hold has a result of knowing that the entire "internal engine" of uMFCD would require rewriting for the DirectX 11 of DCS 1.5+. I did, however, perform some of the preliminary work required to support the F-15 (and other FC3 aircraft) back on DCS 1.2. Here's a pic of the F-15's displays isolated, but not transformed back to the screen-plane:

If you fly ~80nm West off the coast of Bantumi, you'll find a model of Deepwater Horizon.

Well... I could release it tomorrow, but I'd feel kinda dirty doing so knowing where/what the bugs are. :)

So things are essentially back to where they were with UltraMFCD 1.0. There are a few little bugs here and there that I need to sort out, but we're now at the point where there is absolutely no doubt whatsoever that the system works as expected with DCS 1.5/2.0 (although I've not tested 2.0 as haven't yet bought NTTR, although the innards of the graphics engine aren't expected to have changed nearly as significantly as between DCS 1.2 and 1.5). Here's a pretty pic...

First serious milestone reached: :)

I appreciate the urgency :) That said, it's greatly important on this end of affairs to release something that works properly and as designed, as opposed to placing demands upon the user to constantly fiddle with a mod's configuration, settings and overall setup. What made uMFCD 1.0 "different"? "It just works." No messing around. Obviously, given the height at which the bar has been set, it would be a little silly to release something prematurely. Hope you understand. --Baker

Update: 95% of the way towards releasing something you "display heads" can play with. :) Fixed some rather catastrophic errors in my DX11 code. Kicked myself a little bit for working too late on things that are very sensitive to mental fatigue. Drank lots of coffee.

Yes, now you're beginning to "see" what's been causing all the confusion recently. You're correct in that Windows would hide DCS if Helios (uMFCD, Desktop or anything else) were clicked in the instance of it genuinely running in "exclusive mode". The bottom line is that if Helios works with 3D Vision as per your setup, then uMFCD will work too.

Thanks for the ongoing support, folks. Airline Pilot's Voice: "Well, a little spot of bother back there, but we're through the worst of it, so just settle back and enjoy yourselves." :)

Yep. uMFCD turns exported displays in to normal windows, so they work on any screen that Windows™ works with.

Have a look in C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Sounds (or eqivalent). Presumably you should be able to overwrite whatever effect you find there with a file of your choice.

There are currently no plans to implement fullscreen support. I've explained this extensively in the past, but it essentially boils down to the fact that "proper" fullscreen ("exclusive mode" in graphics parlance) doesn't really exist any more, and the effort involved in implementing said mode far, far outweighs the justification in terms of the number of people it would benefit. Having read the threads you linked, that seems more of a bug with DCS, no? Surely they'll resolve the issue separately and in their own time?

Oh, and all those driver-related problems are no longer a problem.

UltraMFCD 2.7.0 for DCS 1.5.5+ and DCS 2.0.4+**** NTTR is available Click, Drag, Resize and Enhance DCS exports. Zero configuration - just launch and fly. Download link: https://ultramfcd.com/ New UltraMFCD 2.7.1 Beta available here. Includes new dual kneeboards and other fixes. Changelog: NEW: Dual DCS and UltraMFCD kneeboards. NEW: Kneeboard exports available in all DCS modules, even when no other displays exported by UltraMFCD. NEW: UltraMFCD kneeboard displays updates from DCS Kneeboard Builder in real-time. No restart of flight required. FIXED/NEW: Fixed bug where DCS kneeboard would display inside other exports. DCS kneeboard now exported as a full UltraMFCD display. NEW: UltraMFCD plays a warning sound if it detects problematic settings upon DCS launch. FIXED: Bug where blank displays could remain on-screen from previously flown aircraft. FIXED: An UltraMFCD window, when clicked, will now move to the foreground as expected. FIXED: Circumstances where UltraMFCD displays might prevent DCS receiving keyboard/joystick input due to clicked UltraMFCD export window stealing focus from DCS. FIXED: Su-25T Shkval display now correctly remembers its position. 2.7.0 Changelog: NEW: F-15C TEWS export now included. IMPROVED: Better handling of notifications regarding DCS settings. FIXED: Serious crash where uMFCD would complain about "MonitorSetup.lua" and "SharpDX.Desktop.DLL" now, finally, resolved. 2.6.6 Changelog: FIXED: Flickering CDU/RWR in A-10C CHANGED: All displays now utilise latest code developed for CDU. IMPROVED: Smoother framerate and more sensible yielding to DCS (frame dropping) when GPU at 100% load. FIXED: A-10A now works as expected. FIXED: Issue where scaling option in Windows Display Settings caused displays to render incorrectly. 2.6.5 Changelog: NEW: Support for Su-25T, Su-27, Su-33, Mig-29A/G/S & F-15C FIXED: Kneeboard reintroduced. FIXED: Keybindings now work again. FIXED: UltraMFCD windows disappearing when viewing DCS FPS data (Ctrl-Break). Changed: "Hide displays when outside DCS" now defauts to off. FIXED: UltraMFCD now passes multiplayer integrity checks. (Except for colour LITENING functionality. This is a legitimate unfair advantege in multiplayer, so allowing this change should be at the discretion of server admins.) FIXED: Mission start dialogs no longer invisible during cold start and certain multiplayer senarios. FIXED: Display buttons now work in multiplayer. FIXED: Ka-50 Shkval now respects request for no cockpit rendering in DCS 2.x NTTR. Improved: Better FPS when graphics card close to 100% load. FIXED: Strange behaviour of mouse pointer fixed. This is a kludge of a fix in DCS which coincidentally broke uMFCD. NEW: Improved CDU graphics. NEW: Added "Show Test Displays" for debugging purposes. FIXED: Touchscreen users no longer experience double-click. FIXED: Multiplayer briefing screen now displays reliably. FIXED: Changing aircraft in multiplay now possible without exiting server. FIXED: Quit dialog now visible after aircraft descruction. UN-BROKEN: Displays visible on mission restart. 2.5.5 Changelog: * Reintroduced: A-10C's RWR, Clock and CMSC. * Reintroduced: KA-50's Shkval and ABRIS. * FIXED: Now works with DCS 1.5.5 and DCS 2.0.4 NTTR. * FIXED: Windows 7 "black screens" problem solved. * FIXED: UltraMFCD now works with low/medium water settings, HDR enabled and Lens Effects enabled. * FIXED: KA-50 warning panel no longer renders within Shkval and ABRIS exports. * Improved: Simplified core engine. Places much less strain on DCS. * Improved: Smoother rendering of exported displays. * Improved: Overall stability better. Complicated behind-the-scenes changes to how DCS and uMFCD communicate should result in fewer crashes. * Improved: Vastly better error handling. Much higher probability of uMFCD producing a Diagnostics Package that is useful for solving problems. Known issues: **** "Deferred Rendering" option in DCS 2.6.1 Alpha causes crash as of 2017-05-30. * Not compatible with DCS 1.5.4 or below. * Exit mission dialog invisible after eject/crash. Entering F10 map view will enable the quit dialog. * Air/ground unit labels (Shift-F10) do not display properly. * TGP image doesn't update when in external views (F2 etc). This is because DCS itself no longer updates the TGP when you're "outside" the cockpit. * DCS kneeboard renders incorrectly. (Will be fixed in uMFCD 2.7.1) Happy flying! --Baker

BC, eh? Without wishing to press home the issue - except I am, as somebody who grew up among the mountains and fjords of Norway - it would be nice to see a "we're looking in to it" as opposed to a "there cannot possibly be a problem".

Here's the screenie, as requested. It's worth noting that when I'm not making mods for DCS, I stand as the last line of defence between graphic designers and their super-litigious clients. A standard conversations goes: "Those two shades of red are not only completely different, but also nowhere close to the client's trademark red." "What are you on about? They're exactly the same!" "It's called the 'colour picker'. Use it. Frequently." So yes... it does look strangely blue on the monitors that preserve the colour-integrity of some of the largest brands on Earth. :) Edit: actually included the screenie.

As per the title, really. While excellent strides have been made regarding performance, I cannot help but notice that the Black Sea theatre is now rendered, from altitude, in a distracting shade of blue. Having spent significant time above 18,000ft myself, I don't particularly recall the sensation that my eyeballs were malfunctioning (other than seeing the Sahara desert from 40,000ft, in which instance my entire brain malfunctioned). Running DCS on an AMD 7970, not that it should matter much. :) --Baker

Much appreciated. :)