Can't open project after installing URP (v2021.3.2f1)

Start importing Packages/com.unity.render-pipelines.universal/Editor/2D/Resources/InspectorIcons/PointLight.png using Guid(b3ab972b21db85d48ade9657efdd4771) Importer(-1,00000000000000000000000000000000)
=================================================================
Native Crash Reporting
=================================================================
Got a UNKNOWN while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

 

First, back 100% of everything up before you proceed any further.

You SHOULD be using source control always, especially if you contemplate changing out entire subsystems like the renderer. If you are not using source control, you have 100% of your project AT RISK AT ALL TIMES. Don't live like this.

Once you have backed everything up, here's some things to try:

- reimport all

- reset / remove problematic packages, then re-add them

- close Unity, remove the Library/ScriptAssemblies folder

- close Unity, remove both the /Temp and /Library folders within your project

- make a new project, add URP, copy all (or parts) of your old project over to it.

 

I get exactly the same error with both 2021.3.4/5 when creating a new URP project. Already created a bug ticket for.

I dunno, maybe it is because I'm using an ancient C2D CPU? The requirements say SSE4.1 minimum which is fulfilled, but maybe someone selected the wrong compiler flag or something. I doubt anyone really tests it on such old hardware.

 

Sure, the issue number is IN-7188

My hardware is

Core2Duo E8200@2.66Ghz
8GB RAM (max. 16GB swap configured)
250GB SSD
GTX 680 with driver 473.47
Windows 10 Version 10.0.19043 Build 19043

I added the export of msinfo32 for more details.

 

Having the exact same problem here. My projects are still stuck in 2020 because 2021 URP just crashes.

 

Basic 3D works, just not URP. I also tried creating a basic 3D project and then adding URP via the package manager, but it crashed again.

 

I'm not the replier, but my issues are the exact same, so I'll say this:

Yes, creating 2D project works on its own. But once you get the URP package, it crashes and can never be opened again.

 

Step 3 and 4 is not possible, as the project Alt-F4's itself during Step 2, and can no longer be opened after that.

 

Creating a 2D project works, installing URP then leads to the same error when importing the PointLight.png.

 

@DavidTeo Any updates on this, sir?

 

It did a complete reinstall and cleared all the data as suggested to me via the bug ticket I created.

Is there a way to debug this from our side? Like attaching the VS debugger to the process?

 

I have also faced the same problem, but I also solve this issue, so I am sharing all of my experiences -

Universal Render Pipeline (or URP for short, formerly LWRP or Light Weight Render Pipeline) is one of the render pipelines available in Unity. It offers varieties of post-processing effects and lighting configurations while maintaining high performance.

To take advantage of all the good stuff in URP, you will have to create a URP Unity project. Or, alternatively, if you want to access the features available in URP in your existing project, then you’ll have to upgrade the project’s pipeline from the built-in render pipeline to URP.
In brief, the steps to install URP to an existing project are: Install the Universal RP package, create a URP asset with the correct renderer based on your project’s type (2D or 3D), set the Scriptable Render Pipeline Settings in the Project Settings to the newly created URP asset, and lastly, upgrade the materials.
Before We Begin
Before we begin, I just want to tell you that, for this guide, I will be using Unity Editor 2021.2.12f1 which is the latest non-LTS official build at the time of writing. The guide should also apply to newer versions of Unity Editor as well.
Install Universal RP Package
First of all, unless your project was created as a 2D/3D URP project from the start, the URP package will not exist in your project. Therefore, you have to manually install it to your Unity project. Basically while doing these I have also faced an error on developing a mobile app development company app by using unity.
Bring up the Project Manager window if you haven’t already. If you can’t find it, go to Window > Package Manager.
Change the packages view to Unity Registry to see all packages from Unity.
Scroll down and find the Universal RP package, or search for it in the search box on the upper right, and then click Install.
Wait for it to download and import its necessary files. This usually won’t take long. Once it finishes installing, we move on to the next step.

Create a URP Asset And Renderer Data
Now that the Universal RP package is installed in your Unity project. You will have to create a URP asset and renderer data.

