I just happened to look at the Hub and saw 2019.3.0f1. Was it just released? I see no posts about it.
3 Likes
For once it’s in the Hub before being announced; it’s a good omen. It’s not even on the download archive page at the time I write this: Download Archive!
And the Hub is getting an update too!
1 Like
It worked out because I was just watching their tank video for UI elements and went to check if 2019.3 beta had any updates.
It is not a full 2019.3 release. Unity names their RC builds with an “f” the same as full releases. But obviously it means this one is darn close.
1 Like
Well damn, that’s pretty confusing. Thanks for the insight!
Well, it’s no longer in the Hub this morning. I should have installed it yesterday… 
The new default font absolutely sucks. The first thing I had to do was change it to Verdana because whatever the new one is called has the worst readability I’ve seen in ages.
1 Like
42 known issues. I figured this would happen after seeing the 2019.2 release and the deadline of this year getting closer, and they’ll sure as hell deliver it again. At least 2019.3 doesn’t have the insane compilation times of 2019.2 (~3x 2019.1).
And oh no, I’d bet my ass they cannot fix even half of those in “a few release candidates”.
Well, 2020.1 alpha 14 works better for me, than the 2019.3.0f compilation-wise 
hmmm… usually, the release candidates were rc tagged…
I’m pretty sure that somebody just messed something up when setting it up for Hub. It’s just RC1 with the wrong tag.
If I recall correctly, it’s not the first time that the first non beta version (0f1) stays in the beta category; the next f1 (1f1) being actually released as “final”.
If I’m right the next 2019.3 to appear in the Hub will be 2019.3.1f1 then.
Well well, I just tested 2019.3.0f1 and, although I like the new font and the new look as a whole (the entire editor is a lot clearer and hurts the eyes far less) I won’t be able to carry on with it; entering and quitting play mode are a pain…
I’ll try 2019.3 later then.
Why is it a pain? Wwhat I’ve noticed is that it fails to recognize internal or external Android NDK - can’t build for Android at all with 2019.3.0f1.
Build with using of [SerializedReference] just crashes. Good release candidate.
Entering and quitting play mod takes forever, like 30 seconds for the first and half of than for the second.
This happens in my project only; I don’t know what to think.
This happens for my one massive project (60GB project folder). For quick projects meant to test out an idea or extract an asset from a larger pack it’s nearly instant. On a 1600X w/ 32GB RAM. Unity 2019.2.
I’m quite puzzled, my project is far from being that huge: 206 mB, Library included…
This is a known issue and the team is actively working on solving it. You can follow the conversation with the devs here:
1 Like
2019.3.0f1 crashes most of the time on entering Play mode whereas b10 did not. The bug reporter does not pop up.