Unity Patch releases discussion

happy a patching scheme is shaping up!

unfortunately the Maya importer still crashes on Maya 2015 files with this patch..

 

Will it appears Maya don't seem to know what year it is..

 

ya, that is kinda annoying isn't it... i'm working on software "from the future"

 

Awesome initiative!

Unity works well for us, but we usually hold back on upgrading to even minor versions for fear of showstoppers. Oftentimes we're forced to upgrade to the latest version anyway due to platform availability or plugin requirements, and that always felt like a (calculated) gamble for us.

Kudos for doing this!

 

(Web Player user here)
May I kindly ask what those changes are? I can't find any release notes about them...

 

I have a minor question: From what I understand, 4.5 will be the next significant release. What happened to Unity 4.4 (assuming it exists)?

 

It exists and is for console users.

--Eric

 

I can't wait to hear all the ld.so errors

 

I have a question. You, guys, mentioned that you'll be focusing on high-priority, show-stopping bugs that affect a lot of users. But what about the small bugs that are easy to fix but are really low priority.
Like this bug I reported a week ago. If I understand it right, it can be fixed in a matter of minutes, but it's so low priority that it will probably never end up on your TODO list.
Maybe you should select a developer or two, who will go through those annoying, low priority, easy-to-fix bugs and fix them? Or maybe you already have someone doing just that?

 

I hear what you saying dude, I seen this in industry so much, the bug is low priority which to a develop means will not fix, or never gets fixed. Talking from industry experience, we usually had to chase up developers when fixing a larger bug to slip in that little extra work to fix small issue. Depending on the developer assigned it happened or not. potluck

 

as we're still working on 4.3.4 Pro -Desktop- , we are holding our project for the upcoming version 4.5 because so in-core stuff we need to do, and we thought maybe it wont be compatible with the 4.5 version so we're holding on to it until then. all I want to know is are we "STILL" talking days/weeks for 4.5 ?

 

That's why I said "If I understand it right". Not having the source, I've read the docs and tested this module with various values and fps settings. I came to the conclusion that the dampen value doesn't get multiplied by delta time. If that's the case - then it probably can be fixed in a matter of minutes. And yes, I was talking about the actual code as I don't know your procedures.
Anyway, my main point was that there are low-priority bugs that are easier to fix than the majority of the bugs in the issue tracker. I think it would be great if someone from your team would go through these bugs and fix them, because otherwise, they'll probably stay in the backlog for quite some time.

 

I really like this new pace at which the updates are released! Keep up the good work!

 

I'm still confused (maybe discussed before) why the patch releases need to do full installs instead of update files affected by the patch?

Currently using Mac and when I download a patch release it actually makes no difference to me if its a patch release or a full release, because either way I need to install Unity again from scratch?

Have I missed something obvious here?

P.S. of course everyone wants bug fixes even if not related to the project they working on. As one never knows if the project worked on will have hidden compile issues or issues that cannot be spotted easily and finally lets not bring up mobile device performance etc.

Thanks

 

I'm still unclear about the patch release naming convention.

What is the relation between 4.5.1f3 and 4.5.1p1?

• Does 4.5.1p1 build upon 4.5.1f3?
• Why not release 4.5.1p1 as 4.5.1f3 or 4.5.1f4 if the difference is only one day? It's an official final release, not a critical bug patch.
• Is it possible there will be a 4.5.1f4 or do you then bundle the patches into a 4.5.2fX?
  • In case there is a 4.5.1f4 how do you tell which patch builds upon which final release? For example, what would a 4.5.1p3 be? You'd only be able to tell by date and release notes, defeating the purpose of the version numbering.

 

Movra: The change log thread: http://forum.unity3d.com/threads/unity-patch-releases.246198/

 

OK Thanks for your explanation. I will download the latest release posted which has the most bug fixes.

... or the f3 release with the more rigorous QA.

Choices, choices....

 

Thanks for the reply, this make sense to me now and with the previous reply from "QA for life" the picture is becoming clearer. When you mention a patch, I do not think of full installation but more like in app update or a smaller installer which overrides some files in the existing install, if that makes sense.

All is debatable I guess..

 

love the patches, keep them coming!

 

@Graham Dunnett any idea on when the 4.5.2 update will be released as I need to make a decision to either get the latest 4.5.1p4 patch or wait for 4.5.2 (depending on time).

Thanks.

 

Well get them working Graham! Crack that whip!!! Get more Red Bull and pizza! lock the bathrooms until they finish! lol

 

