Even though I'm not going to use this until the FPS hit is gone, I could not resist testing it with the kneeboard.Some things that struck me is that the "VFR" maps ar not present and no kneeboard key commands work.Meaning it can not be used for navigation really.Also, pressing RShift+K brings up the original (but distorted) kneeboard over the ABRIS, "VFR" maps are present and key commands work on that.

If you could make the "VFR" maps and key commands to work in the exported display, maybe you could make it work in other aircrafts without GNSS equipment, like the UH-1H and MI-8?

Another thing that would be good to have is to make the active display on top of the others. As it is now for the KA-50, ABRIS is always the uppermost, kneeboard lowest and SHKVAL in the middle, despite what display I would like to focus on.

All good points. There are a couple of reasons why I'm running a custom kneeboard.

1) Historically it was a royal pain to get the built-in kneeboard to behave properly when uMFCD was doing its thing. With recent updates this is no longer an issue, except for not having fixed the obvious problems yet.

2) There will be a number of custom (and flashy) displays in the future. As you've suggested, GNSS for all aircraft is one of them. A bit (lot) like a modern Garmin, if you will. At that point all the charts and VFR stuff will integrate in to those displays. The current kneeboard was the first little foray down that path.

Speaking of which, and your being a KA-50 pilot, I'm looking to include the Ekran, nav panel, warning lights etc as exports in the near future.

There's some new core code in the latest internal beta (2.5.7) which attempts to address the obvious potential reasons for the FPS hit, but I'm not really seeing the improvements I had hoped for on this end.

What was your hardware setup again? And do you mind being the go-to FPS guinea pig? Have developed a repeatable test procedure, you see. In fact, it's exactly that test procedure from which the Las Vegas images on the front page of the uMFCD were captured. Obviously no good unless you have NTTR, but I can easily create something similar for 1.5.5.

So there is already major headway. It's getting to the point where it's difficult to determine where the bottleneck is. It's worth noting that uMFCD renders the displays in much, much higher quality than DCS does by default. I use uMFCD's "HD" setting here. You could try "SD" to see whether that helps.

Good to see an improvement in FPS, but on my setup it's a much bigger difference between with or without uMFCD, around 10-20FPS. A nogo for me.

I can try to be your guinea pig for a while, but I haven't as much time to spare as I like to, and can't promise frequent and timely testing, can pass days between sessions.Do you run a certain mission?Are the demanded settings still valid?

I believe I forgot to mention I only run DCSW 1.5 and only helicopters.

Right. In simple terms your GFX card memory (2GB) is likely the problem here. In recent times I've observed an increasing tendency for DCS to consume far more video ram than is available. I currently have a card with 3GB of RAM, yet DCS wants 9GB under the Sphinx test scenario. The net result is that the GFX drivers start to use conventional RAM as a backup for lack of RAM local to the GFX card, and all sorts of weird back-and-forth between Gfx and CPU RAM starts to take place over the PCIe bus (very slow). Performance crashes as a result.

Adding uMFCD to that mix certainly won't help.

And particularly now that DCS 1.5.5 and 2.0.4 are using the same rendering engine, there's no way around this.

Seems ED are hedging on the future-of-massive-gfx-memory and not the now.

And DCS doesn't take advantage of SLI what I know either, so no use of my second card.Will be a while until economy (i.e. wife) permits an upgrade. So I guess I'm not of much use her as a guinea pig due to outdated hardware, you can do as much optimization as you possibly can but it won't help me much, but hopefully others.

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.