Can the devs please specify if/when a patch-release is coming this week? Right now I’m stuck with the ‘www.responseHeaders’ null-ref error (when no Internet) and I don’t even wanna touch v2017.3.0b4 with a stick as I’m tired of hax-fixing breaking bugs introduced in every release. Thanks!
4 Likes
I also need this ASAP. UI is eating up all resources.
Hey @CDF
Can you clarify what issues you are seeing? I’m interested to know if I might be affected as well. I was expecting performance gain going from 5.5.0f3 to 2017.2, but so far, I’m not sure I can see anything.
Thanks!
EDIT:
I believe you are talking about this: UGUI.Rendering.UpdateBatches Performance Regression
Seems to be fixed in 2017.3.0b5…
That’s the one. It’s really bad when you have a Content Size Fitter + Layout. I’m seeing about 200kb of garbage generated every frame. And frame rate drops to around 15
I see, we do have Layout + Content Size Fitter, so we are probably (if even if slightly) affected by this issue too.
Can a dev confirm when a patch-release is coming? It’s been 1 month since the UI-bug was detected and still no patch-release? We really need to release an update for our app, but are right now just waiting for the patch.
@LeonhardP status?
Problem is they supporting to many version of unity with patches now, the main version is getting neglected with patch delays, beta versions are getting fixes quicker then the main version…its not best
1 Like
Same, except we need to release our first version. I’m refreshing the patch release page every second. Need this so bad right now
Stop refreshing, just follow this thread: https://discussions.unity.com/t/537849
When he posts, u get notification
3 Likes
Nothing, really? Can we get an estimate, so that I know if we should release a broken update or not? Do you plan on releasing this week, next week, in a month? @P-Jawahar @Aurimas-Cernius
This info is very much appreciated!
EDIT:
“[…] And since the latest version is 2017.2, its patches will be shipped every week.” It’s been two weeks since 2017.2 launched. There should’ve been at least one patch, fixing major CRASH and performance issues, which were known 1 month ago.
We are also desperate for the next patch to hopefully fix an incredible number of issues with 2017.2, all of which have been documented and complained on by others.
Can we at least get a rough ETA on it? I really didn’t expect there to be a 2.5 week (so far) gap on the main release version!
1 Like
Even though the performance sucks big time I’m glad I’m not the only one getting this performance issue. I updated Unity to 2017.2 yesterday and have had nothing but development problems. Seems like every little thing will make Unity performance horrible or crash. Using the editor GUI while in windowed mode makes the game drop to 5 fps. The UI is taking up resources as if everything is using Raw Images being loaded from the disk every frame. In general performance has gone down with no changes to my code. 200 fps in 5.6, 70 fps in 2017.2… it seems with all these oversights and problems that 2017 itself was rushed as a whole! Why does everything feel so unfinished and untested?
I run into these kind of issues with almost every Unity (beta) release as well.
The best thing you can do about it is to submit a bug-report and make Unity Technologies aware of the issue. It’s not a guarantee to receive a fix immediately though.
For example, I found these performance issues during 2017.2 beta, which have been fixed in 2017.3 beta already and should get back-ported to 17.2 and arrive via patch release eventually.
Overall Performance degradation in 2017.2
https://discussions.unity.com/t/677966
UGUI.Rendering.UpdateBatches Performance Regression
https://discussions.unity.com/t/677889
As you said Peter77, the best thing is to submit bug-reports. But the sad thing is, the issues that people are having have been submitted waaaay-back.
Since they knew about these issues, they should have a “KNOWN ISSUES” on the download page of the main release build. It’s so frustrating that we made the leap from 5.5.0f3 to 2017.2 in hopes of performance gain and stability only to find out about these breaking bugs first-hand. I shouldn’t need to scour the web before downloading a release-build to make sure there is no breaking bugs.
2 Likes
To me makes no sense to support Unity 5.5.5p1 - when Unity 5.6.4p1 is out…
Then we have 2017.1.2p2 when 2017.2.0 FINAL (with bugs, still waiting for patch)
So why they supporting 5.5x when 5.6 final is out and still not encouraging people upgrade.
It seems to me they have to many builds happening, 2017.2 final with bugs came out, yet they working on 2017.3 at same time. This is all very confusing, and I think its delaying fixes for people who work on short term projects.
My only thought is internal politics of major “money contributers” are slow with any upgrade and dictate their needs
over indie consumers… Which I guess is how things go in this industry…
Here is a brief description how we approach Unity updates to avoid these kind of frustrations:
https://discussions.unity.com/t/670312/5
Thanks Peter77 for your suggested approach, however, we had to update since existing crash bugs with 5.5.0f3. We probably shouldn’t/didn’t need to jump all the way to 2017.2, but the “gains” were tempting - a devil in disguise.
2017.2 Is the child no one likes to talk about at Unity.
1 Like
I wonder if 2017.3 is the patch release to 2017.2
1 Like
Well there was another beta release for it last night, with nothing for 2017.2, of course! I’m guessing they are waiting for thursday, friday for 2017.2 patch 1. If not, then we may make a serious change with how we view unity.
I feel like there are too many ‘versions’ going on, I see updates all around, yet the current shipping version is 3 weeks out from any updates at all. Not comfortable at all, and if you look for any official notice, you find the “current version updates should be weekly and bets should be every 2 weeks.” So we’ve missed 3 update official cycles for the release version with increased beta releases. It sure feels like .2 was abandoned.
1 Like