UltraMFCD for DCS 1.5/2.0

[Sgt_Baker]

Hi folks,

 

Apparently DCS 1.5.5 has completely broken uMFCD. But fret not! Already fixed on this end, and will be releasing a hotfix in short order. Would be releasing in this very post, but going to see whether I can get it to work in DCS 2.0 as well.

 

Watch this space.

 

--Baker

[the_soupdragon]

NIce one mate :thumbup:

[Sgt_Baker]

Edit: This post is now irrelevant.

Edited November 20, 2016 by Sgt_Baker

[Sgt_Baker]

UltraMFCD 2.5.5 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/

 

 

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:

 

* 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.

 

 

Happy flying!

 

--Baker

[BackboneOne]

i got CTD on DCS start

[Sgt_Baker]

i got CTD on DCS start

 

There's always one. :)

 

Mind posting a diag package over at http://forum.ultramfcd.com/topics/3-Support?bugs=?

[Sgt_Baker]

i got CTD on DCS start

 

Forgot to ask: Are you running the absolute latest versions of DCS? They changed lots of things between 1.5.4 and 1.5.5. This version of uMFCD doesn't work with the former.

[strike277]

When I start DCS after Starting Ultra MFCD I get the following Error. I have DCS 1.5 Updated to the latest version, Up dated my Nvidia Graphics DRivers as well. I'm Running Windows 7. IT also causes DCS to Stop working when I try to gointo the 3d world.

[G00dnight]

I think this is dcs does it work without UMFCD, if not do a repair, I use Skatezilla's update utility it is great.

[Sgt_Baker]

When I start DCS after Starting Ultra MFCD I get the following Error. I have DCS 1.5 Updated to the latest version, Up dated my Nvidia Graphics DRivers as well. I'm Running Windows 7. IT also causes DCS to Stop working when I try to gointo the 3d world.

 

Hi Strike,

 

Please submit a Diagnostics Package as per the instructions here. Saves a whole load of back-and-forth.

 

:)

 

--Baker

[Sgt_Baker]

Just a quick heads up. UltraMFCD 2.5.7 Beta is available here.

 

Now everything works properly in multiplayer.

 

--Baker

 

Change log:

 

* FIXED: UltraMFCD now passes multiplayer integrity checks. (Except for colour LITENING functionality. This is a legitimate unfair advantage in multiplayer, so allowing this change should be at the discretion of server admins. Switch this option off is you fail to pass the integrity check.)

* FIXED: Mission start dialogs no longer invisible during cold start and certain multiplayer scenarios.

* 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.

Known issues:

 

* 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.

[hansangb]

Sgt_Baker, question for you. Does UltraMFCD work with VR?

 

With Rift, I still like to use TM's physical MFDs. The problem is that MFDs work just fine, but exporting the MFCDs to the MFD doesn't work due to driver issues. I'm using USB monitors.

 

I was wondering if anyone used it with USB (Lilliput) monitors and Rift.

[Sgt_Baker]

Sgt_Baker, question for you. Does UltraMFCD work with VR?

 

With Rift, I still like to use TM's physical MFDs. The problem is that MFDs work just fine, but exporting the MFCDs to the MFD doesn't work due to driver issues. I'm using USB monitors.

 

I was wondering if anyone used it with USB (Lilliput) monitors and Rift.

 

This is something for which I currently have no hard data. That said, I'm inclined to guess that it wouldn't work out of the box. That and there's no easy way to develop in that direction without purchasing an OR - which is precisely why uMFCD needs to go commercial in the near future.

 

So do you mean you flip up the "visor" when using the MFCDs?

 

-- Baker

 

Edit: I'm slowly getting around to creating a "pure DirectX" implementation of the GUI, which would certainly allow uMFCD to work within fullscreen scenarios, and by extension that would likely open the possibility of it working in VR setups too. It's surprisingly easy to make things stereoscopic once you're at that point. Now the real question is whether people would want the VR exports to be fixed in place in the VR world, or to act like they were mounted inside the helmet, like modern HMDs allow...

Edited November 26, 2016 by Sgt_Baker

[hansangb]

Thank you. You can look out the nose of the bridge and it's pretty easy to hit the physical switches on the MFDs. In fact, if you line it up right, it's very natural as the VR and the physical world lines up.

 

I don't need the stereo view since I'm looking out the nose of the bridge. I just want to project the MFCDs to TM MFDs. The normal method doesn't work because Rift and DisplayLink drivers don't play nice.

 

I'll play around and see what happens.

[Sgt_Baker]

