need track replay Desync between the pilot and cpg

[[RH]Mostafa]

Even thought the Pilot start everything no warning i got those warning that listed below as CPG the attached picture  

Edited June 23, 2022 by [RH]Mostafa

[BIGNEWY]

Hi, thanks for the report and message on discord 

please if possible attach a track replay for the pilot and gunner when the desync happens.

We are investigating but it does not always seem to happen and catching it has been difficult 

[Antix70]

Not sure if it's the same as the OP, but we keep getting an issue where the Pilot and CPG desync.

The CPG can see where the TADS is slewed to, target and fire, but as the Pilot, I see the dashed crosshair that is bouncing all around the Pilot Crosshair.

The track is larger than 5mb, so no sure how I'm supposed to get that to you

 

 

[Floyd1212]

Yes, as PLT I see de-sync between what the CPG is aiming/shooting at, vs what I am seeing on the MFD in VID mode, and where the dashed LOS crosshair is looking.

[granola1861]

I've got this issue as well.  The issue start at around 18 minutes in the mission.  Prior to that (from the pilot seat) the video screen (TADS) follows the tads movement and the tads cross is accurate.  Around 18 minutes in (confirmed via TACVIEW) the desync happens with the video no longer tracking and the cross is locked to the video location.  I can see when the CPG changes from FLIR to TV and zoom modes.  We did find that when the CPG slaves to a location (SP or TP) the video and cross correct themselves only to stop tracking once deslaved.  I did notice the cross moving the opposite direction from the CPG (he said he was going left and I watched it move right). FYI: both players performed a DCS repair prior to the second mission and I deleted the FXO and metashaders2 folder from saved games. 

I've got track files from 2 instances on the same mission but no track files from the CPG position.  Sorry...

 

Hope this can get remedied quick for a Friday hotfix since it is a game killer due to the hindrance to crew coordination. 

 

Server files too large to upload here. 

Link:  https://drive.google.com/drive/folders/1-fh_SmglIRtYG0K3DTrHsnLIZUGVs6Md?usp=sharing

 

-Climber

Edited June 24, 2022 by granola1861
added FYI info

[Antix70]

One thing I have noticed when this happens, is there's a very brief pause in DCS, a lag or something, less than a second, after that, the dashed crosshair follows PHS, and if I settle on a target, the crosshair will bounce around my focus point. Changing acquisition point doesn't do anything. If I set it to fixed, the dashed crosshair will settle to the head tracker diamond, but the TADS video on the Pilots MFD (Video -> TADS -> TADS) still tracks with PHS.

[Tshark]

On 6/23/2022 at 9:38 PM, granola1861 said:

I've got this issue as well.  The issue start at around 18 minutes in the mission.  Prior to that (from the pilot seat) the video screen (TADS) follows the tads movement and the tads cross is accurate.  Around 18 minutes in (confirmed via TACVIEW) the desync happens with the video no longer tracking and the cross is locked to the video location.  I can see when the CPG changes from FLIR to TV and zoom modes.  We did find that when the CPG slaves to a location (SP or TP) the video and cross correct themselves only to stop tracking once deslaved.  I did notice the cross moving the opposite direction from the CPG (he said he was going left and I watched it move right). FYI: both players performed a DCS repair prior to the second mission and I deleted the FXO and metashaders2 folder from saved games. 

I've got track files from 2 instances on the same mission but no track files from the CPG position.  Sorry...

 

Hope this can get remedied quick for a Friday hotfix since it is a game killer due to the hindrance to crew coordination. 

 

Server files too large to upload here. 

Link:  https://drive.google.com/drive/folders/1-fh_SmglIRtYG0K3DTrHsnLIZUGVs6Md?usp=sharing

 

-Climber

 

I have been flying as the CP/G with Climber and we confirmed last night that the desync only occurs if the LMC is used.  As Bignewy suggested elsewhere I have unbound LMC until the bug is fixed.

[granola1861]

-Still having same issue following update on 7-21-22 .  Once LMC is used, the CPG dashed cross and TADS are desynced.  The CPG can slave to the pilot's LOS but once deslaved it will not match the TADs movement. 

Track link:  https://drive.google.com/file/d/10qa9lMDUZzMM9RHPWD56OJv6loiXLd_O/view?usp=sharing

 

-Climber

[Tshark]

In the above post I was the CP/G and here is my track file from the same mission.

Track link: https://drive.google.com/file/d/1NPaoWsOZYtYYzYubCmYEX_gm2YQ_x-bj/view?usp=sharing

-Tshark

[NightstalkerNOR]

Me and my friend had the exact same issue as described two posts above. The TADS would show something entirely different in my screen than his. It was not frozen, but was moving in relation the aircrafts movement. He was slewing as CPG but the TADS Cross in the PHS was looking at me.

[granola1861]

Really expected some movement on this issue this week.  I've stuck the Apache in the hangar until it gets some resolution...

[Antix70]

Still happening for myself and my CPG as well.

[admiki]

Had low rotor RPM few days ago.

We made sure that no one touched anything until both crewmwmbers were spawned in hot helicopter.

Next spawn was just fine.