Pixel Streaming Error After Chrome Updated

Development World Creation
, ,
1

Hi.

When I updated google chrome to version 89.0.4389.72, the below message occurred.

331593-errormessage.png

I have no idea what’s the problem.
Please, let me know how to fix it.

Thank you.

2

Same issue here, need a fix asap!

3

Exact same problem and error message for us as well. Our pixel stream is still working on Chrome 88, which I can verify using a chromebook that hasn’t yet had its browser updated. However, Chrome 89 on Windows and Mac are causing our game to crash.

I have just now submitted a bug using the Unreal Crash Reporter form. We are hoping this can be fixed soon. Our game is currently offline due to this problem.

4

Exact same problem!!! Absolutely crucial for us, it’s affecting production systems.

We solved using Opera (it’s still using an old WebRTC release). But it’s not an option for many of our customers.

Any other workaround???

5

Same problem here!

6

We have the same issue and can confirm that using the Opera browser works as a temporary fix, but we’re still looking for a permanent solution.

7

This answer worked for me:

Link: pixel stream workaround

8

Thank you so much. It works.

9

Hi Peter, Ccdee60,

I don’t know what is happening, but I can’t open the link with the workaround solution.

Would you be able to share it with me another way?

Best Regards,

1 Like
10

Yea it wont open for me as well, do you have the link anyone? I’m looking for a solution

11

The reason is based on contain the ‘a=extmap-allow-mixed’ string in offer string from WebRTC client for pixel streaming plugin. If you remove that string in offer string. it will work well.

The following is the patch code for webRtcPlayer.js in signal web server source code.
offer.sdp = offer.sdp.replace(/(a=extmap-allow-mixed)\r\n/gm, “”);

you can add above code below this line.
offer.sdp = offer.sdp.replace(/(a=fmtp:\d+ .level-asymmetry-allowed=.)\r\n/gm, “$1;x-google-start-bitrate=10000;x-google-max-bitrate=20000\r\n”);

12

Thanks! It worked for my application!

13

This problem is introduced/reintroduced by the new WebRTC/Chrome 94 update that changes the sdp that is sent. Specifically, all versions of Pixel Streaming prior to 4.27 are unable to understand a=extmap-allow-mixed, which Chrome 94 (and the Chrome variants such as Edge) now transmit by default - and which cannot be disabled. In the long term the solution is upgrade to Pixel Streaming 4.27 or higher where we use a newer version of WebRTC.

However, the quick fix for Pixel Streaming <=4.26 is to strip the a=extmap-allow-mixed from the sdp the browser sends (which is the solution the Chrome team recommends). This can be achieved by modifying webRtcPlayer.js, add the following on line 128:

// a=extmap-allow-mixed is passed by default from Chrome 94 onwards, for Pixel Streaming pre 4.27 this must be stripped out as those versions use M70, which has no idea what extmap-allow-mixed means.
offer.sdp = offer.sdp.replace(/(a=extmap-allow-mixed)\r\n/gm, "");
14

Thanks! I can confirm it work for me!
So, with the UE4.27 Is this problem solved?

15

Yes, the whole Chrome 94 WebRTC incompatibility thing is not a problem with 4.27 Pixel Streaming.

16

This worked for us as wel!