fixed Major descync issues

[FalcoGer]

There are some major desync issues apart from the TSD issue noted in the changelog, making multicrew barely workable.

• ACQ doesn't sync properly, CPG may be on PHS and PLT sees it on FXD for CPG
  • Slaving at that time causes the camera to jitter rapidly between the actual tads position and towards the point it is trying to slave to
• TADS camera is extremely jumpy on PLT side, even when perfectly smooth for CPG
  • Especially in Slaved (even when both sides agree on what the CPG ACQ is)
  • Also especially on image auto track on moving target
• Waypoints don't match
  • Pre-made points when selecting aircraft, such as targets may be missing or different
  • CPG slaving to pre-made point doesn't slave to the correct location (both CPG and PLT see the slave to the same wrong location), even if they both agree on the point's position
• When looking over CPG shoulder to see what his screens are like, all 3 (MFDs and TDU) appeared black.
• Disagreement between pilot client thinking CPG got autopage and CPG not actually getting autopage on his end and then happily pressing buttons can lead to FMC disengage desync.

None of these issues were as frequent or as bad before the last update, though they did exist now and then. Some, like the slaving to a point are new. Other's like the waypoints not matching between cpg and plt were/seemed fixed but now regressed to a broken state.

I'll upload a track when I get to it. The track I got now is 45 MB and very long.

Edited May 22, 2024 by FalcoGer

[Japo32]

Also had to add with Human CPG that I rearmed the helicopter and he saw the helicopter without any weapon, while I saw it totally full.

[FalcoGer]

