Unity 5 RC1 Beta available to Closed Beta community but not to Pre-Order Beta?

If so, then why the discrepancy? There's several issues that I've had with Unity 5 that I'd personally love to be able to try to reproduce with the release candidate.

 

whoa! RC1? i haven't seen anything about this and can't find any more information. Where did you hear there is an RC being tested?

 

be patient.. it will arrive in a few days, they just have to make sure there aren't any ship-stopping-undetectable bugs...

 

It's always taken a few days. Calm your tits and insert other similar phrases every single beta did this.

 

There are some issues with Mac + Linux builds plus Audio Fading out between b14 and b22. I was very happy with b22 until i found out about Mac and Linux not working properly. If necessary i can provide builds for both versions of the game.

 

Report it with the bug reporting tool, stop spamming the forums.

 

You know what, forget it... last time i reported anything here... idiot.

 

I understand that, I've been a professional developer for 10 years, i understand beta's and alpha's and am used to companies like Blizzard and Valve who say "It's done when its done." so don't get me wrong when i get excited about it, i'm not gonna be like some people and start shouting "Give Us our release NOW ARGH".

What i'm saying is, they wouldn't be cutting an RC build if they didn't think that it was at least within 6-8 weeks of being released. Which considering the state of WebGL and the looming Chrome updates in April that will Disable all plugins making the web player useless, a lot of businesses would find the fact that Unity is feeling like even taking a look at an RC very exciting. I work for a studio that does a lot of development on Web as a platform to gather data and analytics on projects before moving to other platforms and our most successful game "Adventure Capitalist" is a web-based game. In our daily standup we talk about needing to take 3 weeks to stop feature production and port the project to Unity 5 and WebGL and when is the best time to do that. We don't know for sure, but we need to be prepared for the plugin getting disabled and would rather not fork our repos now and maintain two code bases for an extended period of time.

I'd still like to know where this information came from that there was an RC being tested. From the title of the thread it sounds like the OP isn't in this closed beta, but heard about it from someone, so is that person a part of this closed RC beta and there is an NDA so they can't confirm or deny it? or was there a forum post somewhere? did Unity blog about it and I just haven't found it?

 

This post has absolutely nothing to do with this thread, please take your discussion to the thread already discussing this topic.

 

Doesn't really answer my question. I don't understand why the discrepancy. Practically a great way for Unity to make sure there aren't any last minute issues that would require a re-issue of an RC is to have a broader audience use it, for example those pre-order Beta customers who could benefit from and verify improvements such as those recently made to terrain baking performance. No time like the present. The sooner the better.

 

oh god... what have i done...

 

@Shkarface Noori you raised awareness. Oops.

 

Seriously they're on RC already? That's way sooner than I expected. That's good news to me.

 

Must not be the 'real' RC because the splash screen still says Beta...

 

@superpig thanks for the response. Always nice to talk to a Unity peep. Firstly, I manage my projects under Git source control, best practices and all that, so if on the upgrade to the new Beta it all goes belly-up, well guess what, that's what 'git revert' is for. Secondly I consider my bug reporting to have a high SNR, but I'm biased in that view. But sure, I get how the Open beta is so much broader and more of a 'wild west' for everyone. It's too bad I'm on the other side of the Beta fence.

Good work so far! Each Beta is looking better than the one before. Good direction to be going in.

 

I answered this before in the pre-order access stickied thread.

There's just a delay in our closed beta group delivery and then our updates to be published properly to the web for pre-order access. Nothing more. Sometimes this takes our web group a business day to get to, and that means Friday to Monday.

 

Take your time, i for one what a (nearly) bug free working version

 

It's also much easier to handle obvious bugs when they are caught and submitted by a limited audience rather than have thousands submitting the same bug.

As for timing, I would count on 6 to 8 weeks. Every company has their own release cycle. Not to mention, the bugs found in the RC will affect ship time. The designation of RC just means it is considered close to a shippable state and features are nearer to being frozen. There will likely also be several RCs, not just one.

I can tell you that a couple of my customers have recently submitted bug reports for various reflection bugs in IL2CPP and it's unlikely they are already fixed in the RC, which I haven't tested yet... So don't assume the RC designation means that we are bug free and shippable.

 

Imho its still much too early for RC. Im not complaining, I just see how much bugs ppl still report.
Unity take your time to get solid 5.0 release, please(I think at least 10-15 betas more are needed..)
I know you are under big pressure for faster release, but last thing you want to see is xxx ppl complaining how 5.0 is bugged and unstable ^^