Version 2021 and newer
Right-click, or click the plus button on the upper left of the project file explorer window and select Create > Rendering > URP Asset (with 2D/Universal Renderer).
You will then be asked to name the URP asset, name it whatever you want. This will generate 2 files for you: One is a URP Asset, and one is a Renderer Data (Universal Renderer Data or 2D Renderer Data).

You can now move on to the next step.

Version 2020 LTS

The type of renderer will depend on what kind of project you’re working with.

• If your Unity project is a 3D project, skip ahead to the “Upgrade Materials In The Project” section as this process will be automated by the Render Pipeline Converter.
• If your Unity project is a 2D project, pick URP Asset (with 2D Renderer).

Pick whichever is appropriate for your project.

Hope this article helps everyone properly.

 

Are you sure we're facing the same problem here? Like we said, we cannot open the project once URP is installed, so it is impossible for us actually boot up the project again to proceed with your suggested fixes.

 

I can't open my project too.
It is stuck at resolving packages forever.

After manually killed the nodejs and let unity report a UPM fail, the project opened.
I reseted the package manifest.
Then during repairing the dependency, I found the problem reproduce after adding URP back.

 

Hi, I am facing the exact same issues. Like some other user I also have an old 2core processor, 8gb ram, opengl3.3 graphics api, macos 10.14.6. Not sure what exact log text to report. I can only add two things to this conversation:

1. I am able to install URP properly on Unity version 2021.1.28, but I get crashes no matter if I first create a 3d core project and then try to install URP package or if I directly try to create a new URP core project from Hub (empty or sample) on versions 2021.3.11+ or v.2022. If I recall correctly and even though a former version than the working one, also the version 2020.3.41 crashed when creating URP project, which is weird.
2. Describing the process of installing the URP package: Unity is in not responding status while compiling c# scripts, after several minutes continues importing elements and somewhere during the step in the image below crashes. Not sure if it's always at exact same file, but timewise is happening around then.

Edit: I just noticed this on the mac's crash report, (while trying on 2022.1.0 version):
Identifier: com.unity3d.UnityEditor5.x
Is this normal?

 

The Unity version is 2021.3.8f1. Video card - AMD RX 590 8GB. Processor - Intel Xeon E5450.
I have the same problem with Universal RP. I load the URP and Unity crashes but the project doesn't open anymore.
The same problem occurs when installing the Terrain Sample Asset Pack - Unity crashes, but the project no longer opens.
I'm hooking up the Unity process twice in VS 2019 to see how the Terrain Sample Asset Pack and URP are loaded.
Terrain Sample Asset Pack throws exception "An exception occurred at address 0x00007FFED705A08B (compress_bc7e.dll) in Unity.exe: 0xC000001D: Invalid instruction.
Unhandled exception at 0x00007FFED705A08B (compress_bc7e.dll) in Unity.exe: 0xC000001D: Invalid instruction."
For URP, almost the same, except that the numbers are different.
Unhandled exception at 0x00007FFED658A08B (compress_bc7e.dll) in Unity.exe: 0xC000001D: Invalid instruction."
After exceptions, the project hangs on import, and the project can no longer be interacted with. I end debugging in BC and Unity instantly crashes.
I will attach the data received from Visual Studio.

 

In Unity 2020.1.0f1, the URP opens and the project does not crash.

 

IN-22034

 

Can confirm crash on importing Universal RP on Intel Core 2 Quad Q9650. My processor has SSE4.1 instruction set but lacks SSE4.2. Unity version 2021.3.14f1 LTS.

 

Start importing Packages/com.unity.render-pipelines.universal/Editor/2D/Resources/InspectorIcons/PointLight.png using Guid(b3ab972b21db85d48ade9657efdd4771) Importer(-1,00000000000000000000000000000000)
Unity version 2022.2.1f1 URP 14.0.4
Core 2 Quad
Ram 8 gb
Direct3D:
Version: Direct3D 11.0 [level 11.0]
Renderer: AMD Radeon HD 6670 (ID=0x6758)
Vendor: ATI
VRAM: 1008 MB
Driver: 15.301.1901.0

 

guys still no fix after a year?

 

Good news, I have a fix.

