Unity 2022.2 Is Now Available

[Tautvydas-Zilys]

@DanielRiches

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?

I suspect that Unity.exe compatibility properties has “Run this program as an administrator” checkbox checked:

Can you double check this is not checked?

[DanielRiches]

@Tautvydas-Zilys

I suspect that Unity.exe compatibility properties has “Run this program as an administrator” checkbox checked:

Can you double check this is not checked?

Box is unchecked, I am on an administrator account, and I have read elsewhere that installing Unity on a non-administrator account could solve it, but unfortunately thats not an option as I recently changed my hardware and windows now needs activation in order for me to actually customize accounts, and I’m not sure if that should really be the desired workaround as loads of people will have to start making dummy accounts just to use Unity.

Surely selecting “restart as standard user” should just launch Unity in non-administrator mode? but when I click it it just gives a “Needs Elevation” error.

[Tautvydas-Zilys]

Most people will end up installing Unity via an administrator account, that is a perfectly acceptable and default workflow. It shouldn’t cause this issue.

There is a distinct difference between your “account being administrator” and “program running as administrator”. I wrote a more detailed response about it here: Disable "Unity is running as administrator" popup warning

Does this happen even if you close Unity hub and double click on Unity.exe (it will reopen Unity hub - that’s expected)?

In the task manager “Details” tab, you can add a new column called “Elevated”. If you sort by that, it will show you which processes are running as administrator and which ones are not. If you sort by it, you should see that the vast majority of them do not run as administrator. Is that what you see?

Did you ever mess with UAC (User Account Control) settings? What are they configured to on your machine?

[DanielRiches]

@Tautvydas-Zilys

Most people will end up installing Unity via an administrator account, that is a perfectly acceptable and default workflow. It shouldn’t cause this issue.

There is a distinct difference between your “account being administrator” and “program running as administrator”. I wrote a more detailed response about it here: https://discussions.unity.com/t/884400/4

Does this happen even if you close Unity hub and double click on Unity.exe (it will reopen Unity hub - that’s expected)?

In the task manager “Details” tab, you can add a new column called “Elevated”. If you sort by that, it will show you which processes are running as administrator and which ones are not. If you sort by it, you should see that the vast majority of them do not run as administrator. Is that what you see?

Did you ever mess with UAC (User Account Control) settings? What are they configured to on your machine?

Ok a quick update, double clicking Unity.exe does indeed work without the warning, and it does open Unity Hub in the background but instead of just launching the hub it gives me the following prompt:

clicking open project and specifying a project opens with no warning. Unity may want to tweak the functionality on this so it opens the hub normally if it’s installed so you can select your project, if hub isn’t installed give this prompt?

Clicking the X, maximising the hub and choosing the same project then gives the original error again.

[Spellbook]

There is a major prefab serialization bug in 2022.2.

1. Create a prefab with script attached.
2. Open prefab in prefab editor.
3. Reference a GameObject inside the prefab from the script
4. Delete that GameObject from the prefab. (Status is “Missing” on script)
5. Reference another nested GameObject inside the prefab from the script.
6. Hit play. The 2nd nested object will not be referenced.

RectTransforms inside our GUI prefabs are also randomly losing their height and width properties.

[Tautvydas-Zilys]

@DanielRiches

clicking open project and specifying a project opens with no warning. Unity may want to tweak the functionality on this so it opens the hub normally if it’s installed so you can select your project, if hub isn’t installed give this prompt?

It should already do that. I wonder, perhaps the hub is running in a weird way? Can you try to check whether that “Run as administrator” checkbox is checked in UnityHub.exe properties? Is UnityHub running elevated according to task manager? Did you try quitting the hub via the Windows notification area (next to the clock)?

[DanielRiches]

@Tautvydas-Zilys

It should already do that. I wonder, perhaps the hub is running in a weird way? Can you try to check whether that “Run as administrator” checkbox is checked in UnityHub.exe properties? Is UnityHub running elevated according to task manager? Did you try quitting the hub via the Windows notification area (next to the clock)?

Ok, seems Unity Hub.exe had “run as administrator” checked.

It was also running as elevated in the task manager. So ill just untick run as administrator. At least other people should be able to read all this if they have similar problems lol.

Assuming that’s all I need to do, thanks for the help

[Tautvydas-Zilys]

@DanielRiches

Ok, seems Unity Hub.exe had “run as administrator” checked.

It was also running as elevated in the task manager. So ill just untick run as administrator. At least other people should be able to read all this if they have similar problems lol.

Assuming that’s all I need to do, thanks for the help

That’s all you need to do, and likely reboot afterwards.

[newguy123]

In 2022.2 there appears to be a regression with URP 14 when used in conjunction with AR Foundation, in that when building to android, the camera background stays blank/black.