In 4.5.1p4 there's a fix given as "Added preference setting to enable alphabetical hierarchy sorting". What does the preference do exactly, as after enabling it my hierarchies were not sorted?

 

It adds a drop-down menu to the hierarchy panel ( next to the search field ) where you can switch between the newly introduced TransformSort and the legacy Alphanumerical sort.
But the icon disappears in alphabetical sort mode , i guess this is some kind of glitch ?

Previously you had to add a simple editor script to add this menu ...

 

Thanks for that, although it has caused my whole hierarchy to disappear.



And spewed out this error a bunch of times.

Code (CSharp):

1. NullReferenceException: Object reference not set to an instance of an object
2. UnityEditor.GameObjectTreeViewDataSource.SortChildrenRecursively (UnityEditor.TreeViewItem item, UnityEditor.BaseHierarchySort comparer) (at C:/BuildAgent/work/d63dfc6385190b60/Editor/Mono/GUI/TreeView/GameObjectTreeViewDataSource.cs:298)
3. UnityEditor.GameObjectTreeViewDataSource.SortChildrenRecursively (UnityEditor.TreeViewItem item, UnityEditor.BaseHierarchySort comparer) (at C:/BuildAgent/work/d63dfc6385190b60/Editor/Mono/GUI/TreeView/GameObjectTreeViewDataSource.cs:305)
4. UnityEditor.GameObjectTreeViewDataSource.SortChildrenRecursively (UnityEditor.TreeViewItem item, UnityEditor.BaseHierarchySort comparer) (at C:/BuildAgent/work/d63dfc6385190b60/Editor/Mono/GUI/TreeView/GameObjectTreeViewDataSource.cs:305)
5. UnityEditor.GameObjectTreeViewDataSource.SortChildrenRecursively (UnityEditor.TreeViewItem item, UnityEditor.BaseHierarchySort comparer) (at C:/BuildAgent/work/d63dfc6385190b60/Editor/Mono/GUI/TreeView/GameObjectTreeViewDataSource.cs:305)
6. UnityEditor.GameObjectTreeViewDataSource.SortVisibleRows () (at C:/BuildAgent/work/d63dfc6385190b60/Editor/Mono/GUI/TreeView/GameObjectTreeViewDataSource.cs:289)
7. UnityEditor.GameObjectTreeViewDataSource.FetchData () (at C:/BuildAgent/work/d63dfc6385190b60/Editor/Mono/GUI/TreeView/GameObjectTreeViewDataSource.cs:102)
8. UnityEditor.LazyTreeViewDataSource.GetVisibleRows () (at C:/BuildAgent/work/d63dfc6385190b60/Editor/Mono/GUI/TreeView/LazyTreeViewDataSource.cs:95)
9. UnityEditor.TreeView.OnGUI (Rect rect, Int32 keyboardControlID) (at C:/BuildAgent/work/d63dfc6385190b60/Editor/Mono/GUI/TreeView/TreeView.cs:378)
10. UnityEditor.SceneHierarchyWindow.DoTreeView () (at C:/BuildAgent/work/d63dfc6385190b60/Editor/Mono/SceneHierarchyWindow.cs:273)
11. UnityEditor.SceneHierarchyWindow.OnGUI () (at C:/BuildAgent/work/d63dfc6385190b60/Editor/Mono/SceneHierarchyWindow.cs:159)
12. 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)
13.  

 

Yes sure, it's 618335.

 

"We're well into making a 4.5.2p1 release. We've found a fatal WP8 problem which is also present in 4.5.2f1. We've fixed it, but need to do some more QA before releasing it. So the patch will be delayed until tomorrow, Friday 18th July."

Is there any way Unity could give more specific information about this issue (what causes it etc.etc), as it's final days before WP8/W8 competition deadline. We have to know are we affected by it!

 

@Graham Dunnett Why apple and ms don't let us build directly from Unity?

ps.: sorry for the off-topic.

 

Thanks, for fast replay. As i understand it only affects running builds from editor.

 

hey @Graham Dunnett great job

hot thread u have
http://forum.unity3d.com/threads/unity-patch-releases.246198/

i go by it like every day...

best regards!

 

They are unreachable... But thanks anyway!

 

@GarahamDunnett what can we do about bugs that are 'or may be' hardware specific, like in my Unity 4.5.2, when I load a new scene, the hierarchy won't update until I re-select one of the sorting options or create a new gameobject, it happens on three of my PCs, [2x Windows 8.1 x64 Intel HD Graphics Core i5,Window 7 x64 nVidia GTX 660 Core i7], should I create a bug report?