My hardware is:

Core2 Quad E8200@2.33Ghz
8GB RAM (max. 12GB swap configured)
350GB SSD for OS
2TB SSD for Apps including Unity
AMD Radeon R9 200 Series (ID=0x6810) 4GB VRAM, Driver: 27.20.14501.28009, Direct3D 11.0 [level 11.1]
Windows 10 Version 10.0.19043 Build 19043 64bit Professional

Unity versions I tested and confirmed affected:
* 2021.3.11f1 LTS
* 2021.3.13f1 LTS
* 2021.3.16f1 LTS

However, from the previous reports above, it appears all of 2021.3 LTS are affected at least as far back as 2f1.

The issue:
* Creating a new project and then adding either the URP or HDRP packages causes the editor to quit to desktop whilst importing the URP or HDRP package.
* Creating a new project using the URP OR HDRP Templates fails to load the Editor, causing it to quit to desktop whilst importing the URP or HDRP package.

I noticed for both URP & HDRP, the last line of the Editor.log (in C:\Users\<username>\AppData\Local\Unity\Editor) referred to importing an graphical image file, albiet different images for each package. When importing the URP package fails, the error I get in the Editor.log is exactly the same as the first post in this thread:

Start importing Packages/com.unity.render-pipelines.universal/Editor/2D/Resources/InspectorIcons/PointLight.png using Guid(b3ab972b21db85d48ade9657efdd4771) Importer(-1,00000000000000000000000000000000)
=================================================================
Native Crash Reporting
=================================================================
Got a UNKNOWN while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Additionally, I noticed that there are two Application Errors logged in the Windows Application Event Log

The first event log entry, Event 1000 begins:
--------------------------------------------------------------------------------------
Faulting application name: Unity.exe, version: 2021.3.13.32088, time stamp: 0x635af9f8
Faulting module name: compress_bc7e.dll, version: 0.0.0.0, time stamp: 0x6064b0a1
Exception code: 0xc000001d
Fault offset: 0x000000000007a08b
Faulting process ID: 0x299c
Faulting application start time: 0x01d92cfad4c5a959
Faulting application path: D:\Program Files\Unity 2021.3.13f1\Editor\Unity.exe
Faulting module path: D:\Program Files\Unity 2021.3.13f1\Editor\compress_bc7e.dll
Report ID: b0a699b9-c120-4339-a410-6e30dbfaa053
--------------------------------------------------------------------------------------

The second event log entry, Event 1005 begins:
--------------------------------------------------------------------------------------
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Unity Editor because of this error.

Program: Unity Editor
--------------------------------------------------------------------------------------

The second event log entry is misleading and unhelpful. It suggests running CHKDSK /F on affected drives, which I did on both my drives, and had no effect.

The first event log entry is more useful because it mentioned "compress_bc7e.dll". Searching for issues with this dll name not only bought me to this thread, but also led me to this github project:

https://github.com/BinomialLLC/bc7e

...which suggested that bc7e is a SIMD BC7 Texture Encoder.

Now recall that the Error.log appears to end whilst importing a graphical image file, and couple that with my understanding that by default, Unity tries to compress graphical textures on import, and it starts to look like this compression on import process is the likely cause of the problem.



The Fixes
=========
There are several possible steps to take, depending on the state of your project & whether or not you can succesfully open it in the Unity editor to make changes, and it should go without saying, please **BACKUP** your project folder before trying any of these changes...

1. If you can open your project succesfully in the Unity Editor,
* open your project in the Unity Editor
* go to Edit -> Project Settings -> Editor
* scroll down the settings until you reach the "Texture Compressors" section
* change the value of the "BC7 Compressor" option so that it reads ISPC (Legacy), and not bc7e or Default
* Close the Project Settings window
* Save the project
* You should now be able to import URP or HDRP successfully.

