Holy mother of ****, switiching to newer Editor version

This is the mother of WTFs, I can guarantee you.

I have been working with 4.6.0b20 the whole time until today I wanted to use assets that require a slightly newer version of Unity. So I thought, why not update to 4.7. To anticipate: I also installed Unity 5 with the same problems.

Besides randomly getting new errors like “AABB aabb” or “blabla OnGui() blabla”, I will have booleans RANDOMLY set!

My class CastManager has a boolean called challengeModeOn, which is always true, except you press a toggle, which is also set to true via Editor. I put a Debug.Log into the Start() method of the CastManager and turns out it will be chosen randomly! Moreover, I have a canvas that is always disabled but for no reason will RANDOMLY setActive(true).

Also, some prefabs that are canvases will not show up because their scale is set to 0,0,0 when created. It is 1,1,1 as prefab value.

One of my objects is not found during the Start() method as well, although it is there.

When stopping just after starting without doing anything, I will also randomly get “Trying to remove Text (UnityEngine.UI.Text) from rebuild list while we are already inside a rebuild loop. This is not supported.” or other strange errors that I NEVER got with 4.6.0b20

I installed Unity 5 into a new folder.

Please let me know what black magic is going on here :face_with_spiral_eyes:

Cannot help but a lesson, dont use old beta software for long time…4.6b20 is very outdated now.
Because now your far in development, should have at least upgrade to 4.6 final when it came out.

I was relying on that integrated “check for update” function which seems to not work because it was always telling me I had the newest version.

It doesn’t work. As a developer it’s always been your responsibility to keep tabs on the tech you use. It’s not a steam game.

1 Like

Now after we made this clear, how can I “clean” my project if not even the Unity 5 import/transformation does that properly?

I mean, the bugs I am getting are beyond understandable, independent from the version so I assume some dead bodies that are not related to my code but to the project itself.

Why don’t you download the 4.6.x version that has the features you most want? Visit:

Choose the 4.x button, and download the specific version you need. Once you have downloaded and installed this, use it to load the project you’ve backed up.

It’s not clear to me which version of Unity is causing the problems you described.

As I said, I tried both 5 and 4.6.7

that’s why I assume it has nothing to do with the very version but with something that wasnt properly cleared up and sticks to some binary or sth. No matter what, I can almost guarantee that it has nothing to do with the way I set up things in the Editor or wrote the code.

Did you switch the existing project between the versions or did you use the last backup before your switched versions?
If possible I’d try at least to use the working backup and update that to the latest 4.x install. Otherwise (since I never had these problems) I can only wish you good luck. Hope it works out for you.

I made a backup and then used the existing project

OK, now even my backup is fucked because of the installs.

UI elements get shifted into positions where they just cannot be because of canvas nesting. My UI gets destroyed after I start the game… I think I will have to entirely rebuild my project with the new Unity 5 … man that is so depressing. And all this seriously just because I was about to buy a 5$ asset …

Somehow I am quite disappointed by the severity of the bugs.

This sounds like a disaster, I’m sorry to hear that. Start by trying to narrow down bug by bug. Make a list of them, then work on one until it is fixed, then move on. If you UI is getting destroyed on start? Put in some breakpoints in Visual Studio to find out where it is getting destroyed. Or, maybe it isn’t even getting destroyed? Maybe it is just off screen, rendering issue, or maybe a pixel render issue?

Unfortunately upgrading to a way higher version probably will cause anyone issues. It’s a given that there will be outdated code, or depreciated methods.

The only way to fix your issue is to start debugging and find these nasty bugs that are ruining your world, best of luck.

This is what I’d do:

a) Load your backed up project in 4.6.0b20. Everything should just work. It’s not ideal because you have some Assets that you’ve bought that don’t work in that.

b) Download 4.6.7. Load a copy of your duplicated 4.6.0b20 backed up project into this Unity. Once it’s loaded save it, restart, and then see what happens.

c) 5.x. Leave it for another day.

So, my assumption is that the duplicated version for 4.6.7 will have a few problems, so post them clearly here and someone will try and help.

Thanks for your help so far, I appreciate it.

I really tried my very best to find out what is going on and how I can migrate my 4.6.0b20 project to Unity 5 but right now I can’t move forward nor backward.

First up, so far I don’t use any assets that require a version newer than 4.6.0b20.

If I use the old Unity 4.6.0b20 again with my old project in the state of the backup, randomly after playing a child canvas of my most important canvas will shift all its children. When leaving play mode, this shift will actually persist! I have never experienced that before installing 4.7 or 5. That is, I cannot use 4.6.0b20 anymore.

ad b) I did, turns out it gives me these kind of bugs.

So I want to look forward and use Unity 5 (or at least 4.6.7)
There, the editor doesn’t even show me graphical elements randomly. When selected, I can only see the anchor positions and size of my elements but there is no graphic. But not for every element, just for the most important ones -.-

So I try to summarize the bugs once more:

  • when using 4.6.0b20, 4.6.7 or 5.x
    I have different canvases. One of them (ArenaHUD) contains another canvas (stats). Every element in this stats canvas will be shifted so that it has its center in the middle of stats. But this only occurs randomly when playing. After I end the play mode, the shift persists (how is that even possible?).

  • when using 4.6.7 or 5.x
    In the window in which I shift the anchors, I won’t see any element of the stats canvas

I may notice as well that the button (where you can actually click) is still where it should be! So I can click in the top left corner, although the graphic is in the middle of the screen :face_with_spiral_eyes:


I was able to find out that the “no UI components” is a known bug: Unity Issue Tracker - [SceneView] UI no longer renders in the Scene view

Wow, can’t believe such a major bug persists over so many versions.

The UI bug does reportedly exist in both 5.1.2f1 and 4.6.7 but
NOT in 5.0.2p4

It seems there is no version after 5.0.2p4 that doesn’t contain it. So much on “keep tabs on tech you use” and “don’t stick with beta software” :wink:

I’d rather go with less updates per month than this sort of major bug.

Too bad the “I will shift a canvas into the middle” still exists in 5.0.2p4 … god
Right now there is no version that I can use! And I tried 4 already. This is really bad guys, really bad. Every version I tried since b20 will not work for me because of a major bug. God I feel bad :frowning:

Honestly, the saga of this bug internally is a long and harrowing one… let me do some investigation and see what the current state of it is. I believe it only affects upgraded projects at this point.

The UI elements shifting does not sound familiar to me, though. Can you report a bug, or make a screen recording of the behaviour, or something, so I can see exactly what you’ve got set up and what it’s doing?

Now I upgraded to the new 5.2.0f3 version but still have a bug that is very similar to the described behavior.

I create an entirely new project and scene, create a canvas with a sub-canvas and set the anchor points. When moving the sub-canvas, the UI does not update the image but only the boarder frame. Only when clicking something like the pixel perfect checkbox, it refreshes. This makes this version entirely unusable for me.

Sorry I didn’t have time to extract the contents of my project so you can reproduce. But maybe you can try what I just described and see if you can reproduce? So the actual images does not move when I move the canvas by hand, only the blue boarder.

This sounds like a simple to reproduce bug. You should definitely create a new project just for this bug and report it!