I just updated from 2019.4.18 to 2019.4.23 because Unity kept asking me to but after I did several assets stopped working. Most notably my player stopped being able to walk and my camera refuses to follow anything, via script or making it a child. Did this update change anything that could potentially cause these issues? I’m heavily considering starting from scratch which is less than ideal
Its hard to answer that question without details. Do you have errors when the game runs? Does it still work if you open it in 2019.4.18?
Are you using source control, did something change when you upgraded?
Hi Karl,
I’ve just updated from 2019.4.22f1 to 23f1 and upon opening my project, all assets were re-imported (which is unusual for that scenario) and the game is displaying numerous issues now.
Upon investigation, it seems a lot of mono behaviours fields (in prefabs) were stripped of some\all of their values. For example, a pickup has a PickupManager class that references (in the editor) a Rigidbody or Audio Source (on the same Game Object) but the fields are now null.
What’s even more odd is that GitHub is reporting only one change, that being the usual ProjectVersion.txt file.
So is this a prefab\editor issue?
Can you file a bug report?
Hi Karl,
Apologies, but not immediately.
A game of mine has just gone into beta and I’ve hit a show stopping Unity IAP \ MS Store issue. So I’m dealing with that right now. I probably can in a few days time. So sorry.
1 Like
Scratch that… I’ve logged it. Seems quite a fundamental issue, so thought it was warranted. Quick and easy to log as well. Good luck!
1 Like
Same here, waiting for it to finish now to see if anything is broken.
This smells like maybe you just need to reimport all, if there really were no other changes.
Nothing broke as far as I can tell, only the post processing package was still outdated while it would be updated to 3.1
1 Like
Thanks Kurt.
That may well be the case. But Unity already ran one by the looks of it, which is unusual in itself for a minor update.
Given that the editor was indicating fields had been null’ed but GitHub was reporting no deltas to the associated files, I’m guessing it’s a prefab and\or editor issue.
I’m up against at the moment, so will try again with 23f1 next week and see if I can re-produce.
For most people who don’t have a lot of experience in the software industry, source control seems like an unnecessary hassle. But this is a prime example of why it is the industry standard. How this situation should normally go is you investigate the issue for a bit, but when you’re bored of that you just use source control to revert your project (or check out an entire new copy of the last revision of your project) and go back to 2019.4.18 like nothing happened. Maybe you lose an hour of your time.
Far less efficient, but still useful, is just making frequent backups of your project. Just create a zip file of your entire project folder. If something bad happens, you just delete your current project folder and replace it with the backup. If you’re doing it this way you should make a backup after making any significant progress, and before making any major change. Changing Unity versions is always a major change, since Unity doesn’t natively support downgrading versions after an upgrade.
But to help you from here, we would need to know more details. Are you getting any console errors? Do you see anything saying a component is missing when you view the relevant GameObjects? When you create a new scene and test these same scripts in isolation, do they function there?
1 Like
The advice you have given here with source control is already more than enough honestly, this is my first game ever and I have no experience or people to teach me.
As for in game the player and main camera prefabs don’t work in new scenes and I have yet to receive any error message for anything. The thing that concerns me is I created a new camera, made it a child of the player, and it still didn’t follow him. It feels like an issue with .23 and my MacBook
1 Like
Hmm, go do that again.
-
Stand here. Look at the camera offset in the inspector
-
Walk over there. Look at the camera offset in the inspector.
How do those quantities differ?
Do you perhaps have TWO cameras in the scene?
This MIGHT be… what happens if you just whip back to 22?
Upon further testing I managed to get it to work as a child of the player (movement speed got reset on the update so it was unable to move), but it still won’t move with the follow target script. Any ideas on why one works but not the other?
Whip out that script and start digging into it: check that all the Inspector fields are what they should be, etc.
Also, give it a run, see what that target script is doing. I recommend liberally sprinkling Debug.Log() statements through your code to display information in realtime.
Doing this should help you answer these types of questions:
- is this code even running? which parts are running? how often does it run?
- what are the values of the variables involved? Are they initialized?
Knowing this information will help you reason about the behavior you are seeing.
Have same problem here. Cant even count how many stuff has been broken. mostly UI, its like 30% of the UI has disappeared or been messed and scripts that never gave a problem before are simply missing…
We are rolling back to .22 , no time to figure out all the details of what the heck happenned. Just letting you know it happened the same to more people.
Regards
Please file bug reports if something has broken .
That’s exactly the behaviour that I experienced post-upgrade.
Are you seeing missing fields on your components (MonoBehaviour derivatives)?
Did you upgrade from 22f1 or an earlier version?
Did you see any deltas in your change control solution (if you’re using ones)?
Karl, 23f1 sounds fundamentally broken to me (under some scenarios) so you may want to consider pulling it. In three years of working with Unity (and mostly weekly updates) I’ve never seen an upgrade break a project like this.
Just reimported all assets and everything seems to be working again fine.
1 Like
Thanks for the update, I’ll try again next week if 23f1 is still available and report back.
Sounds like the forced re-import on upgrade corrupted the library\cache.