Sgt_Baker

I couldn't disagree more. It does appear "difficult" to persons coming from a single-threaded background, yet once the shift in mindset is achieved the benefits outweigh the development overhead. Agreed. DX has, traditionally, FORCED a single-threaded relationship between code and gfx driver. Using the Multithreaded flag would result in the driver stalling while expecting instructions from multiple threads in a single-threaded fashion. This, I suppose, is what I'm getting at. If one considers any given problem from a parallel perspective, the cross-thread protocols are already "built in". It's much, MUCH more difficult to convert a system which was originally conceived as single-threaded.

Does Aries Radio System cover the same ground? Perhaps take a look at their stuff?

Regarding the last few, very interesting, posts: I often contemplate the relative lack of parallelism in games. Coming professionally from the exact opposite end of the spectrum (oodles of data, faster = bigger profit, plus a huge dose of R&D), one develops something of a "1000-core stare". During the development of UltraMFCD, solely for reasons of curiosity and having a nice source of 2GB/s of raw data, I developed a pixel shader which would encrypt the raw video streams coming out of DCS with a pseudo-OTP system. Even with both encryption and decryption of this absurd code-toy running in parallel with DCS, the sim's FPS only dropped by 20% when running on 2048 gfx cores. A very useful bit of research which will be used elsewhere. Now, this brings me to my principal question: Why has the games industry been so slow to adopt a parallel-coding paradigm? For an industry whose principal metrics include "FPS" ("do everything you're already doing, just faster"), one would have imagined they'd be a the front of the proverbial queue. The mind boggles. Regards, Baker

See: http://www.excessiveheadspace.com/tars/download/ There appears to be a new version. No idea whether it still works, mind. :) Baker

Hey Deezle, I've just had a look at this. The CDU export script is derived directly from the Helios script, which complicated the merging process quite a bit (they use the same function names, variable names etc). I'm having the week from hell at the moment - crazy busy - but if you've not got anywhere with this by the end of next week drop me a PM and I'll merge them for you. Regards, Baker

Hi Dan, Part of this question happens to be practically identical to one asked in the other thread earlier today. There's nothing at all technical preventing UltraMFCD from rendering mirrored and in aspect rations other than those preset in the current UI. So, it's something I'll enable in the very near future. As for LAN setups, it's something we've already done at the lab/R&D level. Will be a little while before it appears in the release-grade versions, since it'a feature that will be used by fewer users than the main functionality, but something that's already well underway. Regards, Baker

Hey Sage, Yes, this is something that has come up before. There is absolutely nothing technical enforcing the current aspect ratios other than the resize handle itself. It was designed like this to simply make resizing as easy as possible. The plan is to enable free-form aspects by shift-dragging the resize handle, or some such. No ETA, but it's a really simple alteration, so sooner rather than later. B

Thanks for the diag pack. I'll check it out over the next couple of days (external time obligations obligations, or it would be sooner). Right after I released initial support for the ABRIS and Shkval, I made fundamental changes to how uMFCD works with a view to making it much more reliable. Unfortunately I've not yet had time to propagate those changes to the two KA-50 displays. I imagine your problem will vanish once that happens. Great to confirm with a diag pack, though. :) Baker

Roger that. It's not high priority, but I will look in to preventing uMFCD from unintentionally overriding parts of the monitor setup it doesn't yet support. No problem with the clickspots - a very good idea. Baker

That's not enough to get UltraMFCD to pick up the display. If it is, then I've made a mistake somewhere. After all, do you want the Mig-21 radar with all the A-10C's buttons? ;) P.S. Please refrain from asking people to modify files in the only thread that's all about NOT having to do so. :)

Not yet, since I'm yet to purchase a copy of the Mig-21 module. It's not as simple as shoving a definition for RIGHT_MFCD in to a monitor config, you see. :)

Man, there were typos all over that post. This is what dealing with lawyers does to a person! :D Thanks for pointing it out.

UltraMFCD 1.0.0.60 is available for download at https://ultramfcd.com This is principally a stop-gap release while we deal a necessary yet long-winded process behind the scenes. New: A-10C CMSC

New and improved video in my sig for those of you who are unfamiliar with uMFCD. :)

Likewise. DCS 2.0 will enable some fundamental and rather positive changes to how UltraMFCD works too.

Not at the moment, but Helios supports the functionality you are after.

For now, yes. The original plan was to replicate all functionality in full-screen mode, yet that plan was active when the beast was a lot more simple than it is today. As it stands, the arguments for running in fullscreen a sufficiently limited that I can't honestly say that we will be implementing that mode, on account of the likely cost/benefit being out of whack. Out of interest, does DCS even support crossfire? I know that my 7970 comes nowhere near to running at 100% no matter what settings I choose, since the sim appears to be CPU-bound.

No worries. I've modified uMFCD so that it forces DCS in to windowed mode with a view to preventing this type of incident in the future. Thanks for letting us know that it wasn't immediately clear what was happening. :)

This is what beta tests are for, Joe. If this were happening with the paid version, I too would be a little concerned. Our principal problem has been attempting to transparently interact with instances of DCS that have already been hard-modified: I.e. the user has applied a bunch of changes at the file level, yet can't necessarily remember which files were changed, or how, let alone understand how those mods might have affected their system. In the mean time, you could really help us and the users of uMFCD at large by generating a diagnostics package of the crash. Instructions are available a few posts earlier in this thread. :) 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.

Don't worry. It's utterly clear that you're not going to be producing any of this :) :

x2 To what BitMaster says about standard HDDs. When you're in the business of purchasing them in bulk, you happen across a surprising number of failures. Incidentally, Google published some interesting material in this field a while back, which was based on their experience with HDDs in the gazillon servers they run.

Now this is a strange one. It would appear that communication between DCS and UltraMFCD is breaking down very early on. Not something we've seen before. Will have to investigate what might cause this prior to even contemplating a fix. Baker

I wasn't supposed to spark a debate as to whether lefties are catered for in aviation. This chap wants a high-quality stick that fits his preferred hands for things that generally have nothing to do with our hypersim world. He likes space sims. Thanks for the quick response, hegykc. :) Edit: +Throttle

This may have been asked previously, so apologies if we're going over the same ground. I have a friend who is interested in a high-end HOTAS setup (think TM Warthog), yet is a leftie. While discussing it earlier, I remembered seeing this thread a while back. What sort of costs might we be looking at for a left-handed conversion of a TM Warthog HOTAS or similar? Best regards, Baker

Yes, exactly that. What's more, you can still use uMFCD's features in tandem, so if you want the CDU on your main screen and the MFCDs on your iPad, then switch it around... that too will be entirely possible. You'll still have to purchase a copy of UltraMFCD, mind.