UltraMFCD - drag, resize and click display exports. Zero configuration.

[icemaker]

@G00dnight i don't have the Sabre and i have made some tests and the problem is form uMFCD side.

[Iku_CC]

Thanks for the report. This is actually one that I was semi-expecting. Without getting in to further nitty-gritty, when you say your displays are in "surround" mode, would that be the surround mode offered specifically by nVidia cards?

 

The screenies you posted are symptomatic of uMFCD literally half working, and I anticipated trouble with said "surround" technology.

 

Yep..I was meaning Nvidia Surround mode (3 monitors in surround mode and one separate as fourth monitor)..and glad to know that it was not nothing to do my "installation"..:). If you need future assistant from me (testing, files from my system etc)..just ask and I help..

Edited December 1, 2014 by Iku64

[G00dnight]

Floaty mouse issue is only on the screen with the MFCD's on it when it starts mf's on main float is on main, when I move mf's to 2nd screen the float is on 2nd screen but when i take cursor back to 1st screen it moves ok. if I put 1 mf on each the float is on both screens. hope this helps and perhaps Ice can confirm the same for him.

[McMicha]

Hello Sgt_Baker,

 

your uMFCD is a nice project.

 

i have a similar problem as Iku64, but a have not Nvidia Surrond or AMD Eyefinity active.

 

Key bindingin is not recognicing my keyboard and my settings are not saved.

I can't move MFCDs and they don't do anything if I push mouse button over them.

...

CDU and some other window just popup for few seconds...

[Sgt_Baker]

OK. First update to Beta1:

 

https://ultramfcd.com/Public-Beta-1

 

• Possible fix for "floating mouse" issue
  
• Added profiling to export mechanism to investigate FPS issues
  
• Added explicit message regarding DCS in fullscreen mode
  

 

Slow FPS: If your FPS is waaaaay off what would be expected, please copy/paste the output, which is generated once every 1,000 frames, from UltraMFCD's System Messages section to this thread along with a brief description of your system specs.

 

The following screenshot is taken from my system. The mean and median times have rocketed from ~3ms to ~9ms in response to recent modifications to various aspects of the rendering engine. This is clearly undesirable, so I would appreciate your posting times here in order to provide a baseline against which to measure improvements in this area.

 

 

B

[ddocg]

The following was with FPS at 1/5

 

Error loadng key bindings. Please try to clear and re-bind.

 

 

10760:Export times in (min/max/mean/median) 00:00:00.0115242 / 00:00:00.1179281 / 00:00:00.0525346 / 00:00:00.0549776

MemCopy in (min/max/mean/median) 00:00:00.0019165 / 00:00:00.0497396 / 00:00:00.0033484 / 00:00:00.0027851

 

10760:Export times in (min/max/mean/median) 00:00:00.0111621 / 00:00:00.1464801 / 00:00:00.0554926 / 00:00:00.0578058

MemCopy in (min/max/mean/median) 00:00:00.0018682 / 00:00:00.0492844 / 00:00:00.0030993 / 00:00:00.0027078

 

10760:Export times in (min/max/mean/median) 00:00:00.0114388 / 00:00:00.1331435 / 00:00:00.0558091 / 00:00:00.0583324

MemCopy in (min/max/mean/median) 00:00:00.0020099 / 00:00:00.0472853 / 00:00:00.0031250 / 00:00:00.0027248

 

10760:Export times in (min/max/mean/median) 00:00:00.0115989 / 00:00:00.1398162 / 00:00:00.0547023 / 00:00:00.0567335

MemCopy in (min/max/mean/median) 00:00:00.0019028 / 00:00:00.0499688 / 00:00:00.0032551 / 00:00:00.0027005

Edited December 2, 2014 by ddocg

[Sgt_Baker]

The following was with FPS at 1/5

...

 

Wow, yes. To quote one Jamie Hyneman: "Well there's ya problem!"

 

I've been looking at this issue very closely all day. Mean and Median values for Export Time are in the order of 5x what they should be under Full FPS.

 

Given there is such a huge difference between the Export times and the MemCopy times, I'm beginning to suspect that your gfx card isn't communicating with the rest of your machine properly. Would you mind terribly taking a look inside your machine to verify that your Radeon 290 is indeed connected to the bright yellow PCIe socket and none of the brown/black ones?

 

The reason I say this is that the difference between Export and MemCopy is almost exactly that which you would experience if the above were the case: The large black PCI socket on your motherboard is about 4 times slower than the yellow one.

 

