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
  3. Dismiss Notice

Unity Intellisense Problem

Discussion in 'Editor & General Support' started by mrchrissross, Jul 23, 2019.

  1. mrchrissross

    mrchrissross

    Joined:
    Jun 20, 2019
    Posts:
    9
    Hi everyone,

    So after a while of using VS 2019 I've noticed that two issues are occurring for me, and would love to get some help with. The first is when typing the usual void Update or void OnTriggerEnter() the intellisense should kick in to allow me to auto complete the line however ive noticed that this does not happen.

    Another issue that I'm having is similar to the one above but not entirely the same. Once I've typed out the void function, it is then dimmed with a warning saying that the function is unused. Obviously I never call the function as it is mono-behaviour however there is no getting rid of it.

    I already added VS to the external tools, all of unity's the intellisense works bar this and its so annoying.

    Help would much appreciated, thanks!
     
  2. mrchrissross

    mrchrissross

    Joined:
    Jun 20, 2019
    Posts:
    9
    Tried to post images but was unable as I kept getting a message saying they contained spam... -.-
     
  3. D-Gamez

    D-Gamez

    Joined:
    May 31, 2019
    Posts:
    13
    Hi, I've been having the same issue with OnTriggerEnter() and Visual Studio where it doesn't recognise that OnTriggerEnter() is a built in function in Unity's MonoBehaviour. I believe that VS is having issues between Unity 2019 and VS 2019 and they do acknowledge the issue. I've also been having a problem when I open a script from Unity, Visual Studio wont open it automatically but that's easily resolved by clicking the chosen script on the right hand side under the Assets folder.

    Visual Studio recently released and update on 24 July 2019: https://docs.microsoft.com/en-gb/visualstudio/releases/2019/release-notes#16.2.0

    But they haven't addressed these issues yet with c#.

    I think we have to wait for another VS update until they resolve it, unless someone else knows a fix for it.
     
  4. Nixaan

    Nixaan

    Joined:
    May 30, 2013
    Posts:
    116
    I had those issues today after switching to vs2019 from vscode (vscode's responsiveness is not great lately).

    Initially I had those issues but they were gone after setting Unity/Preferences/External Tools/External Script Editor to VS2019 and deleting the sln/csproj files from the Unity project's folder.
     
  5. particule

    particule

    Joined:
    Mar 27, 2018
    Posts:
    1
    I found that Unity 2018.4.12f1 with vs2019 caused this problem. After I fixed and try to using vs2019, same problem occur.
    My solution is
    1. uninstall vs2019
    2. install vs2017
    3. install LTS Release 2017.4.14f1 (you can test it if the problem was solved.)
    4. using Hub install back to 2018.4.12f1

    ps. But the most large issue is only work in new project.
     
    Last edited: Nov 22, 2019
    elder483 likes this.
  6. PaperBagBoy

    PaperBagBoy

    Joined:
    Mar 17, 2020
    Posts:
    1
    I recently had this problem and was able to find a solution for VS 2019. The problem was that I hadn't downloaded a modification to VS. To fix the problem:
    1) Open VS Installer
    2) Click Modify on the VS 2019 tab
    3) Scroll down until you find "Game development with Unity" and click it
    4) Finally, in the bottom right corner, click modify

    Hope this helps
     
    HawkDriver52, keryxified and patzi23 like this.
  7. patzi23

    patzi23

    Joined:
    Mar 8, 2020
    Posts:
    1
    yes, this works - helped me, thank you! :)
     
    RDR49 likes this.