Four blank errors in each new project

[Annundur]

Hello everyone,

I’m a developer but I’m completely new to Unity. I installed it recently and I’ve been watching some tutorials. But I’ve realized that after opening any 2D or 3D new project, four blank errors automatically appear in the Console, and I can’t run the game nor build. These four errors show no indication or info at all, only the hour they showed up (exactly the same time I created the new project). I can’t clear the Console, and double-click on them makes nothing.

If I try to “Build and run” some new info appears in the Console, but I’ve been searching for the error codes and I found nothing.

I attach two screencaptures. The first shows the Console as it is just after creating the New project. The second shows the Console errors after trying to build and run.

I’m working with Windows 7 Home Premium, 64 bits, and Unity Version 2018.3.0f2 Personal. I already tried to empty Unity cache (however it was already empty, as I wasn’t able to do nothing). I also uninstalled and installed Unity again, but I’m having the same issue. While installing, I always choose to install also the Standalone Windows, Android and iOS packs, because I’m planning to develop for these platforms. I already have SDK installed and registered at Preferences->External Tools. I’m using embedded JDK.

While installing, I don’t download/install Visual Studio, because according to a tutorial I’m following, if I’m fine with the MonoDevelop editor included, I don’t really need Visual Studio, and I’d like to skip that if possible, but I don’t know if that could be causing the problem.

I’ve installed Unity in a different hard drive, not the same where I have Windows installed, because I have more space left there, I’m not sure if that matters. I’ve tried creating new projects in multiple locations in both drives, but the errors are the same.

I’ve googled and searched this forum before posting this, but I haven’t found anything that’s really like my problem. If the solution was already out there and I missed it, I’m sorry, and I’d appreciate if someone could link to it.

Any help would be very much appreciated. I’m looking forward to begin in this Unity world, but I can’t do nothing like this.
Thank you very much!

[system]

@Annundur

MonoDevelop editor included

There is no MonoDevelop in 2018.3. It was replaced with Visual Studio in 2018.1:
https://blogs.unity3d.com/2018/01/05/discontinuing-support-for-monodevelop-unity-starting-in-unity-2018-1/

[Annundur]

Thank you very much for your reply, I didn’t know that, I didn’t even get to try to edit any script.

In any case, a while ago I installed it a third time, this time with the full Visual Studio package. However the problem is still exactly the same. I’m thinking of trying an older version of Unity, however this problem is so basic, just after opening the program, that I really thought someone else would have seen it before. Maybe I’ll have to try with Unity 2017 or 5.

[system]

@Annundur

I really thought someone else would have seen it before

Maybe, maybe not, maybe it’s related to some specific hardware-software constellation. You can imagine, this error does not come up just like that for everyone. Otherwise Unity would have solved a long time ago.
Your best bet is to submit a bug report (Help menu/Report a bug) and post the case number you get in the email.

[tutomystic]

I Had this exactly same problem.
I Dont know why,
i used unity othertimes like in 2016 and this not happens

actual vers. Unity 2018.3.0f2

[Noobiezeus]

Help me am also having same problem

[JeffDUnity3D]

Please provide exact steps to reproduce with a new project and the initial settings you choose (3D vs 2D, etc). I’ve seen a few reports of this behavior. I just tested on 2018.3.0f2 and created a 2D blank project, Analytics off, on Windows 10 without issue. Also, please share your Editor logs Unity - Manual: Log files

[liorspidy]

Same problem here…

[system]

@liorspidy

Same problem here…

Then it’s for you as well:

@JeffDUnity3D

Please provide exact steps to reproduce with a new project and the initial settings you choose (3D vs 2D, etc). I’ve seen a few reports of this behavior. I just tested on 2018.3.0f2 and created a 2D blank project, Analytics off, on Windows 10 without issue. Also, please share your Editor logs https://docs.unity3d.com/Manual/LogFiles.html

[system]

@JeffDUnity3D

Please provide exact steps to reproduce with a new project and the initial settings you choose (3D vs 2D, etc). I’ve seen a few reports of this behavior. I just tested on 2018.3.0f2 and created a 2D blank project, Analytics off, on Windows 10 without issue. Also, please share your Editor logs https://docs.unity3d.com/Manual/LogFiles.html