Other that that, your system is evidently quite nippy indeed.

 

Edit: See the "Expansion slots" section of http://www.asus.com/uk/Motherboards/Z87K/specifications/

Edited December 2, 2014 by Sgt_Baker

[Sgt_Baker]

So I did some things...

 

Here's the difference between ~14.00UTC and ~16:30UTC:

 

[ddocg]

:music_whistling: Yellow socket you say.....:doh:

 

I'd never have known that, when I built the machine I vaguely remember there being a reason why I put it in the black socket, can't recall if it was from the instruction book or whether there was a potential clash with other hardware which doesn't make sense as it is now plugged into the Yellow PCIe socket.

 

And here are the results:

 

 

8908:Export times in (min/max/mean/median) 00:00:00.0041378 / 00:00:00.0283697 / 00:00:00.0099271 / 00:00:00.0096708

MemCopy in (min/max/mean/median) 00:00:00.0021779 / 00:00:00.0138918 / 00:00:00.0034448 / 00:00:00.0033172

 

8908:Export times in (min/max/mean/median) 00:00:00.0039923 / 00:00:00.0310108 / 00:00:00.0104761 / 00:00:00.0098356

MemCopy in (min/max/mean/median) 00:00:00.0020468 / 00:00:00.0058758 / 00:00:00.0030168 / 00:00:00.0029774

 

8908:Export times in (min/max/mean/median) 00:00:00.0039712 / 00:00:00.0275960 / 00:00:00.0092389 / 00:00:00.0088189

MemCopy in (min/max/mean/median) 00:00:00.0020503 / 00:00:00.0098497 / 00:00:00.0026864 / 00:00:00.0025965

 

8908:Export times in (min/max/mean/median) 00:00:00.0040245 / 00:00:00.0246127 / 00:00:00.0078886 / 00:00:00.0063184

MemCopy in (min/max/mean/median) 00:00:00.0020219 / 00:00:00.0085728 / 00:00:00.0025964 / 00:00:00.0024812

 

8908:Export times in (min/max/mean/median) 00:00:00.0039935 / 00:00:00.0289189 / 00:00:00.0079954 / 00:00:00.0065868

MemCopy in (min/max/mean/median) 00:00:00.0019841 / 00:00:00.0111764 / 00:00:00.0026126 / 00:00:00.0024917

 

 

It is running a lot smoother and returning fps between 29 and 35 though still has a slight stutter.

Edited December 2, 2014 by ddocg

[Sgt_Baker]

:music_whistling: Yellow socket you say.....:doh:

 

:)

 

And with the next update you'll experience the same 3x increase in uMFCD performance as per my previous post.

[ddocg]

Looking forward to it, as things stand the remaining stutter is only noticeable when looking down left or right. Looking straight ahead I can't perceive the stutter on the horizon.

[rajdary]

Keep going, your Mod looks fantastic!

[G00dnight]

Great the floaty mouse has gone..

the CDU works on 2nd screen with mouse clicks lovely I don't use touchscreen and I have cougar MFD's.

so your getting there, don't want to be pushy but how long to get it saving between missions as it's a pain when I test something and restart over and over.

Great work so far keep it coming.

 

PS...the colour pod Pic is brilliant..so much easier to pick out targets.

Edited December 2, 2014 by G00dnight

[Sgt_Baker]

Another Update

 

Update 2 is here: https://ultramfcd.com/Public-Beta-1

 

Changes:

 

• MFCDs now remember their sizes and positions between sessions. All other options are also saved.
  
• Significant frame rate improvements
  
• "Enable MFCD input" (previously "Touchscreen MFCDs") now works as expected. Note: The graphical buttons will still be visibe - this will be addressed in a future update. If you have trouble with your Export.lua not functioning corectly with UltraMFCD, please disable this option. If your Export.lua works with this option disabled, please get in touch as we're keen to have UltraMFCD work no matter what your Exports might be doing. :)
  

[Sgt_Baker]

P.S. I don't know whether I mentioned this previously, but double-clicking the CDU's display will show/hide the keyboard.

[ddocg]

Seems all I need now are some more 8" touchscreens :thumbup:

 

fps is reporting steady at 32 with one dip down to 22. where i reported previously of there being a stutter at what is best described as the quarterlights, this is now gone or at least to me it is not noticeable it now appears very smooth.

 

