Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice

Question Several ports to pick from when selecting Unity debugger in Visual Studio

Discussion in 'Windows' started by mrCharli3, Jan 3, 2023.

  1. mrCharli3

    mrCharli3

    Joined:
    Mar 22, 2017
    Posts:
    960
    I never used to have this issue, I would just be able to press "Attach to Unity" and it would work, now I always have several ports and sometimes none of them work:

    upload_2023-1-3_13-0-23.png

    Unity 2021.3.13f1.

    How can I identify which port Im supposed to use? Its a pain trying to figure it out every time. Especially since it doesnt always work.
     
  2. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,522
    Are you using an older version of Visual Studio? The dialog should look a bit different nowadays (and would show which one you would want to attach to).
     
  3. mrCharli3

    mrCharli3

    Joined:
    Mar 22, 2017
    Posts:
    960
    Yes, 2017 is the only VS that runs smoothly on my computer.
     
  4. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,522
    Yeah, that makes it tricky. In 2019, we split Unity into several processes and added additional metadata that is broadcast to debuggers so they could display what is what. Unfortunately VS2017 shipped before then and thus doesn't display the extra info :/.

    I find it surprising that VS 2017 runs better than VS 2019 on your machine. From my experience they were pretty similar.

    Have you tried VS 2022? That runs even better since it's now actually 64-bit.