MULTIMONITOR T SHAPE (4 DISPLAYS) - HELIOS + DCS 3 CAMERA FRANKENSTEIN COMBO

[HAL_9000_PsycoPC]

 Am rather new to DCS but can't cope with my tinkering inclinations (see my systems specs in my signature). Have a 4 screen T shape setup with the following specs.

Please disregard the 2520 in the 7680x2520 Resolution as it did not come into play when using my initial 3 camera (7680x1440) setup.

Started using a plain vanilla DCS 3 Camera (7680x1440) view (pic 1) but missed the cockpit info provided by Helios.

PIC 1 "3 camera" view

So I moved into Helios (pic 2). Problem being: Helios starts rendering the pilot position way too far forward and it also distorts the HUD (because of the FOV it assumes I have based on being 1 giant 7560x2520 T shape display)

PIC 2 Helios view -  with far forward pilot position and distorted HUD

So after tinkering for a while and facing the expedient of recognizing myself as a complete idiot for not being able to adjust Helios' FOV (solving the pilot position and HUD distortion problems) I decided to move into a Frankenstein by using a 3 camera 7680x2520 view ALONG with a stand-alone Helios (see pic 3 below).  Now the problem is that the RMFCD does not renders at all.

PIC 3 with 3 separate cameras and Helios running along (outside of DCS) as per CaptZeen instructions. Everything works fine but (lovely FOV, 3 separate cameras, nice HUD, nice Helios info) BUT the RMFCD does not render at all, as you can see in the pic below.

Went through most of the posts here provided by CaptZeen, @jonsky7, @klem, @Hiob, @hansangb, @draconus, @MAXsenna and other good fellas out here but could find no solution to this problem. Any thoughts on why the RMFCD might not render when using my "3ScreenF18f.lua" profile in DCS along with Helios outside of DCS?

Am including below a detail of my .lua file in DCS in case it could be of any help (edited w Notepad ++)

_  = function(p) return p; end;
name = _('3ScreenF18f')
Description = 'Configuration with 3 identical monitors each with its own camera'
Viewports = 
{
     Left = 
     {
          x = 0;
          y = 0;
          width = 2560;
          height = 1440;
          viewDx = -1;
          viewDy = 0;
          aspect = 1.7777;
     },

     Center = 
     {
          x = 2561;
          y = 0;
          width = 2560;
          height = 1440;
          viewDx = 0;
          viewDy = 0;
          aspect = 1.7777;
     },

     Right = 
     {
          x = 5121;
          y = 0;
          width = 2560;
          height = 1440;
          viewDx = 1;
          viewDy = 0;
          aspect = 1.7777;
     }
}

FA_18C_CENTER_MFCD =
{
x = 3593;
y = 2136;
width = 363;
height = 344;
}

FA_18C_IFEI =
{
x = 2969;
y = 2193;
width = 526;
height = 205;
}

FA_18C_LEFT_MFCD =
{
x = 3095;
y = 1640;
width = 391;
height = 369;
}

FA_18C_RIGHT_MFCD =
{
x = 4074;
y = 1640;
width = 389;
eight = 367;
}

FA_18C_RWR =
{
x = 4308;
y = 2160;
width = 182;
height = 182;
}

FA_18C_UFC =
{
x = 3556;
y = 1471;
width = 457;
height = 259;
}

UIMainView = Viewports.Center
GU_MAIN_VIEWPORT = Viewports.Center

--[[
also you can use "displays" table  to perfectly match you configuration .
it is generated by DCS automatically.
displays table is contains information about all currently attached displays 

for example my setup is :

displays = 
{
    [1] = 
    {
        x = 0,   -- note : x == 0 and y == 0 is always mark primary windows display 
        y = 0,
        width  = 1920,
        height = 1200
    },
    [2] = 
    {
        x = -1440,   -- mark that secondary display is on left side of primary display
        y = 0,
        width  = 1440,
        height = 900
    },
    ...  for all displays 
}

screen table also contain x, y members which mark top left corner of DCS window 

note about fullscreen :  directx  doesn't allow fullscreen applications with resolutions more than primary display can handle,
so multimonitor presets in DCS will fall back to windowed mode if fullscreen initialization failed  ( this info also will be printed to dcs.log)

for reconfigure viewports setup for each unit type independently you can declare here function 

function  reconfigure_for_unit(unit_type)   --unit type is string with unit name
    if unit_type == "A-10C" then
          
        Viewports  = ... define new Viewports table 
        -- also you can define cockpit displays viewports here 
        RIGHT_MFCD = ... define new RIGHT_MFCD  viewport 
          
    else 
        Viewports = ... define default for others 
        RIGHT_MFCD = nil  -- remove for others 
    end
end

--]]

Also, am including a detail of my Helios frofile (again, running outside of DCS) just clarification purposes:

 

_  = function(p) return p end
name = _('Helios')
description = 'Generated from compatible Helios Profiles'
FA_18C_CENTER_MFCD = { x = 3593, y = 2136, width = 363, height = 344 }
FA_18C_IFEI = { x = 2969, y = 2193, width = 526, height = 205 }
FA_18C_LEFT_MFCD = { x = 3095, y = 1640, width = 391, height = 369 }
FA_18C_RIGHT_MFCD = { x = 4074, y = 1640, width = 389, height = 367 }
FA_18C_RWR = { x = 4308, y = 2160, width = 182, height = 182 }
FA_18C_UFC = { x = 3556, y = 1471, width = 457, height = 259 }
Viewports = {
  Center = {
    x = 0,
    y = 0,
    width = 7680,
    height = 1440,
    aspect = 5.33333333333333,
    dx = 0,
    dy = 0
  }
}
UI = { x = 2560, y = 0, width = 2560, height = 1440 }
UIMainView = UI
GU_MAIN_VIEWPORT = Viewports.Center

Thank you very much for any support you guys can provide.

 

Edited October 16, 2023 by HAL_9000_PsycoPC
typo

[draconus]

1 hour ago, HAL_9000_PsycoPC said:

eight = 367;

this

[HAL_9000_PsycoPC]

Thank you very much @draconus!!!!! Thank you Sir!!!!!