Helles Belle Posted November 3, 2024 Posted November 3, 2024 14 hours ago, Lekaa said: anyone having issues with to bright in the ingame mfds? Yep, especially the moving map. WIP I guess. Send lawyers, guns and money......... for the …. has hit the fan. Windows 10 Home 64-bit | CPU: AMD Ryzen 7 5800X3D 8-Core Processor | RAM: Corsair 32.0GB Dual-Channel | MOBO: ROG STRIX X570-F GAMING (AM4) | GPU: MSI G271CQP on NVIDIA GeForce RTX 3080 | SSD: Samsung SSD 860 EVO 2TB & Samsung SSD 970 EVO Plus 1TB for Gaming CH Fightersick - Pro Throttle - Pro Pedals | Thrustmaster MFD Cougar x 3 | Buddy Fox A-10C UFC
jonsky7 Posted November 3, 2024 Author Posted November 3, 2024 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 Posted November 3, 2024 Posted November 3, 2024 I have increased the brightness of my second screen to compensate it.
jenx Posted November 20, 2024 Posted November 20, 2024 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 1 Duo Core E8500, 8 GB ram, Win 7, GTX 260, TH2Go, 3x 22in LG W2252TQ monitors, Hotas cougar, TrackIR4, Buttkicker
jonsky7 Posted November 20, 2024 Author Posted November 20, 2024 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. 1
GeoS72 Posted Monday at 02:22 AM Posted Monday at 02:22 AM @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? 1
MadKreator Posted Wednesday at 12:13 AM Posted Wednesday at 12:13 AM On 7/27/2025 at 8:22 PM, GeoS72 said: @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? It is definitely on ED's side. Not just making them switch but accessing all of the others, except the one (Pilot out) that is currently exportable using RIGHT_MFCD. My files in the first post were just preliminary "patches" for Helios.. As I'm sure you found out, in each one of the mfd init files, you just need to un-comment the script that ed has in there by default ( in the GC_Base folder) and give each one its own name, any name. And use that in your monitor file.. However the switching of them is done in some code that we don't have access to ( I believe). Same scenario as the apache tedac. Even in the Apache the only way to get the main mfd's to switch is to use LEFT_MFCD and RIGHT_MFCD and just one of each and it will flip back and forth between pilot and CPG. I don't think the CH-47 viewports have even been thought about. I mean the script is already written in the files, then they commented it out of all except one viewport.. Intel i7 13700k, ASUS rog strix z790A, 64gigs G.Skill Trident DDR5 @6400Mhz, Nvidia RTX 4080FE, 4TB, 2x 2TB, 1TB Samsung NVME, 1TB Samsung SSD, Corsair RM1000x, Corsair Titan 360 X AIO cooler, Lian Li LanCool 2, VKB Gunfighter Ultimate, VKB Custom STECS , MFG Crosswinds, Moza FFB, Virpil Collective, Track IR5, 48” LG UltraGear OLED & HP 24” touchscreen for Helios,49” Samsung Ultrawide, Streamdeck XL, Corsair Virtuoso RGB Headphones
Recommended Posts