Alt+F1 problem.

[Alphapex1]

I have two monitors.Then set LMFD+RMFD on the second screen.
When I use Alt+F1, CENTER_MFCD shows up in the middle of the two screens, 
How can I get CENTER_MFCD to show in the middle of the first screen?

This is my setup.

_  = function(p) return p; end;

name = _('2Cameras');

Description = '2Cameras'

Viewports =

{

     Center =

     {

          x = 0;

          y = 0;

          width  = 1920;

          height = 1080;

          viewDx = 0;

          viewDy = 0;

          aspect = screen.aspect / 2;

     }

}

 

LEFT_MFCD =

{

     x = 1920;

     y = 0;

     width = 960;

     height = 960;

}

 

RIGHT_MFCD =

{

     x = 2880;

     y = 0;

     width = 960;

     height = 960;

}

 

UIMainView = Viewports.Center

GROUND_MAIN_VIEWPORT = Viewports.Center

Edited January 16, 2024 by Alphapex1

[MAXsenna]

@MadKreator @jonsky7 @lesthegrngo On my cell so it's hard to search. How did you guys solve this in the A-10s?

Sent from my SM-A536B using Tapatalk

[lesthegrngo]

please let us know the complete layout of your monitors, total pixel width and height, number of monitors, position and resolution of each. We need that to look at what is happening, as it will show us where things should be being displayed. Let us know if you need help on that

Cheers

Les

[MadKreator]

8 hours ago, MAXsenna said:

@MadKreator @jonsky7 @lesthegrngo On my cell so it's hard to search. How did you guys solve this in the A-10s?

Sent from my SM-A536B using Tapatalk
 

