When first installing Unity, there was no VStudio 2017 version present on the computer, so it ( Community Edition) was installed as part of Unity install process (I remember (at least) one VStudio related combo-box in the Assistant).To rule out any possible doubts, here's a DownloadAssistant screenshot:Įverything is checked, there are 2 items (not very relevant to this case) that are not showing (because the window is not sizeable), but they are checked (and installed). Playing (obviously) also works (needless to say that things are OK in VStudio, no complains from csc), !!!but!!! after trying (and failing) to build, Playing no longer works (reloading the project is the only way to fix it).WebGL build runs just fine (loads in browser) this is the workaround currently used, but it takes ages to complete.First guess was that the tutorial project became somehow messed up, so I created a new one from scratch (a dummy / simple one containing one Sphere having attached a Rigidbody and a C# script that applies forces based on user input), but it behaves the same (this is the project build output in the above image).Googleing and checking the forums, didn't help finding information about this exact behavior:Īs seen on the Build Settings dialog (moved to the right), there are no ( Target Platform or Architecture) combo-boxes allowing to specify build parameters.

For a few days everything went just fine, but then, building for PC Standalone target, stopped working.

Since last week, I've been playing with Unity (5.6.0f3 Community 圆4) on Win 10 (圆4) - using Visual Studio (2017 Community) as attached editor, as Unity 'requires' -, and started with the : Tutorials (first of them). Although it's only remotely related to programming, here it goes:

Unity cloud build added to queue