FWIW the cdu opens with the keyboard visible though, double clicking does indeed close the keyboard however i would look to place the cdu on its own 10" touchscreen in portrait view if possible?

 

Positions are also remembered even after closing both dcsw and umfcd then opening back up, i have the left mfcd on my external monitor and it re-appears there after closing re-opening.....wonderful stuff.

 

Just need to get a job now to pay for the new monitors i now need!

 

Here are the system messages\timings:

 

Error loadng key bindings. Please try to clear and re-bind.

 

 

11164:Export times in (min/max/mean/median) 00:00:00.0037148 / 00:00:00.0207614 / 00:00:00.0058595 / 00:00:00.0051826

MemCopy in (min/max/mean/median) 00:00:00.0021791 / 00:00:00.0073801 / 00:00:00.0033445 / 00:00:00.0032648

 

11164:Export times in (min/max/mean/median) 00:00:00.0036870 / 00:00:00.0181236 / 00:00:00.0061696 / 00:00:00.0057399

MemCopy in (min/max/mean/median) 00:00:00.0022148 / 00:00:00.0075435 / 00:00:00.0033629 / 00:00:00.0032470

 

11164:Export times in (min/max/mean/median) 00:00:00.0036846 / 00:00:00.0199110 / 00:00:00.0067517 / 00:00:00.0065069

MemCopy in (min/max/mean/median) 00:00:00.0018266 / 00:00:00.0057795 / 00:00:00.0028449 / 00:00:00.0028038

 

11164:Export times in (min/max/mean/median) 00:00:00.0034926 / 00:00:00.0208876 / 00:00:00.0070210 / 00:00:00.0066023

MemCopy in (min/max/mean/median) 00:00:00.0018457 / 00:00:00.0050192 / 00:00:00.0026436 / 00:00:00.0026293

 

11164:Export times in (min/max/mean/median) 00:00:00.0035655 / 00:00:00.0196610 / 00:00:00.0061241 / 00:00:00.0055927

MemCopy in (min/max/mean/median) 00:00:00.0018401 / 00:00:00.0043371 / 00:00:00.0025664 / 00:00:00.0025699

 

11164:Export times in (min/max/mean/median) 00:00:00.0035529 / 00:00:00.0167275 / 00:00:00.0057350 / 00:00:00.0051223

MemCopy in (min/max/mean/median) 00:00:00.0017906 / 00:00:00.0039575 / 00:00:00.0025445 / 00:00:00.0025157

 

11164:Export times in (min/max/mean/median) 00:00:00.0036691 / 00:00:00.0116641 / 00:00:00.0059932 / 00:00:00.0058052

MemCopy in (min/max/mean/median) 00:00:00.0018222 / 00:00:00.0049624 / 00:00:00.0026031 / 00:00:00.0026088

 

11164:Export times in (min/max/mean/median) 00:00:00.0034733 / 00:00:00.0119170 / 00:00:00.0071591 / 00:00:00.0075128

MemCopy in (min/max/mean/median) 00:00:00.0018729 / 00:00:00.0055863 / 00:00:00.0026582 / 00:00:00.0026387

 

11164:Export times in (min/max/mean/median) 00:00:00.0038325 / 00:00:00.0123265 / 00:00:00.0074978 / 00:00:00.0077168

MemCopy in (min/max/mean/median) 00:00:00.0018752 / 00:00:00.0059308 / 00:00:00.0027237 / 00:00:00.0027192

 

11164:Export times in (min/max/mean/median) 00:00:00.0037277 / 00:00:00.0122381 / 00:00:00.0077396 / 00:00:00.0080002

MemCopy in (min/max/mean/median) 00:00:00.0019267 / 00:00:00.0054703 / 00:00:00.0027315 / 00:00:00.0027209

 

11164:Export times in (min/max/mean/median) 00:00:00.0036299 / 00:00:00.0190009 / 00:00:00.0078720 / 00:00:00.0080520

MemCopy in (min/max/mean/median) 00:00:00.0018457 / 00:00:00.0060166 / 00:00:00.0027406 / 00:00:00.0027037

 

11164:Export times in (min/max/mean/median) 00:00:00.0041150 / 00:00:00.0133725 / 00:00:00.0078796 / 00:00:00.0080672

MemCopy in (min/max/mean/median) 00:00:00.0018732 / 00:00:00.0053368 / 00:00:00.0026335 / 00:00:00.0026018

 

11164:Export times in (min/max/mean/median) 00:00:00.0036609 / 00:00:00.0128151 / 00:00:00.0076584 / 00:00:00.0078980

