Sgt_Baker

Good News! (No, it is not the Dacia Sandero) uMFCD now works properly with the reference Helios Export.lua provided earlier in this thread (sorry, I forget who). Just for purposes of verification, I've re-attached here to make sure we're all on the same proverbial page. The patched release will be out very shortly. B HeliosExport.lua

As per Twitter request, the CDU now includes Steer Pt +/-.

I'd personally still need physical faders, but apart from that the future lies in large touch-enabled control surfaces.

P.S. If you're wondering why the developer only has two screens... It has everything to do with the ideal placement of studio monitors while making music. :) P.P.S Since we're all essentially nerds, I thought I'd share that apart from the TM HOTAS, this is the coolest toy I own.

Hey folks, I'm going to add a section to the website concerning multi-monitor setups, windowed mode etc. Given that I'm a relatively dull two-screen chap, I wondered if those of you with more esoteric setups could send me a screenie of the Windows display settings? Would be much appreciated. Many thanks, B

Hi Dan, Hope the fullscreen switch sorted the problem. :) Yes, uMFCD will definitely support networking in the future. We experimented with such functionality as early as June last year, and it worked rather nicely. Another case of: Watch this space. B

Hi Dan, Could you be a little more specific as to what is happening, please? B

New material on the website: https://ultramfcd.com/User-Guide/A-10C-MFCD https://ultramfcd.com/User-Guide/A-10C-CDU https://ultramfcd.com/User-Guide/A-10C-RWR :)

Of course. This requires that I redesign the settings UI to make space for all the new stuff, but under the covers this type of binding is already supported. Edit for clarity: The UI is already scheduled for a redesign, so will support this when that's complete.

This is indeed uMFCD's fault. You're right, though, in that I have been contemplating introducing kneeboard functionality. :)

They feel sterile to me. Then again, I've never actually flown an A-10 nor an F-15.

Preamble: I have not read this thread in full, since spending far too much time stuck to this keyboard/monitor/mouse as it is. :) Statement of fact: None of the FC3 flight models feel in any way "real". This is to be expected. We pay $40 for a hypersim of any given aircraft, and cannot expect the same fidelity from the lesser cousins of those products. An observation: If I'm not entirely mistaken, the F-16 had a "shuttlecock of death" mode of stall where it would fall from the sky the right way up. I recall (from FFAF) there being an "Override" button on the FBW which would allow the pilot to rock the aircraft out of the plunge. Conclusion: Negative stability comes with a plethora of caveats. While the SU-27's flight model might not perform as desired, the modes of failure are closer to the "die or die trying" state of affairs in RL. Bottom line: If every SU-27 pilot would part with $40, we'd have these problems fixed in no time at all.

Just tested this and the display clears as expected.

It's worth noting that the beta versions of uMFCD need to be able to contact ultramfcd.com upon startup. If something goes wrong, such as a dodgy connection or the site going down, the app will think that it has passed its expiry date and shut down. This feature will not be present in the release versions, which will require the purchase and entry of an activation code once the trial period has expired.

By all means. It's a case of "fitted for but not with" at the moment. I need to engage in a little bit of refactoring, and had planned on implementing keyboard state at that time.

Thanks for the report. This is now patched and will be included in the next release.

That'll happen in the relatively near future. The first release will cover the A-10, with a similar setup for the KA-50 to follow shortly thereafter. The beta is fully-functional and stable, so feel free to take it for a test drive. Link at the bottom of this message.

Thanks for the clarification. You'd be surprised how difficult it is to get beta testers to say "everything is OK" or "problem was unrelated", so really appreciate notifications such as this. :)

You can drag them to and click them on any monitor that's connected to your machine - assuming Windows is aware of it. Additionally, every display can remember up to three positions and sizes, so you can, for example, quickly expand the TGP to maximum size when you want to take a close look at something, stowing it to a smaller and less obtrusive position when it might get in the way of the Mk I Human Eyeball.

Ooops & Fixed. Patched version available at same URL. :)

Beta 1 Update 9 ( 1.0.0.28 ) is available at https://ultramfcd.com/ Fixed: CDU juttering around while being dragged. Added: A10-C Radar Warning Receiver Near future: The remainder of the A-10C's countermeasures system. Better compatibility with various mods, such as Helios and SweetFX Fix for issues with kneeboard.

I've been experiencing random crashing, which I thought was down to a mistake I'd made with uMFCD. After a day of fruitless combing my code, I decided to let DCS run alone. This was in Free Flight Air Start. Here's the crash log: :) Faulting application name: dcs.exe, version: 1.2.14.35734, time stamp: 0x54a12324 Faulting module name: ZweiBlau.dll, version: 1.2.14.35734, time stamp: 0x548c854b Exception code: 0xc0000005 Fault offset: 0x000000000000fe22 Faulting process ID: 0x1584 Faulting application start time: 0x01d0335d47e1d2fc Faulting application path: C:\Program Files\Eagle Dynamics\DCS World\bin\dcs.exe Faulting module path: C:\Program Files\Eagle Dynamics\DCS World\bin\ZweiBlau.dll Report ID: 42a175e2-9f51-11e4-9fa6-5404a62c6dd2 Faulting package full name: Faulting package-relative application ID:

I've been getting DCS crashes (access violation exception) with and without uMFCD. (Read: A day spent tracking down a bug that appears it /may/ have nothing to do with me). Watch this space. :)

Long-awaited "new stuff" will be in the next release.

Yep, used to do that in EECH. Laser Hellfires /did/ have a purpose. :)