IntelliSense lost when developing with C# for Unity #371
Comments
|
From @VinditCo on December 22, 2015 12:45 I think I have the same thing. Any suggestions on how to debug this? |
|
From @BazIdle on December 22, 2015 13:27 Can confirm the same issue with VSCode + C# + Unity. Omnisharp keeps restarting. This is what I managed to get from embedded developer tools: ("potentially unhandled rejected promise" and "Error: Canceled: Error: Canceled" are looping on every Omnisharp restart) |
|
From @VinditCo on December 22, 2015 13:41 @BazIdle good find. Which Unity version are you on? Figured a downgrade might fix it. I've tried to find previous versions of vscode for OSX with no joy. Any ideas where to find one? (The builds on the Wiki are auto-trashed by OSX claiming they're corrupted - so I have to look elsewhere...) |
|
From @VinditCo on December 22, 2015 13:51 Looks like it ! Like 91 of Workbench causing an issue |
|
From @VinditCo on December 22, 2015 13:53 After this and the disastrous Unity update I'm going to have a new rule: Don't download any software updates pushed during December. All devs are on the egg-nog... |
|
That stack trace is unhappy but won't be the cause of this issue. Can check your omnisharp log (Cmd+L, L) and paste it here? |
|
From @cluo85 on December 22, 2015 14:20 Here is my omnisharp log. I don't know why there are some strange characters. I'm not using any Chinese characters in the directory names and project names. There are only Chinese characters in comments.[INFO] Starting OmniSharp at 'd:\Work\AlienTown\AlienTown.sln'... |
|
From @BazIdle on December 22, 2015 14:24 @jrieken here you go: https://gist.github.com/BazIdle/c1aae81f1fc6d6e0122d |
|
This seems to be an issue with omnisharp. Moving there and see what we can do |
|
By the way, my mono version is 4.2.1 |
|
I'm using whichever mono comes with unity 3.5.1f. Version 2.6.5 I think ? Will downgrading OnmniSharp || VSCode fix this? |
|
@VinditCo Could you try a newer version of mono? Anything above 4.0.1 should be good. Also, what OS are you using? |
|
Sorry, just checked, i have mono-4.0.2.5 installed. Should be fine though, right? Will update anyway |
|
4.0.2.5 should be fine. |
|
Great, anything else you'd like me to check? |
|
I'm running into the same issue, I think. Running VSC 0.10.5, Mono 4.2.1 from a clean install, and I get a number of "[ERROR:OmniSharp.MSBuild.MSBuildProjectSystem]" errors. Seems like the omnisharp compiler is much stricter than Unity's, but doesn't report the line numbers of the errors. |
|
I downgraded to VSCode 0.9.3 newest version found here : https://github.com/Microsoft/vscode/wiki/Previous-Releases And it's working again. Anyone know where I can find 0.10.3 (the previous build to 0.10.5) ? |
|
@VinditCo Just use the "latest" download link and modify to the version you need. Works for OSX links as well (I did downgrade at work, where I use Mac). |
|
Nice! Good thinking! |
|
I'm having the same issue, I didn't find this until now but I believe this bug is identical: |
|
Has there been any updates on this. All current versions of Visual Studio Code (from 10.3 onwards) have this bug. Is there anything else we can do to track it down? |
|
Never mind. Seems like the new version is not compatible with the VSCode plug in (yet). (dotBunny/VSCode#70) Also, intellisense craps out after a few minutes of usage. |
|
@CapnCromulent I don't see any difference with the .10.10 build personally, the issue is still occurring. I believe the changelog is not referencing this issue but rather a speed up to listing the completion results, whereas this issue is with omnisharp hitting some kind of crash in the background and ceasing to work entirely until it restarts. @VinditCo I asked a while back in the iteration plan, and got the response: I think when they move to the new version maybe we will be in luck :) |
|
@Figbash Thanks for the link! I'm having the same problem and this version works just fine. |
|
Just being vocal to let devs know of the spread of the issue. Same here, omnisharp dies after some time on large (400+ files) project. Omnisharp restart helps sometimes; VSCode restart helps always. Extensions version 0.3.7; VSCode version 1.0.0; Unity3D 5.3.4; Windows 8. |
|
It's still bugging out for me on any version of VSCode > 0.10.3. Unity 5.3.3, OSX... Any news on this? |
|
Still same problem with VSCode 1.2.0 & Omnisharp 0.3.3. |
|
There's been more some discussion here : dotnet/vscode-csharp#269 (comment) It seems to be something to do with large projects. Until someone is assigned to fix many of us are having to stick with 0.10.3 |
|
@VinditCo I can confirm that it has nothing to do with project size. Intellisense works for me on 1 computer and not on another (both OSX, both same project). |
|
Still seems to be an issue. |
|
I also have this issue. It works from time to time when I open a project, but shortly after Intellisense is just providing nonsense autocompletion. |
|
I still have this issue... |
|
Me too, on both mac and win. Especially coding some playmaker or behavedesigner scrpit, intellisense does need some 20 or 30 seconds to show up. I guess it's due to dlls.. Because other plugins we used in Unity3d are in form of C# scripts, such as NGUI. It works very well. |
|
I have this issue too.WIN10,Unity,VSCode |
|
having the same in win 10, unity2018.3 and VS Code |
From @cluo85 on December 21, 2015 12:44
The IntelliSense worked fine at the beginning when I started the VS code. Sometimes after I used it for a little while, The IntelliSense would lost.
I have two ways to fix this: One is to type the command "Restart Omnisharp" and I will get IntelliSense again. Most of time this way will work, But sometimes it won't. Another way is to close vs code and reopen it. This way worked every time.
I guess the IntelliSense lost usually happened when I write comments in Chinese. But sometimes it didn't happen. I'm not sure.
I'm using C# language. Windows 10. Newest version of Unity and VS code and dotbunny unity tool.
Copied from original issue: microsoft/vscode#1535
The text was updated successfully, but these errors were encountered: