Unity 5.0 beta 17 available

Unity Engine
1

Unity 5.0 beta 17 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 which is a work in progress):
Here are the links to individual component installers for Unity 5.0.0b16.

Windows:

32-bit Editor
64-bit Editor
Web Player
Sample Assets
Example Project

OS X:

Editor (64-bit only)
Web Player
Sample Assets
Example Project

1 Like
2

Does this include the fix for the windows licensing? So no more doing the cmd line?

3

Nice change-log, hope Android fixes make it to the next release if needed. (4.6.1 issues and 4.6.1p1 fixes)

4

Yes.

5

Not in the changelogs, fixed stadard shader tiling problem?

1 Like
6

We are doing custom inspectors for arbitrary file types with the following base class:

[CustomEditor(typeof(Object), true)]
public class CustomObjectEditor : Editor
{
    public void OnEnable()
    {
        m_inspector = null;
        string assetPath = AssetDatabase.GetAssetPath(target);

        if(assetPath.EndsWith(".gameconfig"))
        {
            m_inspector = new GameConfigInspector(target);
        }
        else if (assetPath.EndsWith(".tileset"))
        {
            m_inspector = new TilesetInspector(target);
        }

        if(m_inspector != null)
        {
            m_inspector.OnEnable();
        }
    }

    public void OnDestroy()
    {
        if (m_inspector != null)
        {
            m_inspector.OnDestroy();
        }
    }

    public override void OnInspectorGUI()
    {
        if(m_inspector != null)
            m_inspector.OnInspectorGUI();
        else
            base.OnInspectorGUI();
    }

    private ObjectInspector m_inspector;
}

In Beta 13 an earlier this was working fine, but in Beta 15 and later the OnInspectorGUI() method is no longer called, giving us totally empty inspectors. The OnEnable method is still called, though. The bug still occurs in Beta 17.

7

And I have to recompile everything

1 Like
8

Please Unity, make the beta version stable. We don’t want changes in beta versions! [/sarcasm]

3 Likes
9

Well there is something called API auto updater which should update those changes, or atleast a simple note telling us that those attributes changed, because I spent a lot of time figuring out what was causing unity to crash, anyways a beta is a beta and it’s buggy, so I was expecting changes.

10

It sounds completely different if you state that the api auto updater didn’t get them. This means it is a bug.

1 Like
11

Has someone bug reported standart shader tiling problem? Because it still exists…

12

.
Changes are good if they make Unity more professional. I can accept even recompilation of everything (two days for my Unity Project!). However, if changes are made only for changes make no sense. I am glad that Unity 3D is becoming more mature. The 64 bit Editor and better support for multithreading saved my commercial project and I know what I paid for. I hope Unity Technologies will develop their software in a professional direction.

13

It was reported:
http://forum.unity3d.com/threads/beta-16-tiling-does-not-work-on-standard-shader-case-653950.284246/

14

They don’t work so fast. They are busy. I bug reported a problem with Mecanim a few Betas ago and just now, in Beta 17, I see it was fixed. I am really glad.

15

Did they make changes just for the sake of changing something?

Was the development not professional so far?

1 Like
16

It’s my private opinion but I think Unity Technologies is concentrated on attracting as many people as possible, especially young and unexperienced. It’s a perfect tool for such users who have no programming experience. You can download, install and just play. This software is really user-friendly. It’s good because when I opened Blender for the first time, looked at the interface and closed, and then forgot. Great, but I’d like to see the possibility to write in C++, for example, and many other features. But Unity 5.0 changed a lot.

EDIT: Three points are important for me:
1/ More informative log system - I don’t want waste time
2/ Namespaces in the Asset Folder - when you install many packages, there are script conflict. I’m forced to modify some scripts and I hope the authors of them won’t take offense :slight_smile:
3/ C++ - should be faster and consume less memory

17

I kinda agree with Tomza. Every body should accept that unity was not for AAA titles untill unity 5. It was easy to use, user friendly, fast , supports many platform,etc. All these were perfect. However, we(at least I) were really dissapointed at graphics features. But they made a great job in unity5 and I think it is now really good and let us access AAA qualities.

1 Like
18

No matter whether anyone agrees or not, those kinds of comments are just off-topic and not useful for anyone. Everyone is open to create a topic in the discussion section to talk about.

2 Likes
19

Relax, Dantus. I’m installing the new Beta and we will see what the guys from Unity Technologies prepared for us.

By the way, as a author of software you should know that every feedback is precious.

So far, good job, Unity Team! I work on my project with Unity 5.0 Beta and don’t regret that I am not using Unity 4.6. Graphics is amazing, Gokcan.

20

Huger number of errors when I opened the project I had been working on in 16 in 17…

But everything still works.

It’s just that first time opening