Sgt_Baker

Yes, we're aware that this happens. It would appear that SweetFX makes sufficiently wide-ranging changes that UltraMFCD gets very confused indeed. It's on the fix list at a medium priority (because who doesn't like things to look nice?)

If, however, ED were to see this thread and think "Hmm... we could release TAD_COLLECTION.zip freely to all users of /any/ ED product"... then we might be in business, as it were. :)

Yes. And please stop thinking like me. You're going to put me out of a job! :) The issue is not technical. All of the behind-the-scenes stuff to enable "live maps" is already done. The issue is that ED owns the mapping material, and thus far, I've managed to contrive UltraMFCD in a fashion that requires no royalty payments whatsoever. Including the maps would.... lawyers.... contracts.... pains in the arse.

Yank a card?

Where are you going with that?

This is just a hunch, but what happens if you uninstall the USB-display drivers completely? The reason I ask is, as a result of researching extensively recently, they now claim "hardware acceleration". Given the hardware specs, nothing could be further from the truth. I suspect that there are attempts at the driver level to DMA whole screens (literally FPS) of data from Window's DWM (which lives in a graphics card on the PCIe bus) via multiple routing points on the motherboard in order to spew it back out of a USB port. All in all a bad plan. --------- Other prognosis: UltraMFCD and DWM might be getting confused where the SLI situation is concerned. Please check your settings to ensure that you're REALLY running on a single, non-SLI gfx card. As a last resort, literally yank the second card from your system. --B

Yep. To use the Anglo-Saxon vernacular: That is ****ed up. Have you installed any other mods/systems that might fundamentally affect the rendering pipeline?

Forget everything you've read in this thread regarding TM Warthog extenders. THIS is the one you want:

Ah, right. I have discovered a bug whereby uMFCD would attempt to upgrade settings from a previous version after a reset. If said prior user.config contained invalid display positions, there's every possibility that they would have been carried over. Counter-intuitively, it would appear that hitting Reset All while uMFCD is running should produce the intended result in real-time (which was an element of a large behind the scenes update a while back). Additionally, uMFCD would immediately save the values of all the "visible" settings, which would lead to the impression that a hard reset of the file hadn't taken place. This behaviour has also now been fixed. So, in the meantime, please try the following in order: 1. Hit "Reset All" while uMFCD is running and intercepting DCS. 2. If that fails, delete absolutely everything you find pertaining to UltraMFCD (all versions) under the path mentioned earlier. If we're still no-go after performing the above, we'll have to investigate further. Regards, Baker

Who are you educating? ;) P.S. See latest "known issues" from my website: "nVidia's latest graphics drivers (352.86) cause extreme lag/low FPS for exported displays. The problem with this particular driver set has been noticed to manifest with a number of games, not solely UltraMFCD. We will be monitoring the situation closely. If this issue affects you, rolling back to the previous driver (347.52) will resolve the problem until nVidia releases a patch for the latest driver." I code in 100% standard DirectX. No "shortcuts". No "little tricks". (They all made DCS unstable to the point of it not being worth the effort.) How can a single driver update screw up 100% Standard DirectX?!?!?

Given that I am something of an "expert" where DCS and its graphics are concerned, I can say only this: There appears to be no rhyme or reason where DCS and rendering are concerned. Things that should impact FPS severely run quickly. Things that are, as standard in other graphics engines, hardware-accelerated to the point of not existing at all run like a horse on ketamine. I can only surmise that this may be a result of DCS being largely based on the FC engine, old as it is, an excessive reliance of Lua to perform a large part of the sim "work", and a suspicion that ED's folk are aircraft experts, not DirectX gurus. Personally I can accept the FPS hit, since nothing else exists with an aircraft-fidelity even approaching that of DCS.

UltraMFCD, in accordance with "how MS wants these things to be done" stores your settings in the Users directory - specifically: C:\Users\<your Usernam>\AppData\Local\fe23\UltraMFCD.exe_StrongName_t3dncvaehh3oz0zfljdnyzwpfqbexf4k\<version>\user.config However, there's a much simpler method for resetting everything. Simply click the "Reset All" button from the settings screen. :)

That's really weird. Which version of Windows are you running?

P.S. how can you say"amazing. I rolled back the drivers and the FPS issue is completely gone. :O" if the exports aren't working?

Everything is OK until the USB screen is introduced? Isn't that indicative of the problem at large?

No idea why those drivers are borked. uMFCD is 100% textbook DirectX 3D, so why???? History: Way back in the past, Rick Rashid decided to engage in a personal project with a view to learning DirectX. What resulted was ultimately Microsoft Allegiance, and once source-released, FreeAllegiance. Having grown through FreeAllegiance, and implementing their ranking system, UltraMFCD was my re-learning DirectX.

No idea why those drivers are borked. uMFCD is 100% textbook DirectX 3D, so why????

Are you running nVidia's latest drivers, perchance? See "nVidia's latest graphics drivers (352.86) cause extreme lag/low FPS for exported displays. The problem with this particular driver set has been noticed to manifest with a number of games, not solely UltraMFCD. We will be monitoring the situation closely. If this issue affects you, rolling back to the previous driver (347.52) will resolve the problem until nVidia releases a patch for the latest driver." from ultramfcd.com :)

"I hope it would start a small revolution as to how virtual fliers experience the whole thing." My name is Sgt Baker and I fully endorse this product. :)

At some point in the relatively near future, I will be able to provide full avionics support. :)

Firstly, yes, the optimal solution is exactly that you're suggesting: DCS on three screens and displays on whatever else is connected. You should experience an increase in FPS as a result. However, the USB screen might be your undoing for the following reason: USB screens tend not to be hardware accelerated. UltraMFCD is 100% DirectX and operates a bandwidth of appx. 4Gb/s when running at full-whack (both MFCDs at full size), which is significantly more than can be crammed through a USB port. Some users have reported issues, others say everything works fine, so I suppose it depends on the USB screen in question. That said, you can adjust both the size and FPS of UltraMFCD's displays in real-time should you run in to issues. Please let me know how you get along, as this (USB displays) is an active field of interest at the moment. Regards, Baker

Absolutely. I have a policy of attempting not to tread on the toes of other mods (f.ex uMFCD works alongside Helios and DCS Bios), but haven't got around to testing uMFCD with Kneeboard Builder yet. The rationale behind releasing a kneeboard module was that uMFCD caused the standard kneeboard to disappear completely, as Rivvern would remind me at every opportunity. :)

You're not wrong there. Will aim to make this happen by the next release.

When the georeferencing is done, it's a relatively trivial matter to overlay them on to a mapping system of wider scope. ;)+;)+nudge+nudge The complexity arises out of where precisely the moving map data would be sourced. The A-10C module comes with a full pack of aviation charts, which are used for the TAD. The KA-50 ABRIS operates on some form of vector data, which is similar if not identical to the F-10 view. My concern is that distributing either set (preferably the A-10C's as they're the read deal) would clearly violate a raft of copyrights held by ED.

Sorry, I literally misread that. God knows where my brain was at that moment! :D The ownship business is partially complete. Code is already working behind the scenes of the latest release. What needs to be done is manually define the lat/long bounds of all the charts - a tedious process at best if done properly. :)