I hope this was just a side-effect of the new Unity Hub changes, but maybe they’re moving towards shelving this tutorial project? Either way, it might be helpful to update the documentation to help folks find the Karting assets, or perhaps even the whole tutorial to make it use a more recent version of Unity. If you add it to your assets, you can then make a new project and find it in the My Assets section of the Package Manager, from where you can download and import it. ![]() It took some hunting, but I was able to finally find the Karting Microgame, it’s now on the Asset Store here: Karting Microgame | Templates | Unity Asset Store I am getting inconsistent results with (), but I have to confirm if this is another bug or something else on my side before updating the bug report.The steps in the FMOD Integration Tutorial no longer work for downloading the Karting Microgame, since Unity Hub 3.0 has changed the way things work. Migrating every project to the New Input System for a very basic thing like camera movement is becoming a headache. Not acceptable for a LTS while Input.GetAxis is still on the docs and on the project settings: I understand the classic input was set to be removed someday, but that change should be announced. Many legacy camera movements are broken with this, they just stick to 0 values. I have sent a sample project with a simple Debug.log on that case number. ![]() Input.GetAxis is returning 0 in a lot of frames for Mouse X, Y and scrollWheel. If the bug in a LTS is frustrating, the "solution" is even more frustrating. Can someone else take a time to check it please? Or at least update the documentation to avoid using it completely. So… is the classic input system totally removed? It probably should be fixed, not closed. If you have any other questions, please feel free to contact us. I would recommend upgrading to the New Input System because the issue is no longer reproducible after upgrading. I was able to reproduce the issue but I noticed that you are using the Old Input System. My bug report was closed with this message: CASE IN-47086 I’m slowly replacing them with fbx but there are tons of models, since I trusted the engine would support it… Sometimes I think it would be better to stop supporting blend files in the editor… Almost all huge engine upgrades bring different problems with blend models. I must select all blend files in the project and set the scale to 100.Įvery time I get some problems with blend files inside the project. Scale was set to 1, they appear as miniatures, destroying scenes and prefabs. Since I skipped 2021.x I am not sure if this is totally new.Īlso all my Blender models got broken after the upgrade. On 2022.3 they are returning 0 most of the time. I made a report CASE IN-47086 with a Debug.Log showing the values returned for Mouse X, Y and Scrollwheel. Cannot find in documentation what is changed. All my rotation movements and mouse scroll don’t work after upgrading from 2020.3 to 2022.3. Now the import is done in less than 2 hours! (It’s a huge project with lots of textures). Generally my project needs 6 to 10 hours after updating the engine, since Unity 5.6 up to 2020. One good thing and some bad ones… The good: I love how the asset import process is way faster now. So it's easier to just blame it on the buggy release. Usually you can downgrade such a package but more often than not, analyzing that you are in such a situation and taking the right steps (eg package downgrade) takes some effort. For example between 2021.2.latest and 2021.3.0 you may have the same package defaulting to two different versions, which can cause issues if you're not prepared for that. One thing to keep in mind is that packages commonly install a different version when the minor version changes. Unity.Serialization package for 2021.2 installs an older version which breaks my code, but the version that's compatible with 2021.3 also works for 2021.2 so I'm actually using that even for 2023.1 despite that version still being experimental.2021.3.0 through 2021.3.2 (= just three patch releases) do not have a Type defined that Visual Studio and Rider plugins rely on, so I cannot test these particular versions without downgrading both of these IDE packages.So far I haven't noticed anything out of the ordinary EXCEPT for two things: That's five different major/minor versions (will now be six). ![]() Click to expand.I have been running automated builds and tests, as well as manual tests, with Unity versions 2021.2 through 2023.1 typically using the patch 0 release and the latest patch release of each minor version.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |