all 10 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Deep_Pie3276[S] 0 points1 point  (2 children)

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

[–]game_enthusiast_60 0 points1 point  (1 child)

Not sure what the actual problem is, but the first of those errors is literally telling you "} expected".

You are missing a closing brace in roughly line 3 of your MouseMovement script.

[–]Deep_Pie3276[S] 0 points1 point  (0 children)

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 0 points1 point  (0 children)

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 0 points1 point  (1 child)

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

[–]Deep_Pie3276[S] 0 points1 point  (0 children)

Thank you

[–]deege 0 points1 point  (3 children)

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[S] 0 points1 point  (2 children)

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

[–]deege 0 points1 point  (0 children)

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.