Display exports

[jonsky7]

For info

If you like to export your displays I have some info for you.

The only exportable display seems to be the RIGHT MFCD from the right seat
RIGHT_MFCD

and if you like to export your displays based on the aircraft type, the Chinook's self name is

CH-47Fbl1

 

It seems the exports are coming from the folder called GCBase located in the aircraft directly.

The LEFT_MFCD export is commented out at the moment.

Edited August 10, 2024 by jonsky7

[jonsky7]

The inner MFCD and Centre MFCD are currently "commented out" so they don't export, but I've removed the comments (--[[,--]]) and those displays seems to export fine. This is a mod however and will break integrity check on servers requiring "pure scripts" 

 

OvGME ready Mod files to enable the exports for 

Pilots left (inboard) MFCD - LEFT_MFCD
Centre MFCD - CENTRE_MFCD
Co-pilots left (outboard) - CO_LEFT_MFCD
Co-pilots right (inboard) - CO_RIGHT_MFCD

Chinook Exports.zip

 

be aware that the exports do not automatically switch when switching seats so you will need to put the pilots and copilots displays in different locations.

Edited August 10, 2024 by jonsky7

[Deezle]

Thanks. I was looking in the MFD folder for the Chinook for the individual MFD init files in order to export them but they were not there like I'm used to. I'll check this out. Hopefully this will change in the future so we don't have to break IC to use it

 

I already exported the RWR, however it's a completely unusable blurry mess when exported

 

Multi-monitor users keep getting the shaft.

Edited August 10, 2024 by Deezle

[MadKreator]

On 8/10/2024 at 7:30 AM, jonsky7 said:

The inner MFCD and Centre MFCD are currently "commented out" so they don't export, but I've removed the comments (--[[,--]]) and those displays seems to export fine. This is a mod however and will break integrity check on servers requiring "pure scripts" 

 

OvGME ready Mod files to enable the exports for 

Pilots left (inboard) MFCD - LEFT_MFCD
Centre MFCD - CENTRE_MFCD
Co-pilots left (outboard) - CO_LEFT_MFCD
Co-pilots right (inboard) - CO_RIGHT_MFCD

Chinook Exports.zip

 

be aware that the exports do not automatically switch when switching seats so you will need to put the pilots and copilots displays in different locations.

 

Good to know! Just got back in town and started on graphics for Helios profile. Shifted gears and started fiddling with exports, only saw the mfd and cdu folders and if you call them to export they put all of the displays on top of each other, kinda funny. I will mess with the GCBase files and see if I can make some working Helios patches.

[Deezle]

1 hour ago, MadKreator said:

Good to know! Just got back in town and started on graphics for Helios profile. Shifted gears and started fiddling with exports, only saw the mfd and cdu folders and if you call them to export they put all of the displays on top of each other, kinda funny. I will mess with the GCBase files and see if I can make some working Helios patches.

I started a Helios profile for just the two MFDs. I'm happy with how it looks but unfortunately I don't have any working buttons yet. I followed @Capt Zeen tutorial, but the command_defs.lua doesn't have any of the commands in it and I'm unsure how to continue.

[Bigity]

Wonder how these are gonna look smushed to fit into my cougar panel displays

[MadKreator]

18 minutes ago, Deezle said:

I started a Helios profile for just the two MFDs. I'm happy with how it looks but unfortunately I don't have any working buttons yet. I followed @Capt Zeen tutorial, but the command_defs.lua doesn't have any of the commands in it and I'm unsure how to continue.

Yes the file structure is a bit odd. It seems every aircraft is a bit different in how they are presented.. they may be just listed in clickabledata.lua, like button 28 would be command 3028, button 5 would be 3005 etc etc, might check that out. A couple WW2 aircraft i worked on were like that. I’m just getting graphics cut ready now. Except for doing the CDU(s) the rest of it looks like a fairly simple job.  Bluefin is writing the JSON interface for helios for it currently. I will wait for him to get done with that one since I’m very lua-stupid

26 minutes ago, Bigity said:

Wonder how these are gonna look smushed to fit into my cougar panel displays

They’ll be squishy for sure 1.33333 seems to be the right aspect ratio for them.  Currently at 600w x 800t px they look pretty correct.. of course I didn’t do any real scientific measuring. 

[Deezle]

33 minutes ago, MadKreator said:

Yes the file structure is a bit odd. It seems every aircraft is a bit different in how they are presented.. they may be just listed in clickabledata.lua, like button 28 would be command 3028, button 5 would be 3005 etc etc, might check that out. A couple WW2 aircraft i worked on were like that. I’m just getting graphics cut ready now. Except for doing the CDU(s) the rest of it looks like a fairly simple job.  Bluefin is writing the JSON interface for helios for it currently. I will wait for him to get done with that one since I’m very lua-stupid

They’ll be squishy for sure 1.33333 seems to be the right aspect ratio for them.  Currently at 600w x 800t px they look pretty correct.. of course I didn’t do any real scientific measuring. 

I tried that with no luck, but being new to creating Helios profiles, I'm probably doing something wrong.

 

I also came up with the same aspect ratio.

[MadKreator]

1 hour ago, Deezle said:

I tried that with no luck, but being new to creating Helios profiles, I'm probably doing something wrong.

 

I also came up with the same aspect ratio.

managed all 5 mfds and the rwr . In the APR39_init.lua ( assuming where you did the rwr export) line 8- "shaderLineDrawAsWire", set that to true instead of false and you should get a legible RWR.. the in-game one will prob disappear, but your export should be decent

Also it does look like the device commands are listed as button numbers in clickabledata.lua for each device. and of course devices.lua gives you the device ID for each main category of devices. I've never trued to write one of CZ' lua interfaces. I've watched the videos, but then started messing with JSON interfaces and never gave CZ's way a shot.

 

 

Edited August 12, 2024 by MadKreator

[MadKreator]

K now all 5 mfd’s L and R CD/U, RWR and the Chronometer, I think just two more displays to go

[MadKreator]

There's the last two "SFD's". Also the files that I re-wrote and my monitor setup file for reference, ( its a helios file so it may be formatted differently and scaling is not correct necessarily). All viewports are renamed from the originals so its definitely an IC breaker. But if anyone wants to fiddle with these, they are here.

CH-47 Viewport Patches.7z

[Bigity]

Wonder if there is a way to export just the top half of the MFDs

[Bigity]

5 hours ago, MadKreator said:

There's the last two "SFD's". Also the files that I re-wrote and my monitor setup file for reference, ( its a helios file so it may be formatted differently and scaling is not correct necessarily). All viewports are renamed from the originals so its definitely an IC breaker. But if anyone wants to fiddle with these, they are here.

CH-47 Viewport Patches.7z 2.5 kB · 2 downloads

How do I get these into Helios?

[MadKreator]

34 minutes ago, Bigity said:

How do I get these into Helios?

Have to find and Replace the default file with these in the game files.. some in …dcsworld/aircraft/GCBase( the mfd’s, cdu’s  and chronograph) the others in dcsworld/aircraft/ch-47/cockpit/scripts ( rwr and SFD’s) then list them out like I did in the attached monitor file( heliosch47).. but the sizes and locations will be different. Kind of have to mutt it together.. you will have to make a copy then rename your “Helios” monitor file then add these. Since the patches aren’t part of helios yet, helios will just overwrite them, or not let you select the monitor file in dcs. Viewports are always a function of DCS, Helios just helps writing the monitor file for exports.

Edited August 12, 2024 by MadKreator

[Bigity]

44 minutes ago, MadKreator said:

Have to find and Replace the default file with these in the game files.. some in …dcsworld/aircraft/GCBase( the mfd’s, cdu’s  and chronograph) the others in dcsworld/aircraft/ch-47/cockpit/scripts ( rwr and SFD’s) then list them out like I did in the attached monitor file( heliosch47).. but the sizes and locations will be different. Kind of have to mutt it together.. you will have to make a copy then rename your “Helios” monitor file then add these. Since the patches aren’t part of helios yet, helios will just overwrite them, or not let you select the monitor file in dcs. Viewports are always a function of DCS, Helios just helps writing the monitor file for exports.

 

Ah, durp, I was thinking they imported into Helios somehow.  Thanks!

[MadKreator]

27 minutes ago, Bigity said:

Ah, durp, I was thinking they imported into Helios somehow.  Thanks!

Oh no. Bluefin will have to go through them and see if he likes the way I did them/ named them. And he will have to get them programmed in. He has an interface pretty much done, will need tweaks still. He’s testing the couple gauges and I started on graphics for the toolbox today. I will build a full profile once all that is wrapped up and he can ship some things with the next Helios release. It’s all manual at the moment unfortunately. 