This worked fine in 2021.3 with URP 12 and AR Foundation.

More detail in this thread:

AR Foundation 4 VS 5 & URP 12 VS 14 - Correct VS Black Background

Hi Guys Have an issue here. I simple project with just a spinning cube: Unity 2021.3.1f1, URP 12.1.6, AR Foundation 4.2.3 Build to Android device, everything works fine and great However, either UPGRADING that project, or redoing it from scratch with newer Unity and Packages results in Black/Blank Cam feed, with only the spinning cube visible when building Unity 2022.2.0f1, URP 14.0.4, AR Foundation 5.0.2 Now in 2022.2 AR Session Origin is Deprecated, however even if switching out the com…

[TreyK-47]

@Spellbook

There is a major prefab serialization bug in 2022.2.

1. Create a prefab with script attached.
2. Open prefab in prefab editor.
3. Reference a GameObject inside the prefab from the script
4. Delete that GameObject from the prefab. (Status is “Missing” on script)
5. Reference another nested GameObject inside the prefab from the script.
6. Hit play. The 2nd nested object will not be referenced.

RectTransforms inside our GUI prefabs are also randomly losing their height and width properties.

Hey hey. Could you file a bug report with a repro project and maybe a video? Team is having trouble reproducing following these steps.

[erikbaender]

Is anybody else experiencing insanely long build times in 2022.2? The editor insists on building shaders every time which takes about 25 minutes on my system, even in a fresh project with only the HDRP sample scene. In 2021.3 the first build on the same project takes equally long, but consecutive builds will only take a few seconds.

There also seems to be a sharp drop in performance compared to 2021.3. Using a fresh, unmodified HDRP sample scene again as a benchmark, I get between 20 and 30 percent less performance on average in 2022.2. On top of that builds also have an additional performance loss of around 30 to 40 percent compared to just entering play mode, which is very strange to say the least.

[aimatme]

@CameronDWills

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?

Exactly the same behaviour in xcode 13.4.1 and 14.1
xcode builds are broken by GameAssembly compilation error

reproducing steps:
1 Build unity3d 2022.2 project in windows, get xcode project
2 Move xcode project to macos
3 Build on macos
4 GameAssembly compile error (like on the screenshots of post)

[cchute]

Unity your QA is a disaster. I can’t run this editor for more than 5 minutes without it crashing (new mac). With each update I hope it will get better but it only gets worse. I’ve filed dozens of bug reports. You are making my work day unbearable. We can’t make games built on top of a garbage editor.

[peq42]

woah thats a lot of big eye catching words for a non-impressive update

[mirkoni77]

i would like to use replace prefab feature with new tech stream but it seems that is very unstable, is there any other way of doing this currently in previous version?

[newguy123]

@mirkoni77

i would like to use replace prefab feature with new tech stream but it seems that is very unstable, is there any other way of doing this currently in previous version?

Try this dude’s script:

https://www.youtube.com/watch?v=8xFKYrtM2tE

[Disastorm]

There is a bug with light Culling Masks and Render Layers.
I posted in this thread: Culling Mask not Working correctly in URP 12.0 Unity 2021.2.0b
but I’ll repost here.

Culling mask and Render Layers not working properly in 2022.2.1 for URP.

I tested it in a new project.
These are the results.
Render Layers only works properly in Deferred rendering, it does not work in Forward or Forward+.
Light Culling Mask only works properly in Forward, it does not work properly in Forward+ or Deferred.

So effectively:
Forward: selective lighting can only be done with Culling Masks
Deferred: selective lighting can only be done with Render Layers.
Forward+: selective lighting can not be done in any way.

Also note that this issue doesn’t apply to Directional Light.

[CallMeHerm]

I have found some bugs with the physics system in this update.
rigidbody.MovePosition does not work on kinematic rigidbodies but if I turn kinematic on and interpolation is off it does not work either.
When interpolation is on it does work but the movement is stuttery and buggy.
The same script used in the same project on 2021.3.5f1 worked without any problems.

[MarsCitizen_1]

Ever since upgrading to 2022.2.1, I experience consistent Editor errors.

With an Inspector tab in “Debug” mode, there are frequent errors while navigating between Scene and prefabs in a project.

Also, while in Play mode, if a component throws an Error to the Console Log, attempting to click that row/entry in the log results in the Error shown in this screenshot being thrown, repeating infinitely until I toggle off displaying logs of type “Error” in the Console. This may only be happening if the object that threw the error has been moved in the hierarchy, or disabled/destroyed.

[Lahcene]

Just updated to 2022.2.1f1, now whenever I create a new project
the Unity window stays minimized with a white screen for a few minutes before it opens,
without showing any progress bar. Has anyone else experienced this?