Thank you. You can look out the nose of the bridge and it's pretty easy to hit the physical switches on the MFDs. In fact, if you line it up right, it's very natural as the VR and the physical world lines up.

 

I don't need the stereo view since I'm looking out the nose of the bridge. I just want to project the MFCDs to TM MFDs. The normal method doesn't work because Rift and DisplayLink drivers don't play nice.

 

I'll play around and see what happens.

 

In that case it is theoretically much easier than it would be for a full-VR implementation. You might run in to issues where uMFCD complains and refuses to run under fullscreen, which is the result of its historical design. On the other hand, if you don't need to click or move the displays, the fullscreen issue is moot, so perhaps I'll consider that as more of a priority than it has been hitherto.

 

So the question is this: Do the Lilliputs work /at all/ when OR is operating? I.e. do they display the Windows desktop?

[hansangb]

In that case it is theoretically much easier than it would be for a full-VR implementation. You might run in to issues where uMFCD complains and refuses to run under fullscreen, which is the result of its historical design. On the other hand, if you don't need to click or move the displays, the fullscreen issue is moot, so perhaps I'll consider that as more of a priority than it has been hitherto.

 

So the question is this: Do the Lilliputs work /at all/ when OR is operating? I.e. do they display the Windows desktop?

 

 

They do not today. DisplayLink Driver and Rift doesn't work. But I'll play around this weekend and report back.

[Sgt_Baker]

They do not today. DisplayLink Driver and Rift doesn't work. But I'll play around this weekend and report back.

 

This is shitty design on the part of OR. All display drivers should respect other drivers. The concept of "exclusive mode" no longer exists in graphics on Windows. Sure, an app can take "exclusive" control of one screen, yet Windows keeps rendering everything else - thus the "exclusive mode" device really isn't. And hasn't been "exclusive" since Win7 (or perhaps Vista).

 

Does that make sense?

[hansangb]

It does. Right now, I'm stuck with two companies saying it's "the other guys' fault" LOL.

[Trollef]

Thumbs up, works like a charm.

 

EDIT: works like a charm in singleplayer. In multiplayer, the exported screens are not clickable and the app window reverts from detecting DCS to searching for it the second you go from briefing screen to cockpit. (It still works it seems, except for clickable displays.

Edited December 8, 2016 by Trollef
Might have found a bug, worth updating...

[ebabil]

i have downloaded this app but it crashes as soon as i hit instant action mission

[Sgt_Baker]

Thumbs up, works like a charm.

 

EDIT: works like a charm in singleplayer. In multiplayer, the exported screens are not clickable and the app window reverts from detecting DCS to searching for it the second you go from briefing screen to cockpit. (It still works it seems, except for clickable displays.

 

i have downloaded this app but it crashes as soon as i hit instant action mission

 

Hi there,

 

Both of you might like to try the two most recent beta builds available here, the latter of which specifically addresses the multiplayer issue and instant action crash.

 

--Baker

[dooom]

heya baker... i downloaded the beta version 2.5.7 after suffering the instant action crash on 2.5.5.... however - now when i detect/launch DCS, all of the exported displays are black. i can drag and resize them but the intended "repeat" real estate is just black. when i click exit on the mission, all exports flash to show the intended images for a brief second before going to the debrief screen

 

any ideas?

[Sgt_Baker]

heya baker... i downloaded the beta version 2.5.7 after suffering the instant action crash on 2.5.5.... however - now when i detect/launch DCS, all of the exported displays are black. i can drag and resize them but the intended "repeat" real estate is just black. when i click exit on the mission, all exports flash to show the intended images for a brief second before going to the debrief screen

 

any ideas?

 

Yeah, that's a failed experiment right there. What I was trying to do was make uMFCD a little more greedy with the gfx card when it gets close to 100% load, since it's presently throttling back a little too aggressively.

 

Think I'm definitely going to have to revert that change, since there are many reports of precisely the behaviour you're experiencing.

 

--Baker

[majapahit]

crashes DCS here loading

 

Problem Event Name: BEX64

Application Name: DCS.exe

Application Version: 1.5.5.59992

Application Timestamp: 5849dd5e

Fault Module Name: StackHash_bc7d

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 00000000

Exception Offset: 000000fffcaf5be9

Exception Code: c0000005

Exception Data: 0000000000000008

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Information 1: bc7d

Additional Information 2: bc7d03abe7c76b8f8ba09f2ccbe47f6e

Additional Information 3: a920

Additional Information 4: a9200f646579eef0db9c8c5fd7ee2c2e

[dooom]

is there a back version i should use then or just sit tight?