Skip to content

Conversation

@dan-tw
Copy link
Contributor

@dan-tw dan-tw commented May 9, 2023

Relevant components:

  • Scalable Pixel Streaming Frontend library
  • Examples

Problem statement:

We needed a way to differentiate what engine version was being negotiated via WebRTC as their behaviour can differ from version to version. Specifically, we wanted a way to be able to say when we should be sending WebRTC offers from the frontend and when we should be sending WebRTC offers from the instance.

Solution

This PR allows the frontend to receive a custom config message from the signalling server that includes the engine version of the instance that the frontend is attempting to negotiate it's WebRTC handshake with. Using this engine version, we override the flag that tells the frontend whether or not to send the WebRTC offer.

We only send a WebRTC offer from the frontend when the engine version is 4.27 or when it is empty.

Documentation

N/A

Test Plan and Compatibility

Testing across engine versions for both Linux and Windows.

…de an engine version. The engine version is then used to determine if we need to send our WebRTC offer from the frontend or from the UE instance
@dan-tw dan-tw requested a review from david-macpherson May 9, 2023 03:15
@dan-tw dan-tw self-assigned this May 9, 2023
@david-macpherson david-macpherson merged commit 900bcf8 into ScalablePixelStreaming:v0.3.4 May 15, 2023
@dan-tw dan-tw deleted the offer-fix branch June 19, 2023 23:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants