Sgt_Baker

Hi Deezle, In order to help us work out what's going on, could you go through the procedure for generating a Diagnostics Package, please? It will save asking a lot of the initial questions. Instructions: 1) Tick the relevant check box in the Settings section before launching DCS. 2) Start a flight in your aircraft of choice. 3) Once your flight has ended, a large amount of output should appear in the System Messages section. 4) Select All (Ctrl-A), Copy (Ctrl-C) then paste the output in to this thread. Many thanks, Baker

Entirely doable. Will put it on the list. :)

Sneak feature preview: Disable the in-cockpit display of any supported export. A-10C left/right MFCDs now completely independent entities. And lots more. The next update is a big one! :)

Thank you, There are a few more new features inbound for the near future: A-10C Countermeasures System (CMSC/CMSP) More KA-50 stuff (although I'm far from competent in this aircraft, so it takes me longer to figure out what's useful). Definitely fixing the issue with the caution lights. Kneeboard A greater number of key bindings, along with improvements to the underlying code. 3rd-party API, so iControl etc can do their thing without having to render exports to the cockpit. :) Baker

UltraMFCD 1.0.0.58 is available for download at https://ultraMFCD.com New: You now have the ability to select only the exports you want (see new Exports tab in Settings) Improved: All touchscreen, physical and DirectType actions more responsive. Starting with this release, UltraMFCD will start to be more assertive with how it handles interaction with other mods that it should, by design, be overriding. This should help users who may have had manual screen export mods installed in the past, but not be able to manually remove any modified files.

You may have mentioned it on occasion. :)

There isn't a hotkey to perform this action at present, yet adding one would be a trivial act. The functionality is already present in the form of the "Hide displays when outside DCS" feature. Would simply need to wire up a binding to trigger this system manually. Definitely a great idea which will be included in a future release. Baker

Yes, we have a a few users utilising touchscreens in this manner. For the record, another person was in touch a while back regarding compatibility wit the Acer T230H. It's worth noting that the reason there's no driver for Win8+ is that Mircosoft are refusing to certify a driver on account of the screen not supporting 10-point touch. Rather frustrating when things like this happen. Regards, Baker

Use your imagination. :)

Yep. That would be because we haven't implemented the CM systems yet, and a weird quirk of DCS is that they'll refuse to render until such time as we do. High on the list of very-near future additions. Apologies for the disruption in the mean time.

Good to know. :) While we're at it, mind editing the diag output down to something a little less "wall of code"?

Hey G00dnight, Thanks for the diag pack. While I can see that you're loading DCS Bios via your export.lua, there is absolutely no sign of anything to do with Helios. Did you stick all their stuff in BIOS.lua? If so, could you send me that too, please? Baker

And I'm not going to have an Internet Argument™ about this. The A-10C modelled in this sim definitely does not support an HMCS.

If you don't mind, Snoopy, they were thinking of them as something later than C models once they gave them HMCSs. :)

It's a feature supported by an aircraft that ED knows nothing about. I'm not saying that it's not possible, yet this is something that is specifically NOT included in our sim on account of being "very classified". It's far easier to use the "boresight" - along with accurate flying - facility of both the Mavs and the TGP to point them in the general direction of the enemy. Try it. It's very useful. You might like it.

F.ex: You cant shoot a 9M or a 64D "over the shouder" by definition.

On second thoughts, the A-10C (in DCS) doesn't carry any munitions that would render a HMCS useful. Those toys are reserved for the A-10E/F onwards - the likes of which we do not have in DCS. It /is/ possible to implement something of this sort, yet wholly unrealistic since it would require intimate support from ED to even begin to contemplate.

Do you mean using TrackIR 4/5 as the cueing system?

And yes. Just as DCS 2 will be better, uMFCD 2 will be better in step.

Hey Joe, where you goin' with that gun in... Sorry! Got distracted. I've checked the code and the top-left button is no different to the 19 others. In fact it's the one I first click when testing uMFCD internally. I don't have a touch-screen setup here, yet it works under all circumstances that we're aware of. The "glitch" is likely your screen issuing multiple clicks in short order; or none at all. Regards, Baker ..I'm goin' down to shoot my ol' BMP. And I shot it! I did!

You're welcome, and good work spotting the obvious snafu, despite not being a coder... who compares files in Notepad++ :thumbup:

Well... everything I do with DCS rather demands I keep a factory-pure copy of the sim. If your problem has gone, and you're running the latest version.... all good?

All the "hard" work to make this happens has already been completed. As I said in a previous post, all that remains is to activate the UI, along with making sure it actually works properly. :)

Anything of this nature will help. Viewports not appearing suggests that the front-end of uMFCD isn't receiving the signals it requires from the code that's running inside DCS, which in turn suggests that something is going wrong therein. As it happens, the Diagnostics Package system has proved so useful in eliminating a whole number of bugs very quickly that it will see significant development in and of itself in the near future.

Hi Fakum, A good place to start looking for changes to the kneeboard is its init file (C:\Program Files\Eagle Dynamics\DCS World\Scripts\Aircrafts\_Common\Cockpit\KNEEBOARD\indicator\init.lua). Compare what you find in there to the unmodified variant, which is in the spoiler below.