Unity 2019 reuined my game.

So i updated to unity 2019, then when i released a patch for my game, the text was missing for the scores, ONLY on IOS devices, and now i cant revert my project back to 2018.3 because of missing dependencies, GREAT! Seriously? any help at all? this isnt even debuggable because there’s no errors.

You can always revert. But if you have done changes to prefabs etc in 2019 these might not work in 2018. So you might need to revert your git history to a point in time before 2019 upgrade. I always recommend doing migration in a branch. And all other work in the standard dev branch. All dev work is done on dev branch and than pulled into migration branch.

The Unity 2019.1.0f2 is completely broken !

First, if you do not have tried it, be ready to lose a complete day for fixing script errors , prefab problems, models problems ect …

This is 3 bug’s already reported before the official release, but they have released the version without fixing them !

UI broken when you assign a sprite by script :

Reported the 3 April !!! Too late???

PlayerPrefs not working in WebGL :

Reported the 26 March !!! Are you serious???

The best one :
Inspector input field is broken :

How you can release it with a bug like this??? really ???

You can’t do anything just because of the Inspector input field bug … just browse here and see how much problems everybody have with this version of Unity : Unity Engine - Unity Discussions it’s incredible …

I have see a lot of bug’s other than the bug’s listed above but i will not fill any report anymore.
We lose our time for them and for nothing.
You can see on all post that they ask for bug report but they make official release without fixing them.

Free for you to share your Unity 2019.1.0f2 experience … maybe someone can show me that i’m wrong …

Have a good day !

The best part is my game won’t roll back to an older version without lots of errors regarding packages and managers, I dont understand why unity releases a new version like every day, why not just take your time and release proper ones that dont completely ruin entire projects? My game is on the store with no text at all what the hell? absolute joke!!

You need to remove the library folder. Or just start over from a new git clone

There are warnings on every step, before updating project.
But surely having backup, before updating, so there won’t be an issue.

4489621--413662--upload_2019-5-1_16-15-19.png

Older version of Unity

4489621--413665--upload_2019-5-1_16-16-33.png

And if I remember, there is at least one more warning regarding making backup, before update.

12 Likes

I have never understood that warning, they should instead warn that the game must be under version control

6 Likes

I have had many issues with updating unity versions mid-project. All the advice so far is solid, but let me just say, unless you absolutely cannot get around an issue and know its fixed in a new version, or the new version offers a feature the one you started the project in does not - do not update during a games development.

7 Likes

You always need to have a branch with latest version so you know what it takes to migrate

2 Likes

They explicitly warn you before updating. The only way to miss it is by being incredibly irresponsible.

8 Likes

I’m sorry but I really can’t believe you posted this. This is one of the most embarrassing threads I’ve ever read.

Firstly, have you never heard of backups? Well of course you have. Just to get to this point you were required to click the “I Made A Backup. Go Ahead!” button that Unity itself pops up. What makes you think that not making backups is anyone’s fault but your own? Unity told you to make a backup, did you think they were joking?

Secondly, Unity 2019.1 is a new features bleeding edge tech release. 2018.3 is a mature release about to move into LTS. Why would you make this jump and almost immediately push out your new builds? It makes zero sense at all. Like every software application ever created, new feature releases are the most likely to contain major bugs. This is not new information, and not unique to Unity.

Lastly, are you skipping QA? How does something like not even seeing the score end up shipped to your users? When you make a change you need to test everything that change touches. When you upgrade Unity itself, and since Unity touches everything, you need to retest everything on every platform.

That’s why no one upgrades their Unity version late in their development, especially after their game has shipped, unless the new version has must have new fixes or features. Because the testing cost alone is so high.

15 Likes

The best part is how you have a live game, update Unity and push out an update to prod with no version control or QC then proceed to tell a bunch of developers on a public forum that you’ve done this incredibly stupid thing and honestly believe you’re not at fault.

The problem here isn’t that Unity did something wrong, it’s that you were completely irresponsible with your workflow.

11 Likes

He cant mean release as realease to production? Release to a test environment maybe?

1 Like

Literally straight published the broken update to users.

3 Likes

I have never seen a thread of this nature created by someone using proper version control. For that matter I can’t remember the last time I saw a thread like this created by someone using just weekly backups.

It’s almost always a beginner thread but we have had a few by advanced users who were too stubborn to use a VCS.

Check his second post. He mentions he released it onto the store and the text in-game is missing. He released his app to production without any testing at all which makes the statement about the game engine needing proper testing hilariously ironic.

7 Likes

Missed that store part in his post. That’s some crazy shit right there.

I think it’s crazy enough not having automated builds with unit testing. This is a complete other level.

1 Like

Hahaha this thread is effing amazing. I hope the OP can salvage even a tiny thread of his ego long enough to realise that the Dunning–Kruger effect doesn’t have to last a lifetime.

8 Likes

Looks like he released it to production. Even my hobbyist, casual, self taught, non professional workflow includes a step where I open the game and play it before deploying it to the store.

You realise the irony of this post, right? You are complaining that Unity doesn’t do enough QC before releasing a product. Yet you have just released your own product onto the store without doing enough QC. Why didn’t you take your time and release a proper product?

I get it, upgrading Unity sucks. But that is something you choose to do.

9 Likes

Instead of a new git clone just use the following command…

git clean -f -x -d

This will remove everything that is not checked into source. (Make sure you close Unity and your coding IDE before doing so)

3 Likes

Well, that’s on the community at least as much as it’s on the OP. Yes, they made a mistake, but who doesn’t make mistakes from time to time?

I hope everyone here realises that we all start somewhere. I definitely agree with telling people to use version control, have backups, and to do QA… but remember that we didn’t come out of the womb knowing those things ourselves! There’s more to learn about this craft than most human beings can fit into a lifetime, so I can’t find it in myself to be upset at someone for not having picked the “version control” skill before running into a problem it could have prevented.

I for one didn’t value it until after I started using it, despite being given pretty much the same advice that I now give others.

@MdevM : Do you have some kind of backup? If so, roll back to before you upgraded and carry on again from there to get a hot-fix in place for whatever is broken right now.

Then, look into version control. It’s a pain in the bum to start using it, but once you’re in the habit you won’t know how you lived without it. I recommend looking at Azure DevOps, as they have free, unlimited accounts for small teams including Git version control. GitHub could also be worth a look, make sure you get a private repo. Get your project into some kind of remote version control as soon as you can, and get in the habit of pushing changes as you make them.

Make sure you read up on version control in Unity’s manual. You don’t want to just shove everything in there.

6 Likes