MemCopy in (min/max/mean/median) 00:00:00.0018767 / 00:00:00.0062677 / 00:00:00.0027528 / 00:00:00.0027236

 

11164:Export times in (min/max/mean/median) 00:00:00.0036978 / 00:00:00.0137214 / 00:00:00.0077147 / 00:00:00.0079325

MemCopy in (min/max/mean/median) 00:00:00.0018530 / 00:00:00.0068412 / 00:00:00.0027866 / 00:00:00.0027066

 

11164:Export times in (min/max/mean/median) 00:00:00.0043609 / 00:00:00.0132554 / 00:00:00.0079827 / 00:00:00.0082352

MemCopy in (min/max/mean/median) 00:00:00.0018661 / 00:00:00.0159424 / 00:00:00.0027674 / 00:00:00.0027318

 

11164:Export times in (min/max/mean/median) 00:00:00.0041551 / 00:00:00.0138107 / 00:00:00.0080567 / 00:00:00.0082039

MemCopy in (min/max/mean/median) 00:00:00.0018679 / 00:00:00.0069463 / 00:00:00.0026938 / 00:00:00.0026542

 

11164:Export times in (min/max/mean/median) 00:00:00.0040895 / 00:00:00.0144737 / 00:00:00.0077832 / 00:00:00.0079764

MemCopy in (min/max/mean/median) 00:00:00.0018372 / 00:00:00.0067080 / 00:00:00.0025947 / 00:00:00.0025702

 

11164:Export times in (min/max/mean/median) 00:00:00.0040450 / 00:00:00.0216645 / 00:00:00.0076614 / 00:00:00.0078787

MemCopy in (min/max/mean/median) 00:00:00.0019057 / 00:00:00.0045757 / 00:00:00.0027160 / 00:00:00.0026911

 

Delighted with this update, you've outdone yourself again Mr Baker.

Edited December 4, 2014 by ddocg

[Sgt_Baker]

:)

 

FWIW the cdu opens with the keyboard visible though, double clicking does indeed close the keyboard however i would look to place the cdu on its own 10" touchscreen in portrait view if possible?

 

Yes, that should be possible. You mean you'd want me to render the CDU rotated 90deg one way or the other, right?

[ddocg]

No, you don't need to rotate at least I don't think you do. I put the cdu on my 8" touchscreen but before doing so, I was able to rotate the screen which allows the cdu to be shown in portrait view.

 

Where I am unsure is if this behaviour works with more than one touchscreen (where the touchscreen has its own applet to control orientation I don't know if each screen is independant of the applet or whether the applet controls all touchscreens)

 

Perhaps someone who has three touchscreens could test? one screen rotated through 90 degrees with the other two set as default view?

[Sgt_Baker]

The technical terminology for this is "showing off".

 

[Sgt_Baker]

Incidentally, I've just tracked down and squashed a huge crash. If uMFCD was crashing intermittently on launch, this should now be solved and the fix available in the next update.

[ddocg]

Now that is cool, confusing to me but, cool nonetheless.

 

regards the cdu and resizing, would it be possible to be able to resize the cdu both horizontally and vertically to allow it to fill the monitor? I understand this is not a good idea for the MFCD's as they are square however, the CDU being a rectangle it would be great to be able to fill the screen as opposed to resizing diagonally.

[Sgt_Baker]

Now that is cool, confusing to me but, cool nonetheless.

 

regards the cdu and resizing, would it be possible to be able to resize the cdu both horizontally and vertically to allow it to fill the monitor? I understand this is not a good idea for the MFCD's as they are square however, the CDU being a rectangle it would be great to be able to fill the screen as opposed to resizing diagonally.

 

That too is possible. In a certain sense it would make the CDU easier from a programming perspective.

[ddocg]

Hopefully you can implement it without too much hassle?

 

I'm currently searching for square touchscreens for the MFCD's though, I think I'll struggle finding them?

[Sgt_Baker]

Hopefully you can implement it without too much hassle?

 

I'm currently searching for square touchscreens for the MFCD's though, I think I'll struggle finding them?

 

Yeah, square screens are uncommon enough to be classed as special application. They exist, but will likely be rather expensive when compared to a 4:3 or 16:9 counterpart with similar features.

[Sgt_Baker]

Update 3 is available at the usual URL.

 

• Fixed intermittent crash of DCS on mission start.
  
• Keyboard binding now work properly.
  

 

B