A Unity ID allows you to buy and/or subscribe to Unity products and services, shop in the Asset Store and participate
in the Unity community.
Discussion in '5.3 Beta' started by sanpats, Nov 30, 2015.
Will we get 5.3RC3 today? I eager to test it.
i think RC3 will be the official release.
If it's an official release, it wouldn't be called RC3, no?
It'll be out on 8th Dec as planned. I doubt it'll go sooner, no point. So I'd expect an RC3 myself to be the last/final.
Then a flurry of bugfixes before everyone vanishes til Jan
Then a flurry of bugfixes before everyone vanishes til Jan [/QUOTE] hopefully around performance
5.3.0f3 is still being tested. We're seeing if it's our final version. If so, the proper publishing time (vs. beta release) and other details will have it show up on the scheduled date, Dec 8.
Usually makes that not a bug fix but a performance improvement. And from experience, performance improvements often yield new bugs....
when is Unity going to get some performance improvements? Do you know?
I don't think it makes sense to talk about general performance improvements, you have to be specific.
Animation, physics, rendering, GUI
Here is a screenshot of the profiler.......
can the legacy animations system get a performance improvement?
If you find regressions, you can submit bug reports, such that Unity can have a look at them and hopefully resolve the issue. This would help e.g. here:
According to your stats, you seem to spend quite some time to print strings to the console. If you have issues like that, it may be useful to resolve them first, before you ask Unity to optimize their product for your game.
Indeed, though recently we added:
(Stack Trace Logging) and associated API here: http://docs.unity3d.com/ScriptReference/Application-stackTraceLogType.html
That might help a bit first.
Ok I did not know that... Debug carried over into the game build, when its not even useful,in compiled game
Although if you use a decent IDE it's pretty trivial to find them all. While I think Unity should strip for release builds, I'm not sure about development standalone builds.
There are reasons to have Debug.Log in release builds, but if you don't want it, turn off "use player log" in the settings.
Sure it would. Well, technically "f3" using Unity's naming system. So, 5.3.0f3. 5.2 was released as 5.2.0f3 since the third RC was the final build.
Here is the Profiler logs for my project (removing debugs somewhat helped)
Also where could I have someone take a look at this? (what forum or member?)
Just make a logical post in the correct forum for the issue you're having?
But I didn't ask specifically about 5.3.0f3, I asked about whether there will be RC3 on Monday night, before the final release on Dec 8th.
I'm not sure what you mean. The answer to your question, "If it's an official release, it wouldn't be called RC3, no?" is "no". It will be called RC3/f3. They always have been; sometimes RC1 is the final release, sometimes RC2, sometimes RC3 (not sure if they've ever gone past RC3).
I think there's hushed whispers of f4
What I understand is: 5.3.0f3 can be a final release. If it's decided by Unity to be a final release, f3 will be called final/official/stable release. If it is not a final release, it will be called just RC3. A Release Candidate is not a stable release by definition, it's a beta with potential to be selected as a stable release. So the question is whether there will be RC3 as another RC before the stable release on Dec 8th. Which I've already got the answer that it's still deciding by Unity.
No, that's not how it works. If RC3 is the final release, then nothing changes. It's called RC3 in either case. RC stands for "release candidate". If they didn't think it was possibly ready for release, it wouldn't be called RC.
If f3 is selected as a stable release it will not be called RC3, or at least no longer. The build will be exactly the same. A release candidate is, as you said, possibly ready for release. But when it release as a stable release, it is not called RC. This is how they taught me in my college (if I'm not misunderstand my teacher), and the definitions I found on internet seem to support it. As I understand, this is industry standard definition, casual using of the term excluded. I don't know if Unity using it differently in-house, but I don't believe so. Nevertheless, it is possible that I'm wrong, but I already got the answer that RC3 will not be release yet. I don't want to continue this further.
Good because some of us have been on alpha/beta for years and are quite familiar with Unity's naming scheme and general behaviours, not least because it's been explained multiple times by Unity staff, so yes you'd be wrong.
Every company does it a little different with it's own quirks. If your teacher doesn't realise that, then it's the teacher's fault. It's not an important discussion anyway so I wouldn't worry about it.
No. It's called "legacy" because we are doing no further development on it - no new features, no new performance improvements, and only critical bug fixes.
So looks like the final release on Tuesday? as per roadmap
Bit of topic not sure who to ask, but why for the past two month the patch releases been late or not on the correct date. So what was the point of the long patch plan..?
So, our Sustained Engineering team takes care of the patches and roll ups. I think they try for a weekly, but they also try and hold for various specific fixes here and there that they know are in process.
In addition, for this last month and change we've been upgrading some internal tooling infrastructure and working through some snags. So, it threw some timing off recently (for both patches as well as the betas). I think we're through those bits and being able to operate a little quicker so hopefully that timing instability introduction will go away...
Ok I understand, thanks for the information.
Hopefully in the new year fresh start things will go back to normal and for the better
8th of December - Still planning to release today?
Here too waiting for this update...