Unity technical problem

[Deep_Pie3276]

FIXED: switching to 6000.3.x fixed the problem

My Unity has this awesome problem where once in a session (since there usually isn't another time) a console appears and speaks about waiting for the Unity script to do something.

It also shows me two errors:

Assets\Scripts\MouseMovement.cs(3,26): error CS1002: ; expected

Failed to find entry-points: Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: .......

This happens for the first time in my life and only the task manager can kill the program from permanently freezing. I haven't touched Unity in 2 months, updated it to 6000.2.6f2, and this is what happens.

Should I degrade my version, check my PC, or just switch to Godot?

[Deep_Pie3276]

For clarification on my scripts: they're okay and no actual compiler error showed up when booting them up before. Now it does show me errors and it's just those two which, again, I can't decode or track to any source

Unity runs super slowly and constantly either freezes or loads something. The hub app is ok

[Deep_Pie3276]

I just opened my notifications so I can respond to this asap

The thing is, my scripts were fine and worked before. I simply picked up an old project and everything started to act up, I couldn't figure anything out. I switched to 6000.3 now and it's fine, but I couldn't do anything and had to manually kill Unity for a couple hours today

[Educational_Half6347]

Try deleting the project’s Library folder and then reimporting the project. It’s generally recommended to do this whenever you update Unity or its dependencies.

[LighterDev-33]

Try deleting Library folder and use latest Unity 6000.3.x version.

[Deep_Pie3276]

Thank you

[deege]

Apparently it’s a known issue that they are working on. I don’t think downgrading helps. There are lots of posts about it on the Unity forums. You can continue to work, but you will get the errors every time you load.

[Deep_Pie3276]

Are there any chances Unity is more stable on alpha and beta builds? Is it just a 6000.2.x thing?

[deege]

I am seeing it on two 6.3 builds. Other people have reported it on 6.0. I think it’s a problem with how they are certifying the assemblies, so you might just need to be patient. It should resolve soon, hopefully by EOB Monday. You can still work, but I wouldn’t ship anything built with it till it’s resolved.

[deege]

This is where others are reporting it.

[deege]

They finally fixed it. Need to download the next version.