Loophole Posted October 5, 2019 Share Posted October 5, 2019 Because of the new way the MFD viewports are being handled, it seems to no longer be possible to redirect them to a custom viewport - they can only be displayed in "LEFT_MFCD" and "RIGHT_MFCD". This is a problem when you are flying multiple aircraft that use LEFT_MFCD and RIGHT_MFCD, but have displays that need to be in different locations or of different sizes. The most obvious culprit here is the Su-25T, which has a 4:3 aspect ratio RIGHT_MFCD. All of the previous non-FC3 aircraft could be configured to look for a custom aircraft-specific viewport, and fall back to using LEFT_MFCD and RIGHT_MFCD if a custom viewport was not defined. That approach no longer works with the new mechanism implemented for the F-16C: Under the previous system, this would have worked: --ViewportHandling dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") update_screenspace_diplacement(1, true, 0) try_find_assigned_viewport("LEFT_MFCD_F16", "LEFT_MFCD") On a side issue, if you change the "USE_LCD_MFD" setting, then the above *kind* of works - the custom exports *do* appear, but totally fuzzed-out and unusable, and the standard LEFT_MFCD and RIGHT_MFCD viewports are also still displayed as well. It would be great if they adopted a standard of including the calls to check for both an aircraft-specific viewport, and (where appropriate) a generic viewport for every exportable display - would save me a lot of editing after each upgrade! :-) Link to comment Share on other sites More sharing options...
Animal451 Posted October 17, 2019 Share Posted October 17, 2019 I couldn’t agree more, hopefully they change the export name to match the aircraft. ASUS Strix Z370-E, i7 8700k @ 5 GHz, ASUS Strix GTX 1080 TI, 32GB G.Skill Ripjaws V DDR4 3200 MHz, Corsair H100i, WD 1TB SSD Link to comment Share on other sites More sharing options...
Recommended Posts