2. If you can't open your project in the Unity Editor because this issue causes it crash to desktop,
* open your project folder in Windows Explorer (you can use the "..." option in Unity Hub next to your project, and select "Show in Explorer")
* inside your project folder, go to the "ProjectSettings" folder
* find a file named "EditorSettings.asset" and open it in notepad or your favourite text editor (it's a very small file)
* look or search for an entry named "m_Bc7TextureCompressor" - it may not exist if you have never changed it's value before, so don't panic if you can't find it.
* If you found it in the settings, change the value to "1". It should now look like " m_Bc7TextureCompressor: 1"
* If you *didn't* find it in the settings, add a new line and copy & paste all of the following text from inside but excluding the quotes: " m_Bc7TextureCompressor: 1". NOTE: I'm not sure if the order of the settings matter in this file. I suspect they don't, but for context in my versions of this file, this line always appears on the line immediately before the "m_EtcTextureCompressorBehavior" setting, like so:
...
m_Bc7TextureCompressor: 1
m_EtcTextureCompressorBehavior: 1
...
* save your changes to "EditorSettings.asset"
* open your project in the Unity Editor
* the URP / HDRP import process should now complete succesfully, and the editor should open as expected.
* you can confirm your earlier changes by looking in the Project Settings as described in Fix 1.

3. If you tried Fix 2 and you still can't open your project in the Unity Editor, you likely have a different problem. However, as a last resort you can manually remove any package, suich as URP, that is stopping your editor from loading.
* open your project folder in Windows Explorer (you can use the "..." option in Unity Hub next to your project, and select "Show in Explorer")
* inside your project folder, go to the "Packages" folder
* find a file named "manifest.json" and open it in notepad or your favourite text editor.
* look or search for the name of the package you want to remove e.g. for URP look for the entry "com.unity.render-pipelines.universal": followed by whatever version number you're using.
* delete the entire line if you wish to remove the package entirely. Note that depending on the packge you remove & state of your project, this can result in missing dependecy or reference errors when you next load your project, but it should at least load.
* be careful if the package you remove is the last one in the list - as this is a .json file, every line has a comma "," after it *except" for the last line. If you remove the last package listed, make sure you also remove the comma from the previous package entry AKA now the new last package.
* save your changes to "manifest.json"
* open your project in the Unity Editor
* the project should now open succesfully in the Editor.
* if you want to add URP or HDRP at this point, follow the steps in Fix 1.

=========

As for a long term fix, it depends what's causing the problem with the newer "bc7e" compressor. As others have suggested, I suspect it's most likely down to lack of necessary SSE instructions on older CPUs. In which case, a useful fix would be for Unity Hub and/or Unity Editor to test for SSE instruction support when creating a new Unity project, and set the value of "m_Bc7TextureCompressor" in the project settings accordingly, rather than always defaulting to the latest version. Without this, users on older hardware are essentially no longer able to use any of the URP or HDRP project templates as most are unlikely to figure out why their new project is failing to load.

Hope this helps

 

Ok, let's start with the important stuff.
It's been one of those rare, if not the top one, moments that I've been over-excited to congratulate another user for being a problem solver!!! Honestly even before trying the solution and by just reading your post I would find so many different qualities it represents:

• Great and smart work in researching the issue
• Big deal of time spent in the process (obviously)
• Analytical description of the research-flow
• Referencing your sources
• Sharing not just one but several solutions
• Providing knowledge and insight into future research for debugging.
• more!

I am very enthusiastic, probably you are too, as well as extremely thankful to you (and the community in extend) for helping us out! While reading your post and only by coming across your mentions of legacy software, of exposing an issue I had not met in previous suggestions, as well as proposing such a clean and easy solution drove me into creating a new project titled 'URP Hope' (in Unity Editor v.2022.1.23) and giving your solution a try. The outcome is stellar! URP package was imported properly!! I can now go on and install recent packages, try new things and feel less outdated in general.
Even though in my case the shortcoming it's not been such a crucial thing (just too irritating), I am extremely happy, because I had spent plenty of hours (days actually) reading plenty of relevant threads and debugging, because I had lost hope due to my old hardware (probably that's the reason Unity has not invested seriously into this) and because there where other suspicious factors (i.e. some ongoing problem with my licence) which rendered the issue quite complicated and me feeling unconfident of solving it soon.
You friend deserve a high honour of technical supporter/problem solver/psychiatrist or whatever! Kudos!