Derbroomaster

Thanks very much. I can provide a new file of whatever you need if required.

Still happening after the latest patch. There are improvements, but this problem persists.

OK, having read through this thread numerous times and attempting to mess with the .lua file, I'm no closer to solving my problem. I will restate it, since I don't think I adequately described this problem in the beginning. The MFD screens for the Pilot's position do not show in the MFD screens for the Pilot's position in the Helios screen (monitor 1). The Pilot MFD screens for the Pilot's position on the Helios screen are in fact the displays for the CPG. If I press a Pilot MFD button on the Helios screen, it corresponds to the correct Pilot MFD button. If/when I occupy the CPG seat, there is no problem. The screens are exported as expected. Can anyone tell me why this could be happening? Helios profile and monitor configuration .lua files uploaded. AH64 Final1.hpf Helios.lua

Where is the file you're referencing here? And yes, the x value for resolution of the top screen should be 7680, as you mentioned.

Screen 1 is the touchscreen. I believe my true problem is that the CP/G export is being seen in the Pilot seat. When I sit in the front the displays are fine.

I will take a closer look at the Helios setup. I take care to apply Helios patches after every update and ensure each profile does not have identified issues. One thing to note is that the touchscreen (the fourth screen) is 1920 x 1080, while the other three are 2560 x 1440. The coordinates you call out in your screenshots: what numbers should those be as opposed to what are showing? Additionally, what is the .lua file these numbers came from and where is it located? Thanks for the information. I'll be doing my homework. I was away from the sim for a week learning a GA plane.

OK. Thank you for looking.

This is the only Apache-related file in that path: DCS Apache.lua

Where is this file normally located? I don't go under the hood often enough to remember.

I'll put up this information the next time I get on the rig.

While possible, it would be multiple old profiles, as I see this manifest across at least two: the one I referenced and Bunny's AH-64D Helios profile.

Yes. When sitting in the back seat and I look over the CP/G's shoulder, I can see the displays I'm supposed to have on my touchscreen for the pilot. When I switch to the CP/G position, I see the screens for the pilot, not for the MFDs and TEDAC.

This appears to be a DCS thing, not a profile thing. I've used multiple profiles (we have a lot of brainy people among us, nice) and they all have the MFDs reversed. Anyone have an idea what might be causing this?

Hi, all. As it says in the title, the exports for the CP/G are what the Pilot sees in the MFDs, and vice-versa when I take the CP/G position. Buttons all work, and all other displays work the way they're supposed to. Anyone else use this profile? https://www.digitalcombatsimulator.com/en/files/3342923/ It's an otherwise very solid Helios profile and I enjoy using it. I don't mind editing files if that's what's required. Cheers

What fixed this for you?

It was probably an hour or so, I'm not 100% sure. I was under the impression giving a time would help with fast-forwarding to the appropriate time the incident occurred. Do you have an example of this topic you'd like to share? If not, you may not understand the frustration a lot of us are feeling as we constantly provide reports and examples.

So the track files needed to diagnose a problem are themselves unable to be used. Cool. Did you go to the time stated in my original report?

Another example today. This time he was given a target multiple times, starting around 04:33:30 or so. Didn't even lase the target when it was clearly in his sight. https://drive.google.com/file/d/1vvPn3eW32ddslUiJ-rVgywTHVnnuEeKX/view?usp=drive_link

Just happened again. Time 2:47. Lased a target outside of engagement range, then didn't do it again. Gave him at least two or three more targets, which he never lased. You now have a track file and the time to look for. Please investigate. Syria_Modern_012-Day Watch-20241108-112210.trk

Aaaaaand just happened again in multiplayer. PLEASE INVESTIGATE THIS

Just happened again in multiplayer.

Just happened again mid-mission. Killed by OSA that George would not fire on when ordered to.

Hitting a jet with a Stinger from a Kiowa is one of the more satisfying things I've experienced. This problem still exists. Got shot down during squadron night more than once because George AI did not fire when needed.

Still happening.

This is still happening. Almost got killed last night several times due to AI not firing or lasing when he's supposed to.