Unsure how to go about upgrading? Check out the upgrade guides to help you go from previous Unity releases to Unity 2022.2. For complex productions with a high number of dependencies, find out how our Success Plans can ensure the upgrade process goes smoothly.
Marking a major milestone for Unity, the 2022.2 tech release introduces ECS for Unity, a data-oriented framework that empowers you to build more ambitious games with an unprecedented level of control and determinism. ECS for Unity includes the main Entities package, along with Entities-compatible packages for Netcode, Graphics, and Physics.
Please join us on December 8 for our DOTS Dev Blitz Day , an AMA where you’ll have a chance to ask the Unity team your most pressing DOTS questions!
Please remember that with the tech releases you’re trying out the newest features & tools to help us shape Unity’s development, so make sure to back up your projects before opening them in a new version of Unity. The tech releases are not recommended for projects in production or close to release, for these projects we recommend our latest LTS release. If you encounter any issues, please let us know by submitting a bug report so it can reach our developers.
If you have any questions or feedback related to 2022.2, please feel free to share them in this thread and we will do our best to address them.
The biggest problem I have with it is that it no longer allows you to change the script associated with an Object in the Inspector with Debug mode. This feature is very important for refactoring in a project sometimes. There’s an entry for it in the Issue Tracker here, and it was also reported in this forum post .
I’m getting a new warning popup in 2022.2 when launching my project…the problem is when I click restart as standard user it says it requires elevation…does anyone know how to solve this?
After updating from 2022.1 to 2022.2, I’m unable to Archive my build in Xcode 13.3
I get the following error almost immediately after attempting to archive:
Command PhaseScriptExecution failed with a nonzero exit code
Chmod: /Users/myUser/Desktop/ios-build/Il2CppOutputProject/IL2CPP/build/deploy_x86_64/bee_backend/mac-x86_64/bee_backend: No such file or directory
I had no issues archiving my build in 2022.1. Please advise
I’m assuming this has to do with this part of the 2022.2 update:
iOS: Changed IOS Xcode projects to use the il2cpp executable to compile il2cpp sources, so the Xcode doesn't compile the sources directly. This makes iOS consistent with other platforms.
I’m using Windows 11 Unity to build my iOS project, which I then import onto a Mac OS device (via VMWare virtual machine). I open a new terminal in the project folder and run a pod install command to get the workspace file, then archive. This process has always worked in 2022.1 but now it doesn’t.
I noticed the xCode project is setup differently, with a new target called “GameAssembly” and there’s a script attempting to run on it in a file directory that doesn’t exist:
It’s looking for the C: drive which doen’t exist on this machine. I tried copying over the data file and replacing the file path with the filepath of the data folder on the Mac OS, but that didn’t work either.
How can I get around this, or switch the build settings to what they were in 2022.1?
For the sake of testing, I updated my project to 2022.2.
Now all the scenes which had baked lightmaps look broken/misplaced and full of weird jaggy artifacts and bright spots.
The lightmap textures themselves looked fine, so I rebaked one of the scenes and that seem to have fixed it.
The newly generated lightmap textures look identical to the old ones, so I’m guessing something changed somewhere between parsing the lighting data and applying it to the scene.
I’m wondering if this behavior is expected and hopefully avoidable or if it’s a bug, since if I decide to stick with 2022.2, that would force me to rebake a considerable amount of scenes, which of course translates to a massive waste of time…
The editor is unusable in this version! All the bugs from beta got transfered over, nothing was fixed. Selecting object with script glitches out the entire editor and lowers fps to below 0.2.
Anyone else experiencing this I just confirmed with some admins on the Discord that this has always been an issue, it’s just 2022.2 prompts you about it. Seems to be a similar issue to when they introduced prompts for editor waits. Still, a little warning would have been appreciated as suddenly getting a prompt telling you your PC may be “bricked” is a little worrying lol
On the beta i asked for a way to disable that prompt via commandline or something, without success.
In my case it appears because i’m running my user as the “internal” adminstrator, wich nowadays is considered to be the most dangerous thing in the world, because you can brick your machine by doing the “wrong” thing ( delete what you should’nt delete, mess with your registry, send your bank-account data to god knows where etc… ).
I constantly do such things to bend windows to my needs and am fully aware of those pitfalls. I’m from a generation of nerds, where such knowledge is ingrained that deep that i don’t need another layer telling me those obvious facts, so i have no need for those warnings.
But in the end, i decided to simply get used to this dialog, as i see i’m the guy with uncommon habits nowadays …
For some reason unity hasn’t implemented something to stop things like this from taking unreasonably long, but in my case it was some kind of corruption.
If this is like my issue, deleting the library folder is a must. This was happening to me last month but only on my desktop.
I redownloaded my entire project though, but deleting library was the likely lesson.
I too bend windows for a living but due to the new package manager workflow I realized I was blissfully unaware that if a third party package got hijacked then I would just run unchecked code on my computer with administrator privileges.
I look forward to it
