hawk2495 Posted January 6, 2019 Posted January 6, 2019 (edited) Alright. So I just decided to start messing with exporting the DDIs and AMPCD in the Hornet. My current configuration is one 55" 1920x1080 TV as my primary. One 27" 1920x1080 to the right, and one 27" below the main. I've got a decent monitor setup file that does what I want, but I found something interesting. If I run my setup in 3840x1080 with the MFDs exported to my right screen, the displays match up with the displays in the sim. Messing with the stroke thickness and fuzziness produces consistent results between the main and the exports. So that's good. Now, when I run it in 1920x2160, with the exports on my bottom monitor. The lines are double the thickness and fuzzy as hell. I can make them look good with tweaks, but at the cost of not being able to read my HUD. Has anyone else noticed this rather odd difference in output? My luas... This one works perfectly with the 3840x1080 _ = function(p) return p; end; name = _('Monitor3'); Description = 'One monitor with 3 MFD on second screen configuration' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1920/1080; } } Gui = { x = 0; y = 0; width = 1920; height = 1080; } LEFT_MFCD = { x = 1920 + 73; y = 5; width = 530; height = 530; } RIGHT_MFCD = { x = 1920 + 676; y = 5; width = 530; height = 530; } CENTER_MFCD = { x = 1920 + 275; y = 540; width = 530; height = 530; } UIMainView = Gui This one gives me the blurry images in 1920x2160 _ = function(p) return p; end; name = _('1 Screen + 3 MFD on second screen'); Description = 'One monitor with 3 MFD on second screen configuration' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1920/1080; } } Gui = { x = 0; y = 0; width = 1920; height = 1080; } LEFT_MFCD = { x = 0; y = 1080 + 10; width = 530; height = 530; } RIGHT_MFCD = { x = 1390; y = 1080 + 60; width = 360; height = 360; } CENTER_MFCD = { x = 695; y = 1080 + 500; width = 530; height = 530; } UIMainView = Gui I'll attach some screens for comparison. What do you guys think? Edited January 6, 2019 by hawk2495 Why is the rum always gone!?!?!?!
Naruto Posted January 6, 2019 Posted January 6, 2019 That's just how it works at the moment, you have to play with the MDG_strokesDefs settings. I found a good compromise with these setting: stroke_thickness = 0.4 stroke_fuzziness = 0.4 -- Currently is used for DMC generated fonts black outline DMC_outline_thickness = stroke_thickness * 3 DMC_outline_fuzziness = stroke_fuzziness * 1.1 DMC_stroke_thickness = 0.35 DMC_stroke_fuzziness = 0.3 System specs: Intel i9-9900k OC 5.1Ghz, 32 GB PC3200 G.SKILL TridentZ RGB RAM, Asus Strix 2080 TI OC SLI, Asus Z390 Workstation Pro, 970 EVO 1TB M.2 PCIe NVMe and many other SSDs, Alienware 3418DW Widescreen 120 Hz G-Sync Monitor, Corsair H150i PRO RGB CPU Cooler Flightgear: HP Reverb Pro, Samsung Odyssey +, Virpil MongoosT-50CM2 Grip & T-50CM2 Base, TM Warthog, TM TPR Rudder, TM Cougar MFDs, Jetseat, Trackir 5, Sennheiser Game One Headset
Thermal Posted January 6, 2019 Posted January 6, 2019 Nice work finding that out. Certainly seems like a bug.
hawk2495 Posted January 6, 2019 Author Posted January 6, 2019 Yeah.. It just doesn't make any sense to me as to why one configuration works perfectly and the other doesn't. It's essentially the same thing just rendering in a different direction.. Oh well. I did find a workaround that's kind of annoying, but works. I just configured it for 3840x1080 and moved my right monitor below my main in windows display config. Works well, even if I have to jump through some hoops to get my cursor on the correct screen. lol Why is the rum always gone!?!?!?!
hansangb Posted January 7, 2019 Posted January 7, 2019 On the fuzzy setup's Rifght MFCD, , did you mean to use "width 360" hsb HW Spec in Spoiler --- i7-10700K Direct-To-Die/OC'ed to 5.1GHz, MSI Z490 MB, 32GB DDR4 3200MHz, EVGA 2080 Ti FTW3, NVMe+SSD, Win 10 x64 Pro, MFG, Warthog, TM MFDs, Komodo Huey set, Rverbe G1
hawk2495 Posted January 8, 2019 Author Posted January 8, 2019 I did. I was in the process of sizing them down to fit into my Cougar MFDs. The stroke settings were default for this test though. Why is the rum always gone!?!?!?!
Recommended Posts