Can't get passed "ConnectingToNewRemoteSession" in Viewing a Remotely Rendered Model Tutorial

David Canepa 21 Reputation points
2021-01-06T11:44:33.277+00:00

Hello,

I have gone through the Viewing a Remotely Rendered tutorial twice, following step by step as instructed and can't seem to get through the "ConnectingToNewRemoteSession" message on the editor to then be able to see the model. I'm aware it says it can take up to 5 mins. The first time I waited close to 20 mins and nothing happened. The second time waited for 10 mins and still wouldn't get passed that stage. The first time I created the project from scratch following every step. The second time I downloaded the Complete Tutorial given by Microsoft to use as a reference and just finished configuring the settings and tried it and still got the same result. It does advance to "RemoteSessionReady" but again it simply stays there. I can't see what I'm missing. I'm using Unity version 2019.4.17f1 and used all the packages and versions recommended in the tutorial. Any idea what could be causing this? I saw in the tutorial that it could be something related with the Update function. I checked my script with the one from the Complete Tutorial version and they are exactly the same. Is it perhaps something related with the credentials? As I have no clue what the difference between "Account Domain" and "Account Authentication Domain" is. I have looked everywhere on my Azure portal and all I could find is the Account Domain but not an Account Authentication Domain. Is there something that I'm missing?

Azure Remote Rendering
Azure Remote Rendering
An Azure service that renders high-quality, interactive three-dimensional content and streams it to edge devices in real time.
32 questions
0 comments No comments
{count} votes

Accepted answer
  1. Christopher Manthei 251 Reputation points Microsoft Employee
    2021-01-14T13:04:15.483+00:00

    Hi David,

    your GPU is a Broadwell (Gen8) based one, we only support Skylake (Gen9) based GPUs and above due to hardware constraints, see https://en.wikipedia.org/wiki/Intel_Graphics_Technology#Broadwell for a list of intel integrated GPUs and their corresponding generation.
    The trace unfortunately does not show this and neither does the log, we will hopefully improve this gap in the near future.

    Cheers,
    Christopher

    0 comments No comments

8 additional answers

Sort by: Most helpful
  1. Christopher Manthei 251 Reputation points Microsoft Employee
    2021-01-12T17:30:53.793+00:00

    Hello David,

    sorry for all the trouble. This doesn't look like it's a firewall issue. This appears to be a problem with the graphics initialization and unfortunately, this error is not very descriptive right now and only surfaces when connecting to the VM.

    1. Can you make sure you fulfill the minimum system requirements?
    2. A trace might have further information that could explain the init failure. Could you create a trace from before the unity simulation is started up the the point of failure?
    3. Are there any other errors / warnings in the unity log?
    4. Do you have another machine with a different GPU to test on and can you give us the exact GPU name you are using right now?

    Cheers,
    Christopher

    0 comments No comments

  2. David Canepa 21 Reputation points
    2021-01-13T18:21:40.34+00:00

    Hello Christopher,

    Thank you very much for getting back to me and for all your help. It is no trouble at all, most likely the issue is certainly on my side and I'm missing something.

    I have gone through all of your steps. I'm pretty sure I do meet all the system requirements. I was missing the new HEVC Video Extensions, but downloaded it and installed it from the Microsoft Store. I then tried again and unfortunately received the same result, and I only have this laptop at the moment. It is an old laptop and maybe that could be the issue. The GPU is an:

    Intel(R) HD Graphics 5500

    There are no other errors in the Unity log except the init error mentioned previously.

    I have created a trace for the last session I tried which you can find in the link below:

    https://1drv.ms/u/s!Ar6Fh_Y0n_uLklKArMPM_BJABsxE?e=iVd1io

    When I clicked play in the Unity editor for the first time I accidently clicked it twice. So it started and stopped straight away. Then started it again and ran normally until it encountered the error. In case at the start of the trace you see something strange.

    In case it helps the Session ID was: 2d7adcfa-026a-4b39-beb9-e1158b5d0bf2

    I hope this helps provide more information and please let me know if you would need anything else.

    Again thank you very much for all your help.

    All the best,

    David

    0 comments No comments

  3. David Canepa 21 Reputation points
    2021-01-15T21:27:56.093+00:00

    Hello Christopher,

    Thank you for getting back to me, for all the help, patience, for looking into the issue, and for explaining what the problem was.

    I'm really sorry that I made you and your colleagues lose so much time on what is an evident overlook on my behalf.

    On a more positive note, I figured since the issue was my laptop, that I could try it on the HoloLens and that it should work. So I built the app on the HoloLens and I can confirm that it does work! It is very exciting and impressive. I really look forward to keep on working with this technology!

    Again thank you very much for all your help.

    I hope you have a great weekend.

    All the best,

    David

    0 comments No comments

  4. Christopher Manthei 251 Reputation points Microsoft Employee
    2021-01-18T15:32:25.713+00:00

    Hi David,

    no problem at all, thanks to you we found a gap in our error reporting which we have hopefully addressed in the latest release: https://github.com/Azure/azure-remote-rendering/releases/tag/2021-01-18
    At least now GraphicsBindingSimD3d11.InitSimulation should return an error in your case that you should be able to see in the Unity console instead of silently succeeding and making connect fail instead.
    Great to hear you got it working on the device!

    Cheers,
    Christopher

    0 comments No comments