controls display screen lost after multi monitor

[cgjimeneza]

Hi.

I recently added a 12" mini monitor with MFD bezels, (Cougar ones).

I did manage with a lot of help to export the MFDs for apache, -18, -15E and kiowa... so im good there

the problem is that the small control indicator window got lost.

when I redefined the monitor size to account for the small monitor, most of my control indicator, (except for the OH-6) went missing.

I would like your help to define it's position and size as a fixed value and not as part of a formula that might get movednull

[MAXsenna]

It depends on every module where it's already placed. You can change all of them manually except for FC mules. It will break IC and be overwritten after every update.
It's based on a formula that's correct. Unfortunately. I wish the Controls Indicator was defined as a viewport we could place anywhere easily.

Sent from my SM-A536B using Tapatalk

[cgjimeneza]

if possible, send me a file name and what to look for, and i can back track and work from the OH-6A that shows its posit, it would be greatly appreciated

 

[MAXsenna]

if possible, send me a file name and what to look for, and i can back track and work from the OH-6A that shows its posit, it would be greatly appreciated
 

To my knowledge they're all called controlsindicator.lua, and you find them in mods/modulename/cockpit/scripts/ or indicator or something, except for FC modules where it doesn't exist, while it's defined somewhere else.

Sent from my SM-A536B using Tapatalk

[MadKreator]

I’ve never quite understood why these UI pieces ( controls, crew, kneeboard, compas rose on f-10 etc) are scaled and positioned off of the total screenspace instead of being locked to the defined screen for the UI… GUIMainview, or viewports.center… I mean the comms menu, chat window,  messages windows all stay on the main screen no matter what monitor config you have.

Edited November 7, 2024 by MadKreator

[MAXsenna]

I’ve never quite understood why these UI pieces ( controls, crew, kneeboard, compas rose on f-10 etc) are scaled and positioned off of the total screenspace instead of being locked to the defined screen for the UI… GUIMainview, or viewports.center… I mean the comms menu, chat window,  messages windows all say on the main screen no matter what monitor config you have.

Do you think the devs initially expected the game to survive three decades and users having multiple screens where the standard 17" at the time were pretty large?
Good times! I do feel parts of the game should just stop inheriting the spaghetti.

Sent from my SM-A536B using Tapatalk

[cgjimeneza]

I think file is ControlsIndicator_page.lua as it has more parameters.

will try to go from (A-4E vs F/A-18C vs OH-6A and see if if find anything)

 

[MadKreator]

2 hours ago, MAXsenna said:

Do you think the devs initially expected the game to survive three decades and users having multiple screens where the standard 17" at the time were pretty large?
Good times! I do feel parts of the game should just stop inheriting the spaghetti.

Sent from my SM-A536B using Tapatalk
 

I think they hoped it would, and are still in denial that anyone use anything else besides that and VR 

[MAXsenna]

I think file is ControlsIndicator_page.lua as it has more parameters.
will try to go from (A-4E vs F/A-18C vs OH-6A and see if if find anything)
 

Yeah. You could be right!

Sent from my SM-A536B using Tapatalk

[cgjimeneza]

no joy... was not able to find it, see the files I useda-4E control indicator.pdfUH-60L control i.pdf

it's getting to be frustrating

[cgjimeneza]

I have checked these two post;

https://www.digitalcombatsimulator.com/en/files/3321329/

nullbut no luck yet..

[MadKreator]

-I think the whole root of these issues starts from here. (1st pic is huey, 2nd is ah-64)The multipliers an values are in reference to total
"screenspace". When adding multi monitors dcs now sees the added monitors as part of the total screenspace (combined H and W). UI elements ( controls, kneeboard etc etc) I feel like, SHOULD be constrained to the main view.
- I have tried changing this to like 'ScreenType.UIMainView_TRUE'... ' ScreenType.GUI_MAIN_VIEWPORT_TRUE' etc to no avail.. to try to constrain it to what is defined as the center viewport/ main screen/ gui main view. I'm sure its really not as simple as that( nothing ever is), but this is probably the culprit in our issues with these things. however, changes to this actual script in this location, may not be exactly correct for defining that screenspace.
- as far as movement and sizing, it looks like everything is done in scaling like the above picture/ thread suggests. however the values may be wildly different on mine that's 3840X3240 over two screens, compared to 1024x768 on a single screen..
- also there's a chance that there is a more universal or a backend way for changing these things.. there are several things in the graphics.lua that do nothing anymore and are leftover lines of code.. as an example of things in the files that now don’t actually function.

 

interesting line in the kneeboard init.lua " --TODO: to do it really configurable".
These UI Elements all get very intertwined with the viewporthandling.lua for defining how and when to show them... all stepping a bit out of my range

Edited November 9, 2024 by MadKreator

[MadKreator]

... Or I could be completely wrong and that ScreenType.SCREENSPACE_TRUE, could just be referencing the "screenspace" of the cockpit Honestly just theorizing here

[cgjimeneza]

A glass of wine with you, sir...

or a whole bottle...  will try it monday after my chemoterapy session

LOL

[cgjimeneza]

https://www.digitalcombatsimulator.com/en/files/3342187/

see this post I made with modified indicators LUA file for

F/A-18

F-15 SE

A4E-C

AH-64D

UH-60L

Edited November 18, 2024 by cgjimeneza