Sizing of MFCD's to fit Cougar MFD's in A10c

[MustangSally]

Hi all,

 

I have a 19" monitor that I display the left and right MFCD's on. The res is 1280 x 1024. The question is, how do I size them to fit nicely within the Cougar MFD frames?? My monitor setup is as follows....

 

_ = function(p) return p; end;

name = _('Phills 2 Screen');

Description = 'Two Monitor Configuration'

Viewports =

{

Center =

{

x = 0;

y = 0;

width = 1920;

height = 1080;

viewDx = 0;

viewDy = 0;

aspect = 1.6;

}

}

 

LEFT_MFCD =

{

x = 2015;

y = 595;

width = 360;

height = 370;

}

 

RIGHT_MFCD =

{

x = 2705;

y = 595;

width = 360;

height = 370;

}

 

UIMainView = Viewports.Center

 

The horizontal buttons line up nicely but the verticals are about 3/4 of a button out!! If I resize the height then the horizontal labels dissappear.

 

Any ideas?

Edited May 20, 2011 by MustangSally

[Succellus]

Seek the cockpit builder thread, there s a lot of answears.

There s also HELIOS from SCsimulation.

[PeterP]

Everything you need is in this preconfigured files with a detailed explanation and a pixelguide to measure the MFD's directly on screen.

http://files.digitalcombatsimulator.com/en/38323/

[MustangSally]

Everything you need is in this preconfigured files with a detailed explanation and a pixelguide to measure the MFD's directly on screen.

http://files.digitalcombatsimulator.com/en/38323/

 

Thanks Peter, Just what I was looking for.

[Loz]

The Easy Monitor Configurator by Icemaker here

takes all the guesswork out of it. A brilliant piece of work.

[pcalvert]

It's easy to do it the other way i.e. through the lua file.. Mine are set at 410 - fit perfectly... see here

 

http://forums.eagle.ru/showthread.php?t=70880&page=2

[Loz]

Yea but don't you realise that 410 pixels will only fit the TM MFCDs with a monitor using not just the same resolution but also the same overall screen size. He has a 19" monitor with a res of 1280x1024. Is yours exactly the same??

By the way it would be nice if it was in your sig.

[cichlidfan]

Everything you need is in this preconfigured files with a detailed explanation and a pixelguide to measure the MFD's directly on screen.

 

I was kind of wondering the same thing. Like how do you make a pixelguide that knows the pitch of my monitor. Personally I just measured the monitor (horizontally), calculated the pitch, measured the MFD, did the math...presto...all done.

 

375 pixels on my 22inch 1680x1050 monitor.

[Loz]

Exactly my point. Mine are 373 on my 23 inch 1920x1080 monitor.

The good thing about Icemaker's Config tool is that you just drag and pull to fit and then when you save it automatically, it puts it into the Config.lua for you.

It also does that for the other MCFD, the CDU, the CMSP, the CMSC, the RWR, the UHF Frequency, the UHF Repeater, the UHF Preset Channel and the Digital Clock if you want. Saves a heck of a lot of fiddling around especially with HELIOS. I say again, a marvelous utility.

[MustangSally]

Thanks guys,

 

I have PM'd Peter but I'll ask here as well. The problem is not the position or overall size, it's the line up of the vertical button labels on the MFCD to the Cougar MFD's.

 

The horizonatals are fine but the verticals are out by approx 5mm.

 

Any ideas?

[cichlidfan]

Thanks guys,

The horizonatals are fine but the verticals are out by approx 5mm.

 

Any ideas?

 

That is the nature of the image. Perhaps it still matches reality perhaps not but that is not something you are going to fix without distorting the entire image.

 

I know what you are talking about. Mine are the same way but I really don't pay any attention to it. I still can tell which text goes with each button.

[MustangSally]

That is the nature of the image. Perhaps it still matches reality perhaps not but that is not something you are going to fix without distorting the entire image.

 

I know what you are talking about. Mine are the same way but I really don't pay any attention to it. I still can tell which text goes with each button.

 

Thanks mate, had a funny feeling that this was the issue.