Deezle

Well, I noticed that the Moza software deployed it's telemetry files to a "DCS" folder instead of my open beta install folder. I moved the files, as well as the line from the export.lua file to the proper folders, but no dice. I suspect the software is looking for everything in the wrong folder still and will not work. I converted my install folders to the unified version of the game, now that there aren't two seperate branches anyways. I deleted the Moza stuff from the scripts folder, set the install patch again so it would redeploy the files. FFB still does not work.

I also have no FFB with mine. Tried using direct input and telemetry mode. Launching DCS from the Moza software. Must be missing something obvious.

June 27th.

Got mine today. Don't have a way to mount it yet, I'll get something built tomorrow.

I pre-ordered on day one, just got a text message from DHL that I have a shipment inbound, which I assume is my AB9 base, but never got an email from Moza that it shipped.

Wags commented on a YouTube video and basically said that the AFCS and assorted flight control goodies are the highest priority.

Interesting observation. I have the Apache as well and the RWR audio for the Chinook also works for me. Maybe OP can confirm if they have the Apache or not.

This was reported in 2015 or 2016, don't hold your breath.

The radar altimeter is telling you the altitude between you and the load when the load is big enough, normal.

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.

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.

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.

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.

While not exclusive to the Chinook, the problem lies with each module individually (the controls and crew indicator files for each module that exhibits this behavior).

Yeah the text is quite small, it was absolutely necessary for me to export them to my second monitor.

Check in the Mods\aircraft\GCBase folder.

I resized just the cargo area textures by 50% which reduced the texture file by almost 2gb. However it made no noticeable FPS difference for me. Putting the game on medium textures makes a huge difference.

Screenshot to explain the issue.

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.

The text near the parking brake handle tells you how to release it.. Press and release the brake pedals.

Non-VR player here, FPS is definitely noticeably worse than other modules.

ED "can't reproduce" because they don't test multi-monitor setups. This has been a problem on many modules forever They continually don't confine things to the main viewport, extremely frustrating.

I have the same issue and can't figure out if I'm doing something wrong. I see the radio messages but there's no audio. I only hear the radio if the canopy is open.

This has been immediately apparent from my first moments in the Apache. Something is wrong here. Any attempt for me to quickly control the yaw with my feet results in occilations with the FCS fighting me back and forth. I can fly all the other helos in DCS quite well, without the aid of VR, the Apache is the hardest, no question.

It doesn't detect the missile itself, it detects the burning rocket motor, the system doesn't know if the missile has been destroyed or if the rocket motor has simply reached the end of its burn and the missile is still coming towards you. Seems correct to me.