I create all my projects with Analytics off and I have no problem either (Windows 7 SP1 up to date), In case it can help, here are my Configuration settings under PlayerSettings; these are the default settings, I didn’t change them:

No problem either if I switch from .NET Standard 2.0 to .NET 4x (by the way, why isn’t it the default API Compatibility Level setting?).

[insanitymage]

I also was getting the 4 blank errors in Unity 2018.3.0f2 on a brand new project. What ended up working for me, based on looking in the area that APSchmidt suggested, was going to Edit > Project Settings > Player tab > Expanding “Other Settings” and changing the “Scripting Runtime Version*” from “.NET 4.x Equivalent” to “.NET 3.5 equivalent (Deprecated)”.

Unity will prompt you to restart.
Go to File > Build Settings and do just “Build” AND afterwords, select a DIFFERENT folder to do the build to.

I tested again, reverting the Scripting Runtime Version back to “.NET 4.x Equivalent” and I once again got the 4 blank errors. This “Scripting Runtime Version” is definitely the source of these errors for me.

I also fiddled with the “Scripting Backend” version from “Mono” to “IL2CCP” in the course of my troubleshooting, but switched that back to “Mono.” If the above troubleshooting steps do no work for you, you may also try switching the “Scripting Backend” from “Mono” to see if that has any effect.

I also tested this solution with the original project I was having issues with and it seemed to fix my issues there as well.

Before trying to do a build, 4 blank errors:

After trying to build the project (same errors as OP was getting):

My project settings before (these generated the above errors):

My project settings after (these solved the above errors for me):

[Libiral]

Hey, i have the same problem and the solution of changing to .NET 3.5 is working on me.

but i have a question, since there is a warning that it will be removed from future releases, what happen if i continue developing on that setting? and what happened to the end-project if it’s build on .NET 3.5 version on 2019?

is there a way for me using the updated .NET 4.x ?

thank you.

[ratneshpatel]

I am getting the same 4 blank errors with no details about them. Getting sick since last 3 days.

[JeffDUnity3D]

@ratneshpatel The errors are making you sick? That is unfortunate. Did you try the suggestions here regarding the scripting runtime version?

[Joe-Censored]

Not offering any help, just mentioning I saw the same thing. I didn’t try .net 3.5 because my main project I’m looking to upgrade to 2018.3 requires a namespace that only exists in .net 4.x, so I’m holding off for now without an explanation as to what these errors mean (not that anyone actually cares ).

[MajklCZSOA]

Nice. I have the same problem and I see that the solution is not yet.
I try all. Reinstall unity, try get new framework (new and too only v.4.7.1.), new visual studio, plugin to unity VS and too change all option on build…NO FIX. When change to .Net 4x make that nice error with no info (only red time).
Maybe problem in compilation with Win7?

[scarlaxx]

A colleague of mine facing the same issue after upgrading to 2018.3.0f2 and switching to .NET4.x. No change after switching between Mono and IL2CCP scripting backend nor API compatibility level.
So as long as we’re able to we stick with .net 3.5.
This issue seems to be related to Win7 with multiple windows users. Can somebody pls confirm?

[czcrowzero]

But the problem with changing the scripting runtime version to .net 3.5 is that you cannot use Tiny Mode because it’s prerequisite is .net 4x…There’s an error installing the 2018.3.0f2.

[Joe-Censored]

@scarlaxx

A colleague of mine facing the same issue after upgrading to 2018.3.0f2 and switching to .NET4.x. No change after switching between Mono and IL2CCP scripting backend nor API compatibility level.
So as long as we’re able to we stick with .net 3.5.
This issue seems to be related to Win7 with multiple windows users. Can somebody pls confirm?

I saw the issue while running Win 10.

[richardtargett]

Below is where I ran into a problem.

I made the roll a ball before, but now I ran into a problem once I put the camera in place. Maybe its me, maybe its unity.

Hopefully someone will notice the problem we all face, and sort it out, I have the same problem as you all (yes?) not a solution.

Soryr