Sgt_Baker

UltraMFCD 1.0.0.49 is available at https://ultramfcd.com Now includes support for the KA-50's Shkval and ABRIS.

A sneak preview of the next release...

Yes, that is already a part of our "roadmap". As it so happens, we will support Windows <-> Windows prior to Windows/Android or Windows/iOS.

I concur. Coming from the A-10C, the F-15 is something of a shock to the system. Keep flying in bloomin' circles, I'm sure. :pilotfly:

This should now be fixed, btw. B

In a future release, yes. :)

Update: Above issue confirmed to be graphics driver related - nothing to do with UltraMFCD.

I doubt it's an issue with the RAM, but worth a quick test lest we chase other tails in circles. Edit: If anything, a potential "running out of steam" where turning RAM values in to physical signals is concerned.

Just a hunch (and a bit of a pain for you to test), but what happens if you take monitors 2 and 4 out of the equation by physically disconnecting them? The reason I ask is that altogether, those monitors make up an absolutely colossal screen area, even by modern standards. The way Windows works these days is that there's a program running in the background called the Desktop Windows Manager. It is essentially a full-screen DirectX 9 application. When DCS (and indeed uMFCD, which is also end-to-end DirectX) draw to the screen, they in fact do nothing of the sort. What happens is that each app draws to what it "thinks" is a screen, and then DWM composits everything together on to its "master" DirectX surface. Now, looking at that monitor setup, I reckon the DWM is running a fullscreen surface (which has to contain all the monitors, incuding the offset one) of appx 7570 x 2500. Having googled all sorts of things about your gfx. card, I can find nothing to suggest that it /really/ supports resolutions that high. Thus, since things going B&W and random colour squares are waaaaaay outside anything we've seen from uMFCD thus far, I'd like to eliminate the possibility of your gfx driver going quietly loopy under the load. B

OK. It would appear that we've got a few potentially unrelated issues all occurring at once here. It's odd how some people seem to get all the back luck. :) Let me ponder what might be going on for a while, then I'll be in touch via PM if that's OK? B

Well I have to hand it to you: This one gets top points for weirdness. :) A couple of questions: 1) How are your screens arranged relative to each other? (A screenie of the windows display setup stuff might come in handy.) 2) Are you using any third-party display manipulation technologies, such as nVidia surround, SweetFX etc? 3) Could you post your monitor setup lua, please? Thanks, although I'm not quite sure what you mean regarding the CCD... Baker

Hi Jateu, As it stands, iControl requires the MFCDs to be displayed on-screen. That said, the developer and I have formulated a plan for the near future whereby iControl will receive its video streams directly from UltraMFCD, which will solve your problem. Watch this space. :)

It's a pleasure. Working with flight sims is my dream job. :)

uMFCD will override whatever you put in there (or at least is supposed to). Become a Beta Tester and try it out! :)

Yeah, the F-15C's radar export is a little odd. Comes pre-shaded in red, for some reason. I apologise that uMFCD presently affects things it shouldn't. Had to remove a load of "sanity check" stuff to get the most recent release to work properly. If you go to C:\Program Files\Eagle Dynamics\DCS World\Config\MonitorSetup you can modify one of those presets to display the radar. What you need to add is, approximately: _ = function(p) return p; end; name = _('Camera + LMFCD'); Description = 'Left MFCD on the left and camera on the center' Viewports = { Center = { x = screen.width ; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } LEFT_MFCD = { x = 0; y = screen.height - 400; width = 400; height = 400; } UIMainView = Viewports.Center Will give you a 400x400 radar on your main screen. Modify as desired, and yes, you have to do the weird RCtrl-Enter (?) to get it to display.

UltraMFCD doesn't support the F-15C at the moment, although it's pencilled in for the future. We did some custom work recently at the request of a company in France, and once the A-10C's uMFCD is good for release, i.e. out of beta, we'll be tackling ALL the F-15C's displays, not just the radar. That said, if you read up on how to manually export displays, I believe the F-15C's radar will adhere to LEFT_MFCD.

UltraMFCD 1.0.0.46 is available. With particular thanks to Icemaker and Calexo for being hardcore and undauntable beta testers, here is 1.0.0.46. It vastly improves support for custom missions, multiplayer and Helios. https://ultramfcd.com

1.0.0.46, which contains all the relevant bug fixes, will be out tomorrow.

Update 2: Make that three major bugs squashed, each of which became apparent immediately after fixing the previous one.

Update: We have just this minute found and fixed another rather major bug which affects both Helios and Multiplayer. It only became obvious what was going on (i.e. we were previously unable to reproduce the problem) after the .43 patch. It's in testing now, and we hope to get this out as soon as possible. :)

UltraMFCD 1.0.0.43 is available for download at https://ultramfcd.com This release should further improve compatibility with Helios. While we've made great strides in this area recently, there are so many variations on peoples' Helios Export.lua configurations that it's impossible to know where we've got it totally right yet. Thus, please report any unusual behaviour you might experience while using uMFCD with Helios.

Sorry, my bad.

I don't think that's strange at all. While both are 5th generation aircraft, the F-35 is a whole sub-generation younger than the F-22, thus will obviously contain more modern technologies which were developed post-F-22. Due to the fact that so much of a modern fighter's kit is software driven these days, it's no surprise to see these sorts of retrofit. Potentially much easier than it used to be. :)

Join the "Virtual Aerobatic Server 1.2.14 Up 3" and you'll see that all the UltraMFCD buttons work as expected. :)

Due to people beginning to miss this thread and ask questions about uMFCD all over the place, I've started a new thread with UltraMFCD in the title here.