I love using VC as it's small, compact, and does what it needs to without the bloat of the full Visual Studio IDE. A few Unity Answers questions seem to report what I am experiencing, but of course those have no answers.Ĭrossing my fingers and hoping someone has some insight. Googling has been no help as the posts I've found ended up being people with ACTUAL namespace conflicts. Never had this problem before on the old computer, so it's quite difficult to nail down where the blame lies (a configuration in VC? A configuration in Unity? A Windows 10 issue?). The error goes away until later VC decides the currently open script file is again conflicting with itself. My only recourse is to close VC and re-open it by clicking a script in my Unity project. No, the problem is it thinks there are two editors open when in fact only one instance is open, and the conflict it reports is basically with "itself". Basically identical classnames, but the problem is NOT that there are identical class names in different scripts or conflicting namespaces. Here is the problem: Visual Code keeps reporting "Ambiguity between MYCLASS and MYCLASS". Then in November 2018 I upgraded the entire PC, OS is now Windows 10, and I have Unity 5.x, 2017.x, 2018.x installed, mostly using 20 since. I used to run Windows 7 on an older PC, and Unity 5.x, 2017.x. Hopefully this is the appropriate place to find help with this problem I've had every since I upgraded PC:
0 kommentar(er)
