Remember to back up your projects before opening them in a new version of Unity. If you encounter any issues, please let us know by submitting a bug report so it can reach our developers.
A big thank you to all of our alpha and beta users who helped to test 2019.3 and gave us feedback while it was in development! Note that we’ve locked the 2019.3 beta forum for new discussions. Please create new threads related to 2019.3 in the Unity Community Discussion forums.
I am concerned it may only work with the now deprecated built-in VR support, and not through the new XR Plugin System released with 2019.3.
There is also a very detailed post on some experiences me and other developers like @fherbst have experience when trying to use new features such as SRP UniversalRP and the New Input System on VR platforms with many issues. We are always reporting bugs for these as they show up but it would be great to see Unity test the latest features such as URP, Input System, XR Management Subsystems and XR Interaction Toolkit together to make sure they do work together properly. For us developers the current state of Unity XR is fragmented in terms of support for newer features we are being encouraged to use.
In the release notes you should put the Android 4.4 requirement next to the iOS 10 requirement change at the top of the notes. Also the removal of x86 android maybe?
Please try to check if multi-view has no problems in Oculus Quest (such as lag issue) and multi-pass has no problem rendering in both eyes which was the case. Thank you.
I second that there are major issues with Unity’s fragmented XR features right now. The current state of affairs actually feels much worse than Unity 2019.1, with many XR bugs, XR incompatibility with new features, XR specific feature churn, and poor documentation.
In 2020, we need to see a unifying vision to bring it all together and some semblance of XR feature stability.
I have a small issue converting a 2019.2 project to 2019.3, when using on-demand reflection probes the workaround that we used for forcing an update was:
Some issues may arise from converting a live project from 2019.2 to 2019.3. As mentioned in the blog:
If you are in pre-production or simply want to get your hands on all the latest features now, you can begin downloading the full release from our update page. For those of you who have projects in production or want to update live projects, we highly recommend waiting for the 2019.4 Long-Term Support (LTS) release. Unity 2019.4 LTS will ship this spring. It will have the same feature set as Unity 2019.3. The difference is that while the TECH stream offers you the latest features and improvements, in the LTS releases we focus entirely on stability and quality. We only add fixes that address crashes, regressions, and issues that affect the wider community. That means Integrated Success Services customer issues, console SDK/XDK issues, or any major changes that would prevent many of you from shipping your game. The LTS release is supported for two years, with biweekly updates providing further fixes, and is intended for projects beyond pre-production.
this is a complete non answer - you’re just confirming it’s happening without any meaningful advice - sorry
@JoWi_Uniform my guess is it was moved out of Experimental namespace
I would actually verify this myself, if I was only not getting “Incomplete or corrupted download file” message in the hub for the fifth time or so (without any option to resume the download, of course - but this is happening after the download progress indicator fills up entirely so… idk)
I upgraded from 2019.2.12f1 to 2019.3.0f6. Now all my terrains are causing the following error: “Unknown error occurred while loading ‘Assets/Terrain.asset’”. Anyone got a solution / work around? Or are all my terrain files going to have to be deleted?
