Jump to content

Current multicrew sync status?


Recommended Posts

Posted

Heya, just wondering if there's a consensus atm. on what works and what doesn't in multicrew properly.

For example in today's session with a buddy we had quite a few issues, some unrelated to the F-15E itself (like FFB issues, which got sorted with a game restart), and I was just wondering whether they were supposed to work or not.

Main ones that we ran into were that apparently no targeting data was being transmitted between the seats, nor were smart weapon targets synced at all.

On our first run at a target I set up 3 targets for GBU-31s from the rear seat using the radar, and got all the targeting cues etc. on my HUD repeater, but the front seater got nothing. Weapons kept saying "NO ZONE" on the HUD, heading tape didn't show where to go, nothing. Eventually I requested control of the plane, dropped the bombs, and gave control back.

Second run we tried to do the "rear seat designates, front seat transfers co-ordinates to bomb" method. I designated two different targets for him, and he uploaded them on his end, but they didn't actually show up on the smart weapons page for me at all, the bombs kept saying INIT. I then set a couple more targets to the bombs he didn't try to program myself, and those showed up as expected. When it came time to do the drop, he got one bomb off, then the system cycled to a station that wasn't even in the weapon profile (profile had just the CFTs, after the drop it cycled to the centerline station, which was already empty). I had to again take over, and drop the rest. Couldn't drop the second one that he had tried to program, since it was showing as INIT for me.

Included images of what his HUD was showing him, and what my HUD repeater was showing me.

image.png

image_2024-01-14_23-06-57.png

  • Like 1
Posted

OK, confirmed that smart weapons that get co-ordinates from the front seat don't sync with the backseat, and vice versa. So whoever sets the co-ordinates into the weapons has to also fire them.

Also saw a worrying thing with regards to navigation accuracy, the front seater's TSD/moving map stayed perfectly aligned, but even on a short flight my TSD on the rear seat went completely out of whack. Some of the bombs also went off target, so I wonder if it's something like the INS drifting badly for the rear seat, not getting updates from GPS, while front seat is OK...

Here's front seat TDS:

image.png

And here's my rear seat TDS at the same time (roughly):

image.png

They're not even in the same area code. And mine kept shifting all the time, this was taken 2 minutes an 3 seconds later (timestamps on screenshots):

image.png

 

  • Like 1
Posted

Maybe you or the WSO changed the PPKS from EGI to MN or INS.
INS and MN are not synched in multiplayer multicrew. This makes impossible to do missions without GPS. Also INS MN updates aren't synch either.

  • Thanks 1
Posted
4 hours ago, Ignition said:

Maybe you or the WSO changed the PPKS from EGI to MN or INS.
INS and MN are not synched in multiplayer multicrew. This makes impossible to do missions without GPS. Also INS MN updates aren't synch either.

Fwiw I'm the WSO, and neither of us know enough about the plane to do that on purpose at any rate, and I'm pretty sure I saw PP-EGI on the UFC during the flight.

Posted

I just remember the TSD has a bug were it doesn't show correctly the waypoints and the background, you need to change the zoom/range on the screen for it to update.

  • Thanks 1
Posted
On 1/16/2024 at 12:33 AM, Ignition said:

Maybe you or the WSO changed the PPKS from EGI to MN or INS.
INS and MN are not synched in multiplayer multicrew. This makes impossible to do missions without GPS. Also INS MN updates aren't synch either.

That's not correct. INS and MN drift/update are synced. Unless there is a recent bug

Posted (edited)
11 hours ago, Kercheiz said:

That's not correct. INS and MN drift/update are synced. Unless there is a recent bug

It's not. Well when you push the update both cockpits update but in different positions. MN and INS are not synchronized.

Both cockpits have their own drift.

Edited by Ignition
Posted (edited)
On 1/19/2024 at 8:55 PM, Ignition said:

It's not. Well when you push the update both cockpits update but in different positions. MN and INS are not synchronized.

Both cockpits have their own drift.

 

I'm sorry, INS and MN drift are synchronized. Updates too.

I'm the developer and I tested again (Using a HRM map cursor UPDATE)

There might be some issues, and if you find some, please document them using a video from both seats.

 

Edited by Kercheiz
Posted (edited)
1 hour ago, Kercheiz said:

I'm sorry, INS and MN drift are synchronized. Updates too.

I'm the developer and I tested again (Using a HRM map cursor UPDATE)

There might be some issues, and if you find some, please document them using a video from both seats.

 

 

Excellent, but there are issues! Me and my friend (pilot and WSO) had a LOT of desync when using MN. Each cockpit had the same waypoint pointing to different locations in each cockpit. We made lots of MN updates but this was always the case. It never got synched. The mission was in 1990, we did a full INS alignment, cold start.

When the WSO moved the TGP I could see where he's waypoint was pointing, the same when I moved the TGP, he could se where mine was looking and it was very far away, like 0.5+ nm. The same waypoint was not in the same place for each cockpit.

If you're flying let the WSO make the update. Cue the tgp to waypoint, move the TGP (only move) and in the other cockpit the TGP display will switch from where he's looking to where your waypoint is.

Sorry I don't have a track. If we can we make one from each cockpit.

"please document them using a video from both seats."

Yes better I will try.

Edited by Ignition
  • Recently Browsing   0 members

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