Unity 5.0 RC1 is now available for download: Unity 5.0
Please report bugs as usual: http://unity3d.com/BugReportingFAQ
For those needing alternate download choices vs. the download assistant, here are the links to individual component installers.
Windows:
Unity Editor (64-bit)
Unity Editor (32-bit)
Webplayer
Standard Assets
Example Project
OS X:
Unity Editor
Webplayer
Standard Assets
Example Project
Anyone with heavy audio-based project I advice you to stay on b22, there’s a simple bug that makes Audio.PlayOneShot to work only once per audio clip. I’ve already reported the issue and they have said the issue is likely to be a known issuse, case number [670601]
Thanks for the offline links! downloading now.
Hi!
Just to let you know because I don’t know if this is a bug or only an error in my project:
I’ve updated from Beta 14 and I had SampleAssets folder that I’ve deleted to import the new “Standar Assets”. I’ve imported first Effects package and then Utility package. When importing Utility I’ve these two errors:
Error importing folder (The GUID f030ca9293dfc164c8bc07b982e19f38 is already mapped to Assets/Standard Assets/Effects/CrossPlatformInput/Prefabs. But the meta data wants it to be mapped to assets/standard assets/crossplatforminput/prefabs)
Error importing folder (The GUID 4c4bc148459cd764dbb1d4e94e49299b is already mapped to Assets/Standard Assets/Effects/CrossPlatformInput/Sprites. But the meta data wants it to be mapped to assets/standard assets/crossplatforminput/sprites)
Best!
More problems after updating:
I can’t open any Animation Controller made in Beta14… I’m having this error:
IndexOutOfRangeException: Array index is out of range.
UnityEditor.Graphs.AnimatorControllerTool.OnGUI () (at C:/buildslave/unity/build/Editor/Graphs/UnityEditor.Graphs/Animation/AnimatorControllerTool.cs:721)
System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[ ] parameters, System.Globalization.CultureInfo culture) (at /Users/builduser/buildslave/mono-runtime-and-classlibs/build/mcs/class/corlib/System.Reflection/MonoMethod.cs:222)
This early RC1 scares me … (much to do in terms of Enlighten GI static baking still …)
Exactly my thoughts. I am wondering how did they do this demo with the lighting, when no one else can seem to get it working? Was it a BS demo?
I’ve managed to get Enlighten to work properly… took some finessing but I got it working 
Yeah already RC… 
I haven’t managed yet to get the lightmap baking to work even half as well or fast in any of my projects as it did in Unity 4. Is it even possible or is it already known fact that baking will take 3-5x longer than it did in U4 regardless if you are using terrain or not?
I’ve tried to keep up with all the lightmapping threads for tips and tricks but I still find the speed unusable compared to the old. If it’s about the correct settings then there should be at least some quickstart guide to get decent results as trial and error is dead slow.
Well, let’s hope they can fix it before release. Otherwise I can’t image the shitstorm that’s gonna hit the forums.
Well that’s a problem then isn’t it? If you have to finesse to get the enlighten to work, where the other system, just worked…
From my perspective this release seems time-boxed rather than quality-boxed at this point. Could be mistaken here, but certainly an RC1 seems early to call. The Betas were early to call also so it could just be a different approach. At the end of the day it just matters what gets shipped out as Unity 5.0.0. Fingers crossed.
I guess the target release date is around early next month so that they can announce it at GDC
Actually, I should clarify… I finessed it to my liking in my test scenes
The pessimist in me leans toward this. Having said that, there have been a few replies stating some things were fixed for Beta/RCs beyond the one coming up. So, they probably have a lot more fixed than we are aware of and have estimates on the showstoppers they know of at this time. Time will tell.
Actually, the new RC1 breaks A LOT of scripts… even ones that belong to Unity. 
Such as?
All of them… I have post fx and none of those compiled… I am going to run RC 1 again and hope that fixes it.
I have the Standard Assets with Cameras, Characters and Effects in my project and do not see any compilation issues. Those were the Standard Assets that came with beta21 I believe and I haven’t even updated them for RC1.
Same here, except I probably updated them with beta 22 just in case something had changed. So yeah, no script problems here with RC1, including a number of 3rd party asset store items I am using.
It would be quite handy to know when changes have been made to standard assets between Unity releases, especially as I have customised a few of the scripts, but I’ve been able to cope so far.