Sgt_Baker

OK folks, Could those of you who have recently reported severe functionality problems (crashing, not getting to "Running" status (see video in my sig)) please download the latest version - 1.0.0.57 - and go through the procedure for generating a diagnostics package, please? Would be very much appreciated. :) Regards, Baker

UltraMFCD 1.0.0.57 is available at https://ultraMFCD.com Fixed: DCSBios should now work alongside UltraMFCD. Further fixes to support for Helios. Improved: Gather Diagnostics Package now collects last-ditch error information in the event of a crash on start. If you've been experiencing this sort of error, please create a diagnostics package and post it to this thread.

OK, a fix for DCS Bios compatibility will be in the next release. :) Baker

Thanks for that. It's immediately obvious where the problem is occurring. What DCS Bios does is move all the functions that are usually in Export.lua in to an external file. Will have a think about what to do about this.

I doubt you're missing anything. What is supposed to happen is that you simply launch the app and off you go. The presentation of this bug is identical to a few reports we've had recently. In each of those instances the bug went off and hid again before we were able to derive a proper diagnosis. In the latest instance, the user discovered that there were six copies of uMFCD running - while this shouldn't be possible, it would be worth checking Task Manager to make sure this isn't the case. So... still working on this. Hope to get it sorted soon. Baker

Hi SpeedStick, Do you happen to have any mods installed to DCS? Clearly, we're still trying to track down what's causing this problem. Regards, Baker

The ability to do so is largely coded up under the covers. All we have to do is enable to UI to achieve this along with the relevant internal testing. Will appear in the very near future.

I'll look in to this, but the simple solution would appear to be leaving the option checked for the time being. No loss of functionality that way. :)

Hi Skorak, To be perfectly honest, I've never touched DCS Bios. While there isn't a conflict regarding the networking ports, this bug could very well be similar to those we face with Helios previously. The thing to do here is to get uMFCD to generate a diagnostics package, then post it here (which obviously requires you to use the latter method where uMFCD runs). Doing so should give us some clear indications as to where the conflict is occurring. 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 or a PM to myself. Cheers, Baker

I think the jet considers such things as "is my gear down?" and "is the radar altimeter reading zero?" when attempting to determine whether it in on the ground. Quite possibly reading pressure on the landing gear too. Most of these things can be read from the sim via export.lua. However, enabling a modifier in real-time would involve some rather invasive and difficult meddling with the sim's Lua system. Probably more effort than it's worth. Not impossible, but does the work outweigh the benefit? Edit: For what it's worth, I took a long hard look at the input system while developing uMFCD. I decided to leave it well alone.

Hi Scott and TonyZ, Yours are the second and third reports of this bug in a 24h period. We were first made aware of the issue by somebody who emailed us directly. In that instance, too, the bug vanished before we were able to get a decent bead on it. Will be monitoring this in an effort to eliminate the problem. In the mean time, I'm glad you're finding the app useful! :) Regards, Baker

Hi Scott, There's definitely something going very wrong there. We recently introduced a diagnostics feature that should help determine what's going on. Could you follow the steps below then paste the output to this thread, please? How to use Generate diagnostics package: 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 or a PM to myself. Additionally, could you check whether the Windows Event Log contains anything pertaining to the crash, and include that too. Many thanks, Baker

Hehe. I know! Not ignoring you. :)

UltraMFCD 1.0.0.56 is available at https://ultramfcd.com Fixed: FRAPS, TS3 Overlay and the like are now supported. Given that enabling support for these tools requires some rather fundamental changes to the core of UltraMFCD, we would be very interested to hear about any stability issues while using these apps. Further improvements to the KA-50 ABRIS & Shkval Known issues: The KA-50 caution lights appear overlaid on the ABRIS export. We will be releasing the caution panel as an export in its own right in the very near future. Key bindings don't work with KA-50 yet. (Much more to come in this area!)

Thank you, thank you and thank you. :)

Thanks Watar! In one quick act you've pointed me straight to where the bug is manifesting. :) I'll issue a fix in short order. (To keep things sane in here, you can go ahead an edit that "wall of code" down to something a little less... imposing)

Forget what I said in my last post... UltraMFCD 1.0.0.53 is available for download at https://ultramfcd.com Fixed: When running uMFCD with the KA-50 for the first time, the Shkval would appear in the same aspect ratio, size and position as the ABRIS. New: Since the introduction of support for the KA-50 last week, some users have been reporting that the Shkval and ABRIS appear as solid black displays. Unfortunately, we've not been able to track down this bug internally as yet. In order to simplify life for our beta testers while looking for this bug, we've introduced the "Generate diagnostics package" feature. What it does is gather up all the files that could be causing problems for/might help with fixing uMFCD and generates an output to the System Messages section that you can easily copy/paste here. How to use Generate diagnostics package: 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 or a PM to myself. Much easier than finding all the right files and pasting them manually! :) B

*shameless plug* You can get this automatically with UltraMFCD. *shameless plug*

Precisely what Icemaker said. If possible, could you PM me C:\Users\<yourusername>\Saved Games\DCS\Scripts\Export.lua and C:\Users\<yourusername>\Saved Games\DCS\Logs\DCS.log after trying to run with UltraMFCD, please? Many thanks, Baker

Really appreciate your saying that despite the fact you can't actually use it yet.

You can set your resolutions to whatever you like - no need to make any specific accommodation for uMFCD. Of course, you'd already know that if you weren't experiencing the dead-screen bug. :)

/dxgui/ contains all sorts of things that don't pertain to flying an actual aircraft. Then again, it might be hard-coded in launcher.exe. Only way to find out is to snoop around. :)

This is absolutely correct.

Sorry: Just to be clear, I already have a diagnostic build cooked up to test exactly what is going on. Have simply been busy in other areas over to past few days, so not enough time to commit to a quick reaction fix/diagnostic update/whatever is required. When presented with problems like this, it is our preference to work with a small number of testers in close to real-time than a huge number while relying on the forum for feedback. I'd be more than happy to contact you via PM when the diagnostic build is ready.