Is that the Apache? I’ve never actually flown it. In the a-10 commenting out a line in viewporthandling.lua ( to turn off in-game mfd’s) AND doing the same in one of the a-10 BAKE files( so the  mfd’s don't show on the main monitor in alt-f1. not sure if the same applies to the Apache or where that file would be. I came across it by sheer luck.

 Here was our conversation on the a-10. Maybe something similar for the Apache. Not sure if this is the same thing happening to the OP

[Alphapex1]

8 hours ago, lesthegrngo said:

please let us know the complete layout of your monitors, total pixel width and height, number of monitors, position and resolution of each. We need that to look at what is happening, as it will show us where things should be being displayed. Let us know if you need help on that

Cheers

Les

@lesthegrngo

This is my monitor layout，

 

Edited January 17, 2024 by Alphapex1

[Alphapex1]

23 minutes ago, MadKreator said:

那是阿帕奇吗？我从来没有真正飞过它。在a-10中注释掉viewporthandling.lua中的一行（以关闭游戏中的mfd）并在a-10 BAKE文件之一中执行相同的操作（因此mfd不会在alt-中的主显示器上显示） f1. 不确定这是否同样适用于 Apache 或该文件在哪里。我纯粹是运气好才发现它的。

 这是我们在 a-10 上的谈话。也许阿帕奇也有类似的东西。不确定OP是否也发生同样的事情

Yes, it's Apache.

Thanks, I'll try it.

[EyeDoc]

В 16.01.2024 в 15:21, Alphapex1 сказал:

I have two monitors.Then set LMFD+RMFD on the second screen.
When I use Alt+F1, CENTER_MFCD shows up in the middle of the two screens, 
How can I get CENTER_MFCD to show in the middle of the first screen?

This is my setup.

_  = function(p) return p; end;

name = _('2Cameras');

Description = '2Cameras'

Viewports =

{

     Center =

     {

          x = 0;

          y = 0;

          width  = 1920;

          height = 1080;

          viewDx = 0;

          viewDy = 0;

          aspect = screen.aspect / 2;

     }

}

 

LEFT_MFCD =

{

     x = 1920;

     y = 0;

     width = 960;

     height = 960;

}

 

RIGHT_MFCD =

{

     x = 2880;

     y = 0;

     width = 960;

     height = 960;

}

 

UIMainView = Viewports.Center

GROUND_MAIN_VIEWPORT = Viewports.Center

 

Hi. I have a similar problem with Alt+F1 View, though my setup is a bit different from yours, and I've noticed this kind of MFD displacement flying F/A-18. Initially (using one monitor only) I wasn't quite happy with 3 huge MFDs (on Alt+F1 View) obscuring the lower half of the screen (almost no ground surface is visible through them since in addition to their size - almost half of the vertical resolution - they have solid black background - as the one on your screenshot). I will add my screenshots to illustrate what I mean. So I decided to remove at least central MFD from the main screen and bought WinWing MFD+DDI for this purpose. But after plugging it in, making settings in Wimdows (main monitor on the left, WinWing on the right) and configuring it with its SimAppPro I noticed that along with some positive effect (central MFD is no more visible on the main screen, it moved to the WinWing's monitor - and remains there both in ordinary F1 View and in Alt+F1 View) there's also negative effect - my right MFD is now displaced to the right and part of it is out of the main monitor (I can see only left portion of it). And I think it has something to do with viewporthandling.lua. In the very first lines of this file you can see reference to (what I think is) the total screen resolution taken from the Settings window:

-- positioning on screen in HUD Only view 
function update_screenspace_diplacement(aspect,is_left,zoom_value)
    local w = LockOn_Options.screen.width;
    local h = LockOn_Options.screen.height;

And I think that's why this displacement can occur - because DCS in HUD Only (Alt+F1) view will align everything based on this TOTAL screen resolution - and NOT the MAIN SCREEN resolution (as would be more logical). So I tried to "tell" DCS the correct width and height of my main monitor directly typing its resolution there:

-- positioning on screen in HUD Only view 
function update_screenspace_diplacement(aspect,is_left,zoom_value)
    local w = 3840;
    local h = 2160;

Of course, I'm not sure that this is a completely right solution, but it helped me to bring my right MFD back inside my main monitor. So, position is fixed, now the size is the question... Does anyone know where (in which script file) the default size of these MFDs is hidden? And a wish for ED - please, let us configure our multi-monitor or HUD-only views in a more user-friendly way (not by manually editing numerous script files distributed across different folders, but by "drag and drop" graphical interface - Helios can be taken as an example) from inside DCS, without the need of third-parties software. There should be a way to define what is to be displayed (and in what position) on which monitor (or group of monitors) in multi-monitor configuration or  in HUD-only view. I think, it's simply not possible for ordinary user to figure out where to find all of these hidden settings and change them without causing possible configuration problems, security issues or even program crash. So, please, help us to do it more easily and safely.

[EyeDoc]

Well... I looked through viewporthandling.lua trying to understand what was the meaning of these expressions and variables (in my setup, with my screen resolution). I made notes and found the line which (to my mind) defined the size of MFDs. The last line in quoted fragment:

-- positioning on screen in HUD Only view 
function update_screenspace_diplacement(aspect,is_left,zoom_value)
    local w = 3840;
    local h = 2160;
    -- oculus_rift part removed from here    
    local x0 = 0        -- setting screen top left corner coordinates, x0=0
    local w0 = 0.5 * h    -- w0=y0=height/2=1080
    
    local aspect     =     aspect or 1
    local zoom_value = zoom_value or 0
    local default_width  = 762    -- w0 + (64 * zoom_value)

If you put your desired size there (like I did, commenting the rest of what was there originally) all the following calculations of the correct coordinates are performed automatically. And the result is as follows:

[Alphapex1]

On 3/18/2024 at 3:23 AM, EyeDoc said:

Well... I looked through viewporthandling.lua trying to understand what was the meaning of these expressions and variables (in my setup, with my screen resolution). I made notes and found the line which (to my mind) defined the size of MFDs. The last line in quoted fragment:

-- positioning on screen in HUD Only view 
function update_screenspace_diplacement(aspect,is_left,zoom_value)
    local w = 3840;
    local h = 2160;
    -- oculus_rift part removed from here    
    local x0 = 0        -- setting screen top left corner coordinates, x0=0
    local w0 = 0.5 * h    -- w0=y0=height/2=1080
    
    local aspect     =     aspect or 1
    local zoom_value = zoom_value or 0
    local default_width  = 762    -- w0 + (64 * zoom_value)

If you put your desired size there (like I did, commenting the rest of what was there originally) all the following calculations of the correct coordinates are performed automatically. And the result is as follows:

Wow,My buddy , this is amazing!  I never expected there would actually be a solution.  I'm unsing translator tool to reply to u,sry for my poor English  that  I can't express my excitement, but I'm truly grateful to you (I searched all over the internet and couldn't find a solution).  I will adjust my game settings using your method.  Thank you so much for your help, buddy .