Add this to the list as well. all routes were completely filled with WP 1 (which didn't exist)

[derfritz]

Same issue here, the aircraft is basically unflyable in multicrew. The waypoints don't get synced, the FCR did not sync properly (was not scanning for CPG, but scanning fine for pilot) and the acq did not sync.

[Raven434th]

Also the CAQ for plt and cpg are not displaying on tsd for BOTH to see on the map at same time

 

[sorcer3r]

 

is there a hotfix for those desync issues planned ?

 

2 hours ago, derfritz said:

Same issue here, the aircraft is basically unflyable in multicrew. The waypoints don't get synced, the FCR did not sync properly (was not scanning for CPG, but scanning fine for pilot) and the acq did not sync.

 

yeah. releasing this patch with new fcr freatures but without working fcr for cpgs is ... uhm strange?

[derfritz]

12 hours ago, sorcer3r said:

yeah. releasing this patch with new fcr freatures but without working fcr for cpgs is ... uhm strange?

Yeah indeed, quite annoying because we had missions planned over the weekend, lots of wasted time for multiple people. I don't know why you would release this patch, they could have released the phantom and patch the apache together with the kiowa in two weeks. Pretty frustrating all around.

[horus-DCS]

When I played 2-ship 4-player multiplayer mission right after the latest patch released, I was a pilot and couldn’t get any target points that were stored by my CPG. And CPGs couldn’t share any data with each other either.

The multicrew experience is seriously broken for now, we need a hotfix ASAP.


Sent from my iPad using Tapatalk

[SkunkOn]

Hello,

I am new to DCS. I love the apache since I was 9, so I bought it and I was very happy to finally get into the simualtion game.

A friend of mine and me were very disapointed about the missing missiles in the gunner seat. It's a very strange experience, when you and your gunner operate from different realities.

Please fix the desync bug as soon as possible.

Skunk

[Guest]

Just had a human player jump in mid-flight as the CPG.  He had no missiles available to shoot (also not on his WPN page) depite the fact that we were carrying them/visible on the pylons. 

[NeedzWD40]

3 hours ago, Gunslinger52 said:

Just had a human player jump in mid-flight as the CPG.  He had no missiles available to shoot (also not on his WPN page) depite the fact that we were carrying them/visible on the pylons. 

This makes me wonder: did he check the WPN utility menu and cycle the MSL option?

Edited May 26, 2024 by NeedzWD40

[SkunkOn]

vor 3 Stunden schrieb Gunslinger52:

depite the fact that we were carrying them/visible on the pylons. 

we tried several times. One time the gunner couldn't even see the missiles on the pylons. The weapon menue also showed the existence of the missiles exclusively to me as the pilot. I launched one, and even that was invisible to him.

[sorcer3r]

1 hour ago, SkunkOn said:

we tried several times. One time the gunner couldn't even see the missiles on the pylons. The weapon menue also showed the existence of the missiles exclusively to me as the pilot. I launched one, and even that was invisible to him.

Can confirm.

As gunner I  can only see weapons if I contact groundcrew for rearming. But you still can get desynced after that.

When I switched from F10 map back into gunner seat I had a short desync .. engine was off and no power on the mfds.

So I rejoined the slot inflight and the weapons were gone again.  This module is just broken at the moment.

[Stewart]

Unplayable right now. Nothing is syncing except the FCR now. The TADS is jumping all over the place as the pilot when the CPG is using it. Weapons are not loading for CPG until they also load them. WP's are not syncing. I set a WP and it will show 40km, but for the CPG it shows over 100km or it will not show a WP at all for them. Completely broken right now. 

[Guest]

 

[Floyd1212]

ED is well aware of what the desync issues are, as the patch notes even say to expect them.

The real question is, when can we expect a fix? What does “ASAP” mean in the patch notes? Is there a hot fix coming, or are we going to be waiting for weeks?

Your most passionate users, members of virtual squadrons that train and fly together as a PLT and CPG team, are essentially grounded right now with a completely unusable module. 

[perryverde]

I SHARE!!!!!

[TonySoft]

Good morning, I find it inconvenient to release an update without the team having noticed the various obvious bugs right away. Hope Fast Solution !!!

Edited May 29, 2024 by TonySoft

[RedBaronsBane]

I fly with Gunslinger52 (above) and as his CPG and as CPG for someone else, as well as and for another regular 2-man team in our Squadron, the CPGs are getting repeated CTDs after no more than 5 minutes.  The pilots are not getting CTDs, just the CPGs.

Before my CTDs, I've had the Weapons desync issues and the Waypoints desync issues (first all routes were fully populated with WP1, and then what I had as a waypoint was about "correct" for me, but the pilot saw it about 50km further away).  I never got to the TADS/FCR desyncs because we C'dTD too often to get that far.

I ended up each time just flying my own single-crew Apache and I'm not trying CPG until it's all fixed because it's not usable at the moment.

There are desyncs that we've all come to live with/workaround, and then there's this release which is fully broken as a CPG.  This is a ridiculous state to push a release out.  I love the idea of the new features, but some are best used with two humans, and we can't use them as such.  Better to make us wait another "two weeks" than releasing something this regressed and broken.

I've flown as a single since the release and while I've not used CPG seat a lot, when I have hopped in there, it appears to be fine, so as far as I can tell, these issues are for multi-crew CPG seat only.

[Ignition]

Many desync issues are present since 2 years.

[sorcer3r]

9 hours ago, Ignition said:

Many desync issues are present since 2 years.

but it was at least flyable before last patch. And rejoining fixed most of the desync issues.... now rejoining cpg makes it worse...

[Guest]

On 5/30/2024 at 3:53 AM, TonySoft said:

Good morning, I find it inconvenient to release an update without the team having noticed the various obvious bugs right away. Hope Fast Solution !!!

 

In defense of ED, they did warn us about the breakages after releasing the two new features.  But why?  Just don't release the new features until they work nicely.  We have waited long enough for them, a few more weeks wouldn't have hurt.  If they are short of testing staff, just say it.  Surely there are dozen's of people who would gladly help them out for free. 

[Raptor9]

29 minutes ago, Gunslinger52 said:

Just don't release the new features until they work nicely.  We have waited long enough for them, a few more weeks wouldn't have hurt.

If bugs occur in the same update cycle as new features, it does not mean that the new features are the cause. Sometimes it has nothing to do with the module itself, it is the nature of evolving software, especially in early access. We have a solid testing team, but sometimes things like this occur and the devs will try to fix them as soon as possible.

As indicated here and on the changelog, we are aware of the issues and are trying to fix it as soon as possible.

[Guest]

Cheers Raptor9,

I wish you all well in getting things going again.  Presume there is a tough balance that you need to find with each release.

What you have managed with C-Scope and Link is awesome.

Have a good weekend.

'52

[SkunkOn]

Thanks Raptor9 for answering here.