lxsapper

Do you guys think it's apropriate to PM Nineline and ask him to revisit this thread?

Hey Beamscanner, since you are going to look through the LUA, MDG_strokesDefs.lua seams to be interesting. I haven't tried messing with it, but it aparently is used to control the black outlines on the DDIs symbology. One of the things I can clearly notice on the bad visual setups is an increase in the black outline. Maybe Worth messing about with, might give more interesting results than the other more used "fix". Also noticed, and maybe this is closer to a real fix, that Common_page_defs.lua on Multipurpose_Display_Group\Common\indicator\ is using some GetScale Variable to set DDI font and Symbology scale. Don't know much about coding, but maybe that can point you in the right direction.

I'm trying to personalize and automatize the placement of the displays of all my aircraft. And as it stands FC3 aircraft export their displays to eighter LEFT_MFCD or RIGHT_MFCD. I need to change the display name to something else, almost per aircraft. But I can't find the apropriate init.lua's for this, or whereever this is defined. Can anyone point me in the right direction.

Like the Title says. THis is a problem only in multi-screen config. It was like this at launch. Had hoped that the Fix for the uncentered Jester UI, would also fix this when deployed. But it has not been so. So I'm reporting it here on it's own. And Here is a Video:

Just to further add to this, you don't have to have a dual glass to be able to focus on infinity. A lot of planes have single glass HUD.

If you use the manovering Flaps/Slats, you should be ok. They auto retract.

Actually I think the Damage model on the Slats/Flaps is fantastic. I had them get stuck in asymetric positions (from behing deployed beyond safe airspeed obviously) this sounds very mechanicaly feasible imho.

MVM just saw that you have several small screens in your cockpit. Will send you a PM later.

Hey Guppy, do you mind setting your monitor in windows to be side by side and setting your total resolution accordingly. if you don't want to create a monitorsetup file from scratch for that, you can use my automatic one I posted here: https://forums.eagle.ru/showthread.php?t=236279 Need more people confirming this only happens (or is agravated) is certain total res aspect ratios.

Just wanted to share with everyone a MonitorSetup file I came up with, based on others as well the automatic default ones and then giving them my own spin on it. I'm quite happy with this file and a bit chumped up about it, if I'm beeing honest. :D It's setup to work with two screens (it will also work with one, but output will be the same as the 1 Screen default file), it will display 3d graphics on 1st monitor and then it will take your second monitor and it will place the 3 MFDs (if your plane has them) acording to the following: - Left MFCD top left corner, with spacing for cougar MFDs and screen size adjusted for you monitor size and resolution. - Right MFCD top right corner, with spacing for cougar MFDs and screen size adjusted for you monitor size and resolution. - Center MFCD monitor center bottom, with spacing for cougar MFDs and screen size adjusted for you monitor size and resolution. It only requires two things, that you set your DCS resolution acording your screens that you want to use. And that you make a small edit in the file where you will input your screen diagonal size in Inches. And here is the Lua code for everyone who wants to give it a go: Small disclaimer, I don't actually own the Cougar MFDs, so measurements where taken from layouts avaiable online.

Apears to be tied to the aspect of the total resolution beeing used. See my screenshots in this thread please: https://forums.eagle.ru/showthread.php?t=226340 https://forums.eagle.ru/showpost.php?p=3844870&postcount=8 https://forums.eagle.ru/showpost.php?p=3848759&postcount=18

+1!

That's not what is beeing discussed here. They are talking about the logic of when a threat should be moved to the lethal band. Not if the Lethal band should be on the inside or outside of the RWR display.

Ok I can now confirm Beamscanner, is very much on to this. Here is the MFDs beeing exported in preaty much the same resolution (actually each display is about 4x4 pixels less, but that should not make much of a diference) but only using part of the second screen, in a vertical resolution. You can now see that, the displays are still considerably less readeable than in the side by side configuration, but still noticebly more readable than when using the whole screen. So this is defenitly tied to the total rate of x/y pixels.

I think you might be on to something. I had similar suspicions, will do some testing later today.

For reference my main monitor is 1920x1080 and the monitor with the MFDs is 1600x900. The resolution used was as per the screenshots: 3520x1080 and 1920x1980.

I did realize this has been discussed before. But because this thread is marked [CANNOT REPRODUCE] and nine line is posting in it apparently oblivious to the issue, I decided to post my findings here. Also because I'm not sure if someone had made the observation about the dife trencesbetween arrangements. This can also explain I think, why .some people don't observe the issue at all. The fix for me atm is using the monitors in windows side by side configuration, that doesn't have to mac the physical arrangement. This makes it somewhat awkward the monitors in windows, so a real fix by ED would be appreciated.

comparison images: It appears to be related to the black border surounding text and symbology.

Ok, I've been doing some multi-screen configurations and found that this problem apears when the export screen is in a vertical configuration. It makes no sence but on an horizontal configuration, the export screen is perfectly readable.

That's not necessarily the visual model that's incorrect. Might just be the amount the Shock absorver colapses, that is insuficient with weight on Wheels atm.

Actually it makes sence, since the HUD is colimated.

Was on a multi-player session last night. Took a Hornet for that one, my friend was in the Tomcat, we we parked right next to each other. His Tomcat sliding around. At one point near start up completion, his plane slid against mine. He lost his wing, I was undamaged.

Radar Altimeter Bit test - Green light not illuminating.

thanks, that is great to know.

saw it afterwords. Do you know if they are aware of the second issue. Not sure if they both will share the same fix.