[jonsky7]

11 hours ago, Bigity said:

Wonder if there is a way to export just the top half of the MFDs

Don't think so but you could just resize them so just the top half fits inside your MFD.

I personally have them squashed to fit. Don't have an issue with reading the text etc, my MFD buttons are mounted to a 11 inch 1080p display.

[jonsky7]

On 8/12/2024 at 4:11 AM, MadKreator said:

managed all 5 mfds and the rwr . In the APR39_init.lua ( assuming where you did the rwr export) line 8- "shaderLineDrawAsWire", set that to true instead of false and you should get a legible RWR.. the in-game one will prob disappear, but your export should be decent

Also it does look like the device commands are listed as button numbers in clickabledata.lua for each device. and of course devices.lua gives you the device ID for each main category of devices. I've never trued to write one of CZ' lua interfaces. I've watched the videos, but then started messing with JSON interfaces and never gave CZ's way a shot.

 

 

 

I've also looked into this, I have created and modified keybinds before but I'm not a .lua guru by any stretch.

However, the CDU keyboard buttons are not written like they usually are, and I couldn't seem to get anything to work. Even tried just changing the "name" of one of the keybinds, but it didn't show up in the controls menu. Any change also just seemed to grey out all the other keyboard binds unless it was already bound to a key.

Also Quaggles input injector script didn't seem to work.

Very different to usual.

[MadKreator]

9 hours ago, jonsky7 said:

I've also looked into this, I have created and modified keybinds before but I'm not a .lua guru by any stretch.

However, the CDU keyboard buttons are not written like they usually are, and I couldn't seem to get anything to work. Even tried just changing the "name" of one of the keybinds, but it didn't show up in the controls menu. Any change also just seemed to grey out all the other keyboard binds unless it was already bound to a key.

Also Quaggles input injector script didn't seem to work.

Very different to usual.

Interesting, I haven’t messed with the CDU yet, thats the next project. Bluefin smashed out the entire interface already but I haven’t browsed it. Got  a dev build already for helios with the mfd’s and gauges but the CDU will take some work Nothings ever the same aircraft to aircraft. Always a mystery trying to figure out a new module

[Bigity]

17 hours ago, jonsky7 said:

Don't think so but you could just resize them so just the top half fits inside your MFD.

I personally have them squashed to fit. Don't have an issue with reading the text etc, my MFD buttons are mounted to a 11 inch 1080p display.

Same, one MFD in each top corner except its a 1366x768 (or something like that)

Edited August 13, 2024 by Bigity

[Deezle]

On 8/11/2024 at 8:11 PM, MadKreator said:

managed all 5 mfds and the rwr . In the APR39_init.lua ( assuming where you did the rwr export) line 8- "shaderLineDrawAsWire", set that to true instead of false and you should get a legible RWR.. the in-game one will prob disappear, but your export should be decent

Also it does look like the device commands are listed as button numbers in clickabledata.lua for each device. and of course devices.lua gives you the device ID for each main category of devices. I've never trued to write one of CZ' lua interfaces. I've watched the videos, but then started messing with JSON interfaces and never gave CZ's way a shot.

 

 

 

This is what I'm seeing for the MFD buttons in the clickable_data.lua. It's different than most of the other buttons and switches. I've tried both 3001 and 3906, just trying to get T1 working first. Upon inspection in modelviewer, 3906 is the correct number for T1 on the inboard pilot MFD.

 

