When I try to open my project Unity crashes. Checking Editor.log shows that 2018.1.0b4 is available. But when I go to download it, the latest beta available is 2018.1.0b3.
Seconded. Crashes on startup unless I block Unity’s network traffic.
Unity staff is probably going to ask you to submit a bug-report, following the advice given in this document. If you want to speed things up, it’s probably a good idea to submit that bug-report already and post its case number here for UT to pick up.
Using the bug-reporter seems to be an important step, because it makes sure the report is in Unity Technologies bug-tracking pipeline, has to be processed at some point. Using the forum is often used to add to a little more attention to a bug-report, but does not replace submitting the bug-report.
It’s from advantage to attach a project to the bug-report that UT can use to reproduce the issue and test their fix against. Attaching a video to the bug-report that shows how to reproduce the issue and the issue itself, has been proven useful too.
The easier an issue can be reproduced by QA, the more likely it is to get forwarded to a developer, who might or might not work on a bug-fix for that at some point.
After you submitted the bug-report, you receive a confirmation email with a Case number. UT often asks us to post the Case number in the forum thread, which allows them to find that bug-report if they look at your post.
Following these steps will increase the chance that UT is looking at your issue tremendously.
Happened also before last beta.
I’m seeing this too, clearing out all related files and seeing if a clean reinstall of 2018.1 works. It even crashes on a new project.
I can go back and use 2017.3 just fine. Will submit a bug report after I test a clean reinstall.
The good news is that a clean reinstall of 2018.1b3 on my mac seems to have cleared the issue and I can open projects with the beta again.
The bad news is I have a different problem and submitted a bug report for that, wouldn’t be surprised if they’re related to each other.
Case # is 990956, I get a bunch of asserts for Failed to change file flags.
1 Like
So anyway beta 4 is coming in days?
I saw the beta 3 notice pop up late the other night when working with beta 2, and then it was available the next morning/afternoon (I’m in US PST), so I’d imagine it’s on a server but won’t be exposed for at least until this evening or tomorrow.
1 Like
Unity Beta is a weekly release so expect Beta 4 in Tuesday/Wednesday. (Or maybe even today in a few hours like they did with the Beta 2 release)
I had something similar a couple of times in my test project. Deleting Library folder helped every time.
Looks like I was able to get it to repeat again, even with deleting the Library folder (I am opening the Lightweight shader graph example project to get a baseline).
The workaround for me at least seems to be: Disable Wifi → Open Project → Re-enable wifi → Reimport to force package downloads (which restarts the project opening, but seems to have skipped the download check if the project is already open).
I’ll put in another bug report for the crash after my mac has finished updating some other things, if I can repro it with some log information.
I’ve confirmed this crash again on multiple projects: case #991040
Well, that was fast.
https://discussions.unity.com/t/689279
1 Like
The crash issue should be fixed in b5.