Display exports

[Helles Belle]

14 hours ago, Lekaa said:

anyone having issues with to bright in the ingame mfds?
 

Yep, especially the moving map. WIP I guess.

[jonsky7]

16 hours ago, Lekaa said:

anyone having issues with to bright in the ingame mfds?
 

It is a long running issue when exporting MFDs that the exported displays can be a bit dim, and the cockpit displays become too bright.

It has been suggested that when exporting, the display being copied also gets another layer (double output), making it bright.

As I dont fly multicrew, what i do is export the co-pilot displayS. That way the pilots MFDs that are in my face are not effected, and the day/night/off button works as it should.

[xfirf]

I have increased the brightness of my second screen to compensate it.

[jenx]

any one have problems with the CDU buttons keying twice. its doing it for me on push and release to type twice

 

Also is there a key bind for the MFD's? Im trying to use my thrustmaster MFD's

[jonsky7]

24 minutes ago, jenx said:

any one have problems with the CDU buttons keying twice. its doing it for me on push and release to type twice

 

Also is there a key bind for the MFD's? Im trying to use my thrustmaster MFD's

I havent noticed that issue.

If you go in the controller issues a d bugs section, you'll find a post by me that has all the keybinds for the cdus and mfds.

[GeoS72]

@jonsky7, @MadKreator, & @Deezle,

Thanks for researching this display export for the Hook!

I noticed the contents of the MFD_device_IDs.lua file identifies the MFDs as follows:

"CO" - co-pilot outboard
"CI" - co-pilot inboard
"C"  - center
"PI" - pilot inboard
"PO" - pilot outboard

MFD_SELF_IDS =
CO = 0,
CI = 1,
C = 2,
PI = 3,
PO = 4

My multi-monitor config includes the use of 3 CubeSim 600x800 monitors plus the primary 2160x1440 display.

I played with the MFD_init_copilot_in/out.lua and MFD_init_pilot_in/out.lua files to see if they would alternate between positions. Foreshadow: it didn't work. Both pilot & copilot displays were overlaying on top of the other. I'm not a coder so break stuff but not confident to fix it.

Here is what I modified for the copilot files:

MFD_init_copilot_out.lua (lines 17 - 18):
17: update_screenspace_diplacement(0, true, 0)
18: try_find_assigned_viewport("CH47_Copilot_LEFT_MFCD")

MFD_init_copilot_in.lua (lines 17 - 18):
17: update_screenspace_diplacement(1, true, 1)
18: try_find_assigned_viewport("CH47_Copilot_RIGHT_MFCD")

I made a separate entry on my monitor config file to add the correct viewport for CH47_Copilot_LEFT/RIGHT_MFCD. I also used the "0, true, 0" and "1, true, 1" displacement values to aid in monitor identification. It did not help. I also changed the displacement values in the pilot position to "3, true, 3" and "4, true, 4" respectively. Again, this was no help in blanking the copilot displays while in the pilot seat and vise versa. 

The blanking of the displays when the player is not in the corresponding position is very similar to the AH-64 TEDAC blanking issue when switching from CPG to Pilot seats. @jonsky7, you initiated that TEDAC thread almost 2yrs ago too.

The solution you guys provided is a good start! For now, the pilot displays are presented on my CubeSim monitors while in any other crew position. At lease they respond to input from the Copilot seat. Ultimately, I believe this problem should be resolved by ED.

What do you guys think?