This line can cause problem
GetComponent ().addPlayerUnit (playerUnitObj);
Case: a GameObject through script get component attached , then component have a reference to a non monobehavior object , then component receives a non mono behavior object at a run time and then uncaught exceptions happens and Unity engine crash happens .
Itās neither alpha or beta but it behaves like this. Unity has a serious QA problem but letās not talk about this, because itās outside comfort zone.
Hello,
Was using 2020.3.12f1 LTS version on my project and everything is ok, when i hit any script in my project Visual Studio 2019 16.11.5 start and open all scripts in my project.
Yesterday i see Unity released version 2021.2 so i install it in Unity hub to, copy my project and everything works except Visual Studio, when i hit any script in my project VS open only that script and, can work in the Unity but there is bar in the background:
Things i done already:
Unninstalled Unity entirely along with Hub and Visual Studio 2019
Install clean Hub, both version of unity i mention above and Visual Studio 2019.
Problem remain.
Delete library in project i run using newest Unity version to rebuild that library.
Problem remainā¦
I have been using this package: https://assetstore.unity.com/packages/essentials/starter-assets-first-person-character-controller-196525
for first person movement with 2021.1, but now after going to 2021.2 suddenly the rotation with the mouse was kind of laggy. After a while I found a fix by changing update mode in input settings to āProcess Events In Dynamic Updateā. But I am not sure what exactly has happened here. Has someone else seen this issue?
I think it only happens with this package. Even if you just install it in a new project. But I havenāt done too much research. I only tried some of the Cinemachine samples and they were fine with fixed update mode. But they are all third person controllers.
Also, it just seems to impact rotation, not translation.
Several tool handling and gizmos are not swowing on editor in 2021.2.1f1, like Camera and Directional Lights, or Light Probes yellow gizmos. This was not an issue in 2021.2.0f1.
Is the input lag in the editor a known issue? Iāll be typing values into the inspector and it will lag 1-3 characters behind and even throw tantrums such as not wanting to register enter/return until the editor catches up to fill in the variables. M1 Mac 8 gigs. just running the editor and vs code
I have other thoughts to express right now. How did Unity release such a buggy version for their main platform (Mac), or did I not get the memo that Mac is not the main platform anymore; itās mind-boggling? Sort of unrelated to this version but I reverted back to 2021.1 (the latest versions) after this (and other compatibility issues) and my WebGL project is taking TWICE AS LONG to build with absolutely no significant change to the project, how is this possible?
Hi Unity, @LeonhardP ,
First off, thanks for your hard work. This new version is great!
Iām not sure if this is the right place. But I wanted to report that an issue marked as fixed is not or no longer fixed in 2021.2.0f1 and 2021.2.1f1
Using UnityWebRequest with forced gzip compression does not work in Editor (and presumably Windows builds), but does work on other platforms (WebGL). This makes testing requests in editor quite difficult.
Thanks for the kind words! It looks like the fix was backported to 2019.4 and 2020.3 but not to 2021.2 after originally landing in 2022.1. I have asked the team to look into this.
ok in new 2022.2.1 all of the move tools got into problem and not showing properly.
I found out if we disable Gizmo Toggle in editor they will work fine.