Pilot Inboard MFD ------------------------------------------------------------
			elements["MFD-PL-KEY-T1-906"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T1"), 		device_commands.Button_1)
			elements["MFD-PL-KEY-T2-907"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T2"), 		device_commands.Button_2)
			elements["MFD-PL-KEY-T3-908"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T3"), 		device_commands.Button_3)
			elements["MFD-PL-KEY-T4-909"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T4"), 		device_commands.Button_4)
			elements["MFD-PL-KEY-T5-910"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T5"), 		device_commands.Button_5)
			elements["MFD-PL-KEY-T6-911"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T6"), 		device_commands.Button_6)
			elements["MFD-PL-KEY-T7-912"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T7"), 		device_commands.Button_7)
			elements["MFD-PL-KEY-R1-913"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R1"), 		device_commands.Button_8)
			elements["MFD-PL-KEY-R2-914"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R2"), 		device_commands.Button_9)
			elements["MFD-PL-KEY-R3-915"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R3"), 		device_commands.Button_10)
			elements["MFD-PL-KEY-R4-916"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R4"), 		device_commands.Button_11)
			elements["MFD-PL-KEY-R5-917"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R5"), 		device_commands.Button_12)
			elements["MFD-PL-KEY-R6-918"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R6"), 		device_commands.Button_13)
			elements["MFD-PL-KEY-R7-919"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R7"), 		device_commands.Button_14)
			elements["MFD-PL-KEY-R8-920"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R8"), 		device_commands.Button_15)
			elements["MFD-PL-KEY-R9-921"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R9"), 		device_commands.Button_16)
			elements["MFD-PL-KEY-B1-922"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B1"), 		device_commands.Button_17)
			elements["MFD-PL-KEY-B2-923"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B2"), 		device_commands.Button_18)
			elements["MFD-PL-KEY-B3-924"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B3"), 		device_commands.Button_19)
			elements["MFD-PL-KEY-B4-925"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B4"), 		device_commands.Button_20)
			elements["MFD-PL-KEY-B5-926"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B5"), 		device_commands.Button_21)
			elements["MFD-PL-KEY-B6-927"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B6"), 		device_commands.Button_22)
			elements["MFD-PL-KEY-B7-928"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B7"), 		device_commands.Button_23)
			elements["MFD-PL-KEY-L1-929"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L1"), 		device_commands.Button_24)
			elements["MFD-PL-KEY-L2-930"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L2"), 		device_commands.Button_25)
			elements["MFD-PL-KEY-L3-931"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L3"), 		device_commands.Button_26)
			elements["MFD-PL-KEY-L4-932"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L4"), 		device_commands.Button_27)
			elements["MFD-PL-KEY-L5-933"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L5"), 		device_commands.Button_28)
			elements["MFD-PL-KEY-L6-934"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L6"), 		device_commands.Button_29)
			elements["MFD-PL-KEY-L7-935"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L7"), 		device_commands.Button_30)
			elements["MFD-PL-KEY-L8-936"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L8"), 		device_commands.Button_31)
			elements["MFD-PL-KEY-L9-937"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L9"), 		device_commands.Button_32)

This is what I'm seeing in the devices.lua. Presumably the pilot inboard MFD is device #7?

 

-------DEVICE ID-------
devices = {}

devices["MCPU"]                     = counter()

devices["CDU_LEFT"]                 = counter()
devices["CDU_RIGHT"]                = counter()

-- MFD 4
devices["MFD_COPILOT_OUTBOARD"]     = counter()
-- MFD 3
devices["MFD_COPILOT_INBOARD"]      = counter()
-- MFD 5
devices["MFD_CENTER"]               = counter()
-- MFD 2
devices["MFD_PILOT_INBOARD"]        = counter()
-- MFD 1
devices["MFD_PILOT_OUTBOARD"]       = counter()

 

Still not having any luck.

Edited August 16, 2024 by Deezle

[MadKreator]

11 hours ago, Deezle said:

This is what I'm seeing for the MFD buttons in the clickable_data.lua. It's different than most of the other buttons and switches. I've tried both 3001 and 3906, just trying to get T1 working first. Upon inspection in modelviewer, 3906 is the correct number for T1 on the inboard pilot MFD.

 

Pilot Inboard MFD ------------------------------------------------------------
			elements["MFD-PL-KEY-T1-906"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T1"), 		device_commands.Button_1)
			elements["MFD-PL-KEY-T2-907"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T2"), 		device_commands.Button_2)
			elements["MFD-PL-KEY-T3-908"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T3"), 		device_commands.Button_3)
			elements["MFD-PL-KEY-T4-909"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T4"), 		device_commands.Button_4)
			elements["MFD-PL-KEY-T5-910"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T5"), 		device_commands.Button_5)
			elements["MFD-PL-KEY-T6-911"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T6"), 		device_commands.Button_6)
			elements["MFD-PL-KEY-T7-912"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T7"), 		device_commands.Button_7)
			elements["MFD-PL-KEY-R1-913"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R1"), 		device_commands.Button_8)
			elements["MFD-PL-KEY-R2-914"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R2"), 		device_commands.Button_9)
			elements["MFD-PL-KEY-R3-915"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R3"), 		device_commands.Button_10)
			elements["MFD-PL-KEY-R4-916"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R4"), 		device_commands.Button_11)
			elements["MFD-PL-KEY-R5-917"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R5"), 		device_commands.Button_12)
			elements["MFD-PL-KEY-R6-918"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R6"), 		device_commands.Button_13)
			elements["MFD-PL-KEY-R7-919"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R7"), 		device_commands.Button_14)
			elements["MFD-PL-KEY-R8-920"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R8"), 		device_commands.Button_15)
			elements["MFD-PL-KEY-R9-921"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R9"), 		device_commands.Button_16)
			elements["MFD-PL-KEY-B1-922"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B1"), 		device_commands.Button_17)
			elements["MFD-PL-KEY-B2-923"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B2"), 		device_commands.Button_18)
			elements["MFD-PL-KEY-B3-924"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B3"), 		device_commands.Button_19)
			elements["MFD-PL-KEY-B4-925"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B4"), 		device_commands.Button_20)
			elements["MFD-PL-KEY-B5-926"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B5"), 		device_commands.Button_21)
			elements["MFD-PL-KEY-B6-927"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B6"), 		device_commands.Button_22)
			elements["MFD-PL-KEY-B7-928"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B7"), 		device_commands.Button_23)
			elements["MFD-PL-KEY-L1-929"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L1"), 		device_commands.Button_24)
			elements["MFD-PL-KEY-L2-930"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L2"), 		device_commands.Button_25)
			elements["MFD-PL-KEY-L3-931"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L3"), 		device_commands.Button_26)
			elements["MFD-PL-KEY-L4-932"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L4"), 		device_commands.Button_27)
			elements["MFD-PL-KEY-L5-933"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L5"), 		device_commands.Button_28)
			elements["MFD-PL-KEY-L6-934"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L6"), 		device_commands.Button_29)
			elements["MFD-PL-KEY-L7-935"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L7"), 		device_commands.Button_30)
			elements["MFD-PL-KEY-L8-936"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L8"), 		device_commands.Button_31)
			elements["MFD-PL-KEY-L9-937"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L9"), 		device_commands.Button_32)

This is what I'm seeing in the devices.lua. Presumably the pilot inboard MFD is device #7?

 

-------DEVICE ID-------
devices = {}

devices["MCPU"]                     = counter()

devices["CDU_LEFT"]                 = counter()
devices["CDU_RIGHT"]                = counter()

-- MFD 4
devices["MFD_COPILOT_OUTBOARD"]     = counter()
-- MFD 3
devices["MFD_COPILOT_INBOARD"]      = counter()
-- MFD 5
devices["MFD_CENTER"]               = counter()
-- MFD 2
devices["MFD_PILOT_INBOARD"]        = counter()
-- MFD 1
devices["MFD_PILOT_OUTBOARD"]       = counter()

 

Still not having any luck.

 

Bluefin has them working in the Helios dev build that I have while building the parts. I have not looked at the interface yet since I’m in graphic mode right now. I will check it soon and let you know what I see in it, to get you on the right track. I think it will ship with Helios soon though. The mfd’s are done and functional, I’m building the CDU now, the two analog gauges are in progress, interface and viewport patches should be done in a couple days. The interface may only ship with guaranteed working mfd’s, cdu’s and gauges right at first. It will take me some time to go trough everything and clean it up while building the rest of the switches and panels. It will be at the mercy of what bluefin wants to do, of course, but I think pushing out these main components first is a good idea since they do the brunt of the work. Everything else ( main functions like hook and winch controls) are easily bindable to hotas controls for the moment 

[MadKreator]

15 hours ago, Deezle said:

This is what I'm seeing for the MFD buttons in the clickable_data.lua. It's different than most of the other buttons and switches. I've tried both 3001 and 3906, just trying to get T1 working first. Upon inspection in modelviewer, 3906 is the correct number for T1 on the inboard pilot MFD.

 

Pilot Inboard MFD ------------------------------------------------------------
			elements["MFD-PL-KEY-T1-906"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T1"), 		device_commands.Button_1)
			elements["MFD-PL-KEY-T2-907"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T2"), 		device_commands.Button_2)
			elements["MFD-PL-KEY-T3-908"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T3"), 		device_commands.Button_3)
			elements["MFD-PL-KEY-T4-909"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T4"), 		device_commands.Button_4)
			elements["MFD-PL-KEY-T5-910"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T5"), 		device_commands.Button_5)
			elements["MFD-PL-KEY-T6-911"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T6"), 		device_commands.Button_6)
			elements["MFD-PL-KEY-T7-912"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_T7"), 		device_commands.Button_7)
			elements["MFD-PL-KEY-R1-913"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R1"), 		device_commands.Button_8)
			elements["MFD-PL-KEY-R2-914"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R2"), 		device_commands.Button_9)
			elements["MFD-PL-KEY-R3-915"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R3"), 		device_commands.Button_10)
			elements["MFD-PL-KEY-R4-916"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R4"), 		device_commands.Button_11)
			elements["MFD-PL-KEY-R5-917"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R5"), 		device_commands.Button_12)
			elements["MFD-PL-KEY-R6-918"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R6"), 		device_commands.Button_13)
			elements["MFD-PL-KEY-R7-919"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R7"), 		device_commands.Button_14)
			elements["MFD-PL-KEY-R8-920"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R8"), 		device_commands.Button_15)
			elements["MFD-PL-KEY-R9-921"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_R9"), 		device_commands.Button_16)
			elements["MFD-PL-KEY-B1-922"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B1"), 		device_commands.Button_17)
			elements["MFD-PL-KEY-B2-923"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B2"), 		device_commands.Button_18)
			elements["MFD-PL-KEY-B3-924"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B3"), 		device_commands.Button_19)
			elements["MFD-PL-KEY-B4-925"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B4"), 		device_commands.Button_20)
			elements["MFD-PL-KEY-B5-926"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B5"), 		device_commands.Button_21)
			elements["MFD-PL-KEY-B6-927"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B6"), 		device_commands.Button_22)
			elements["MFD-PL-KEY-B7-928"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_B7"), 		device_commands.Button_23)
			elements["MFD-PL-KEY-L1-929"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L1"), 		device_commands.Button_24)
			elements["MFD-PL-KEY-L2-930"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L2"), 		device_commands.Button_25)
			elements["MFD-PL-KEY-L3-931"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L3"), 		device_commands.Button_26)
			elements["MFD-PL-KEY-L4-932"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L4"), 		device_commands.Button_27)
			elements["MFD-PL-KEY-L5-933"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L5"), 		device_commands.Button_28)
			elements["MFD-PL-KEY-L6-934"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L6"), 		device_commands.Button_29)
			elements["MFD-PL-KEY-L7-935"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L7"), 		device_commands.Button_30)
			elements["MFD-PL-KEY-L8-936"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L8"), 		device_commands.Button_31)
			elements["MFD-PL-KEY-L9-937"] 				= mfd_special_key('PI', _("Cockpit.CH47.MFD.KEY_L9"), 		device_commands.Button_32)

This is what I'm seeing in the devices.lua. Presumably the pilot inboard MFD is device #7?

 

-------DEVICE ID-------
devices = {}

devices["MCPU"]                     = counter()

devices["CDU_LEFT"]                 = counter()
devices["CDU_RIGHT"]                = counter()

-- MFD 4
devices["MFD_COPILOT_OUTBOARD"]     = counter()
-- MFD 3
devices["MFD_COPILOT_INBOARD"]      = counter()
-- MFD 5
devices["MFD_CENTER"]               = counter()
-- MFD 2
devices["MFD_PILOT_INBOARD"]        = counter()
-- MFD 1
devices["MFD_PILOT_OUTBOARD"]       = counter()

 

Still not having any luck.

 

Oh also slipped my mind, on CZ’s discord in the “share your profiles” section , user Klismell posted a small quick and dirt profile he made. not a full interface but I believe the mfd’s ( pilot’s and center) as well as pilot CDU are function in his interface.

[Deezle]

7 hours ago, MadKreator said:

Oh also slipped my mind, on CZ’s discord in the “share your profiles” section , user Klismell posted a small quick and dirt profile he made. not a full interface but I believe the mfd’s ( pilot’s and center) as well as pilot CDU are function in his interface.

Thanks, I'm a member of that Discord but I forgot about it. I downloaded that profile and I'm not having any luck with the buttons working on it, let alone when using that interface with my existing profile. Someday I'll figure out what I'm doing wrong. All my CZ profiles work fine.

 

EDIT: Well I went through and deleted a bunch of stuff and started over and it's working now. I think there was some sort of interference between my existing profile and the one I downloaded? IDK, but at least it's working now.

Edited August 17, 2024 by Deezle

[Lekaa]

anyone having issues with to bright in the ingame mfds?