[False] Performance drop when stopping and running the SignalingManager

Unity Engine
, , ,
1

Hey,
Did someone else encounter an issue where the stream stats show a worse framerate of the stream in a scenario where:

  • You call the
    SignalingManager.Run()
  • Then you connect the browser client
  • Call the
    SignalingManager.Stop()
  • Run again
    SignalingManager.Run()
  • Connect the browser client again

In this scenario, the first launch shows the framerate of the stream in the browser at around 130 FPS and after a relaunch, the performance of the stream drops to around 105 FPS and stays that way for any other relaunch.

I had to edit the framerate values of the VideoStreamSender to go beyond 60 FPS but the same thing occurred in the Oculus Quest 2 where on first launch the stream had around 30 FPS then after a relaunch the framerate dropped to around 10 FPS.

2

Is there anyone else that could confirm this or had this type of issue?

3

Updating this thread to make things clear - the issue was internal and related to my own way of hosting the webpage, sorry!