Comm API broken on XBox

Version: 1.35.21.0

Frequency: Consistently

Severity: Blocker

Bug description:
We employ the new Communications API to communicate between WASM and Javascript. We use it as documented, and it functions well on PC. It does not work on Xbox. Because it does not work, it blocks our Tablet from communicating with the Aircraft.

Repro steps:
In the PC version of our 737 + tablet, the OPT pages work fine. They are sending computational data to the aircraft and receiving results back.

In the Xbox version, OPT pages will not work.

Attachments:
Our aircraft now has a ‘ping’ functionality. It pings the tablet using Comms API and logs this information to a place where it can be read in the cockpit (on the CDU). I am attaching two photos: successful pings on the PC aircraft, and unsuccessful pings from an Xbox version.

pc

Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content

1 Like

@FlyingRaccoon we’re receiving user reports that our tablet, which utilizes Comm API, has recently stopped working on Xbox only. It had been working until a few days ago, and is still working fine on PC. I fear that the latest Xbox update might have interfered with Comm API operation.

It appears to me that the Xbox might have reverted to the old broken behavior that we outlined above. I have a new screenshot (attached) showing the broken behavior we saw in January: PING SENT but never replied. It seems the tablet cannot respond to the C++.

Could I ask for your help on this?

Regards,
Chris P.
PMDG

1 Like

We’re seeing similar issues with our JS/WASM comms pipeline on Xbox…

1 Like

Hi everyone,

Could you please specify which version of the sim is used to run which version of your aircraft? The original bug was reported on 1.35.21.0 but it is unclear to us if latest reports were done with SU14 or SU15 beta.

Best regards,

Eric / Asobo

Thanks, @EPellissier . The issue we’re seeing is only reported on Xbox; PC users seem unaffected. Our understanding is that the Xbox users are running SU14.

Regards,
Chris P.
PMDG

@EPellissier I am on SU14 and issue is there on XBOX

@EPellissier
The issue is on the latest for Xbox, being 1.36.3.