Jump to content

Recommended Posts

Posted (edited)

Hi,

 

as soon as the human CPG activates the LMC, there are significant desynchronisations of the LOS crosshairs in IHADSS. This is observed with both multi- and local servers.

 

To reproduce this, I created the track files at my two places (CPG-PC/Pilot-Simpit) within a network.

 

I can reproduce it 100% at any time and unfortunately this makes the LMC effectively useless in its application. To avoid this bug we no longer use LMC.

 

Greetings

T-Bone

 

Edit_1:
Has been listed multiple times as fixed before, but is not the case.
https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.7.12.23362/

https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.7.11.22041/

 

LMC Desync Package.zip

Edited by [Eule-22] T-Bone
  • Like 1

Main machine: Ryzen 7 5800X3D, 64Gb 3600Mhz, Gainward RTX 5080 Phoenix V1

Second machine: Ryzen 5 5600X, 32Gb 3600Mhz, ASrock 7700 XT

Equipment: microHELIS Bell 206 Pedale + Toe-Brakes, microHELIS OH-58D Collective, DIY FFB-Rhino clone, Realteus Forcefeel, TrackIR 5

Posted
On 12/14/2022 at 11:26 AM, [Eule-22] T-Bone said:

Hi,

 

as soon as the human CPG activates the LMC, there are significant desynchronisations of the LOS crosshairs in IHADSS. This is observed with both multi- and local servers.

 

To reproduce this, I created the track files at my two places (CPG-PC/Pilot-Simpit) within a network.

 

I can reproduce it 100% at any time and unfortunately this makes the LMC effectively useless in its application. To avoid this bug we no longer use LMC.

 

Greetings

T-Bone

 

Edit_1:
Has been listed multiple times as fixed before, but is not the case.
https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.7.12.23362/

https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.7.11.22041/

 

LMC Desync Package.zip 2.32 MB · 0 downloads

 

I think it actually WAS fixed, but was re-introduced in 2.8, along with the related bug where the CPG stores coordinates via the TADS and the location the (desynced) PLT version of the TADS is used to generate the coordinates. 

Posted (edited)
2 hours ago, Scaley said:

I think it actually WAS fixed, but was re-introduced in 2.8, along with the related bug where the CPG stores coordinates via the TADS and the location the (desynced) PLT version of the TADS is used to generate the coordinates. 

Negative, this bug was already present before the 2.8 update.

 

The delayed bug report is due to my lack of time.

Edited by [Eule-22] T-Bone

Main machine: Ryzen 7 5800X3D, 64Gb 3600Mhz, Gainward RTX 5080 Phoenix V1

Second machine: Ryzen 5 5600X, 32Gb 3600Mhz, ASrock 7700 XT

Equipment: microHELIS Bell 206 Pedale + Toe-Brakes, microHELIS OH-58D Collective, DIY FFB-Rhino clone, Realteus Forcefeel, TrackIR 5

  • 5 months later...
Posted

It looks like this bug is back. I see this thread never got any attention from ED the first time around.

Can someone confirm this is being looked at?  It’s not very helpful to have the CPG launching on targets while what the PLT sees in the back is the TADS drifting aimlessly in some other direction.

Would updated track files or a video be helpful here?

Posted
5 hours ago, Floyd1212 said:

It looks like this bug is back. I see this thread never got any attention from ED the first time around.

Can someone confirm this is being looked at?  It’s not very helpful to have the CPG launching on targets while what the PLT sees in the back is the TADS drifting aimlessly in some other direction.

Would updated track files or a video be helpful here?

We noticed in the last patch that we had 1-2 DeSyncs in flight, but thought it had something to do with the internet connection because it worked again shortly afterwards.

I will try to isolate the bug and create a new track file.

  • Like 1

Main machine: Ryzen 7 5800X3D, 64Gb 3600Mhz, Gainward RTX 5080 Phoenix V1

Second machine: Ryzen 5 5600X, 32Gb 3600Mhz, ASrock 7700 XT

Equipment: microHELIS Bell 206 Pedale + Toe-Brakes, microHELIS OH-58D Collective, DIY FFB-Rhino clone, Realteus Forcefeel, TrackIR 5

Posted (edited)
9 hours ago, Floyd1212 said:

It looks like this bug is back. I see this thread never got any attention from ED the first time around.

Can someone confirm this is being looked at?  It’s not very helpful to have the CPG launching on targets while what the PLT sees in the back is the TADS drifting aimlessly in some other direction.

Would updated track files or a video be helpful here?

I can confirm that the LMC and IAT functions are no longer correctly synchronized. Attached are the files of the pilot and CPG places.

Note: It takes me 2-3 minutes to set up everything for the test, so you can see the erroneous behavior only from about 8:03.

Pilot-Seat_TADS-Desync.zip CPG-Seat_TADS-Desync.zip

Edited by [RENEGADES] T-Bone
  • Like 1

Main machine: Ryzen 7 5800X3D, 64Gb 3600Mhz, Gainward RTX 5080 Phoenix V1

Second machine: Ryzen 5 5600X, 32Gb 3600Mhz, ASrock 7700 XT

Equipment: microHELIS Bell 206 Pedale + Toe-Brakes, microHELIS OH-58D Collective, DIY FFB-Rhino clone, Realteus Forcefeel, TrackIR 5

Posted
30 minutes ago, Lord Vader said:

Hi @[RENEGADES] T-Bone

We have some issues with multi-crew sync and I added this to our internal reports.

Thanks

 

Roger 👍,

let me know if more tracks are needed in different constellations.

Main machine: Ryzen 7 5800X3D, 64Gb 3600Mhz, Gainward RTX 5080 Phoenix V1

Second machine: Ryzen 5 5600X, 32Gb 3600Mhz, ASrock 7700 XT

Equipment: microHELIS Bell 206 Pedale + Toe-Brakes, microHELIS OH-58D Collective, DIY FFB-Rhino clone, Realteus Forcefeel, TrackIR 5

  • Wags locked this topic
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...