Sgt_Baker

Perhaps I made a mistake. Just fixed that for users who implement the "Display Scaling" option in Windows. There's a possibility that something relating to that slipped through. Will look in to it. --Baker

To utilise a joke a lawyer once made: Major_Baker (Special Bread Service)

Will promote 2.6.7 to release build if nobody has any objections...

This has gotta be some kind of patch lap record. Fixed in latest build. Head over to http://forum.ultramfcd.com/posts/m341-UltraMFCD-2-6-7#post341 :)

Yup, you're quite right. Seems the shift-hold code was never ported over to the KA-50 displays. Will patch that ASAP. --Baker

Yeah. I have a long history in the 3D/VR area, primarily with the high-end military grade user in mind. The irritatingly low resolution is precisely what puts me off purchasing a VR headset. :)

@Gunnergolly Then again, follow the instructions for creating a diagnostics package. There might be some clues in there.

Hi Gunnergolly, Unfortunately the Diagnostics Package function doesn't interrogate low-level DirectX stuff as that in and of itself would kill performance. It can, of course - something active on this end - but completely inappropriate for public release. It does, however, sound like there some utility/mod/malfeasance or the other on your system which is permanently meddling with DirectX rendering. Things too look our for are screen-capture programmes, visual-enhancement stuff (SweetFX etc), DirectX DLLs sitting anywhere in DCS's folder system... Does this happen with all games or just DCS? --Baker

Location: Sweden... Sweden... Sweden.... MY GOD HE COULD MEAN ANYTHING!

No worries. Just making sure nobody wanders off and spends $30 on something they can't actually use. :)

That's for Microsoft's FSX, NOT DCS!

It doesn't at the moment, although VR support is planned for the future. --Baker

This is in the works, yes. However in a recent vote on Twitter, the unwashed masses voted overwhelmingly for adding support for additional aircraft over networking functionality. It will be introduced in the not too distant future, though. --Baker

Please follow the instructions here: http://forum.ultramfcd.com/posts/t1-HOWTO---Submit-a-bug-report---PLEASE-READ-BEFORE-POSTING --Baker

Hi Gunnergolly, Two things: 1) Attempt running with V-sync disabled. 2) Try the latest beta from here. There are some changes in there which potentially have a great effect on FPS. --Baker

Understood and appreciated. --Baker

Hi SiThSpAwN, I've been flying much more recently (as opposed to doing software stuff) and can confirm that the assertions made in this thread are indeed very much to the point. The first indication I received that there might be a problem was UltraMFCD users saying (more or less a direct average-quote) "Thanks for the update, but I'm not going to be flying until they fix the FLIR problem". Of course, I take these comments with as much a pinch of salt as you do. It wasn't until I started flying missions again that the extent and severity of the problem became apparent. FLIR systems are now so impaired that night flying is impractical for all but the most experienced users. In my personal experience the difference is, no pun intended, like night and day. I'm more than happy to provide screenshots/slides to support the overall assertion should that be required. What my request would be is the following: Perhaps this could be elevated from "Request for improvement" status to "There is a real bug" status? Or some such. This is, of course, my diplomatic tuppence, but I think a point of concern should be that people are avoiding the software as a whole until the problem is resolved. Best regards, Baker

Here ya go: http://forum.ultramfcd.com/posts/m322-UltraMFCD-2-6-6#post322 --Baker

Hi Neal, Sounds like something interesting is going on. One thing I can say for certain is that uMFCD doesn't change anything at all on your PC or within your DCS install. It's completely dynamic: Does its thing while it is running, when not running it's like it was never there. Just to get this straight, are you still attempting to use uMFCD, or is this a lingering problem that is unrelated? My initial suggestion (whether running uMFCD or otherwise) with complex display setups is to take DCS back to a clean install and reintroduce mods gradually. If you are still using uMFCD, you can get rid of the PeterP exports stuff, as it isn't required when using UltraMFCD. --Baker

As it so happens, Sgt Pancake, I'm endeavouring to introduce VR/HMD features to UltraMFCD - one of which would be a more fine-grained control over the manner in which labels are rendered. Full disclosure: uMFCD presently breaks the label system. That said, you quickly become used to flying without that type of support. ALSO: Have a look at the DCS options screen. There are a few new things in there such as "Model Enlargement" and "VR Pixel Density", which I believe attempt to address the low-res problems with the current generation of VR devices. --Baker

Можете ли вы быть более конкретным, пожалуйста? Что происходит? Есть ли сбой это? :) --Baker

I'm going to perform a bunch more testing, but may have a patched release ready as early as tomorrow. --Baker Edit: I also got rid of a bunch of legacy code which, if I'm not mistaken, has given an additional boost to the smoothness of the exports' FPS. The problem is that once you've spent too long looking at things, your eyes start to play tricks, so your (all) feedback is welcome on that front.

@fenmonster: Problem solved on this end. DirectX shenanigans with instructions executing out-of-order or at random/arbitrary times.

Hi Fenmonster, Looking in to this as we speak. Seems to be one of those intermittent issues, but am able to sporadically reproduce on this end. Will let you know more after some testing... --Baker

So, as an FYI, the wheels are now turning with a view to introducing support for the Mirage, Viggen, Mig-21, Gazelle etc. :)