Question [Solved] Upgrading from HDRP 7.1.8 to 7.2.0 crashes editor

Hello,

I just try to upgrade my projects from HDRP 7.1.8 to HDRP 7.2.0 and I encountered a nasty bug.
After all RP assets got imported, the editor prompts that all HDRP materials have to automatically updated.
Then I click on "Ok", it refreshes some materials, but the progress bar is not even at quarter and then Unity crashes. So Unity crashes in the middle of the update progress, which is really bad.
When I now try to open my project again, it will crashes too. So I guess the update procress corrupted my project, completely.

So that means, until the auto update for the materials is not fixed, I cannot go to HDRP 7.2.0 or I have start completely from beginning.

That project used DirectX12 and DXR. But the error log proves me one time again that DirectX12 in Unity is completely unstable.

After upgrading other projects, it seems it only fails with DirectX12 and DXR enabled.

========== OUTPUTTING STACK TRACE ==================

0x00007FF7C733936C (Unity) D3D12Fence::Wait
0x00007FF7C736035C (Unity) AsyncReadbackDataD3D12::Update
0x00007FF7C73A9EA5 (Unity) GfxDeviceWorker::RunCommand
0x00007FF7C73B131B (Unity) GfxDeviceWorker::RunExt
0x00007FF7C73B16D8 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FF7C823BA83 (Unity) Thread::RunThreadWrapper
0x00007FF804B97BD4 (KERNEL32) BaseThreadInitThunk
0x00007FF80656CED1 (ntdll) RtlUserThreadStart

 

same issue after open existing scene Unity Freeze and crash

 

Same; although it manifests in my case with a test project build with 7.1.8, switched to DX12, upgraded to 7.2.0 and now cannot load the default HDRP sample scene, instantly takes Unity down.

 

same here. I don't even use DX12 / DXR tho

 

Same issue here by upgrading
3 different DX12 DXR projects projects on all included scenes from 7.1.8 to 7.2.0
in Unity 2019.3.0f6 and 2020.1.0a22.
Editor crashes after opening a scene after HDRP upgrade.

 

Since you mentioned it happens on DXR, make sure you wipe LocalPackages folder and remove the hdrp-config package from your manifest and try to run HDRP wizard again once it opens.

What happens now (afaik anyway) is that if you upgrade HDRP, it doesn't update the config package that was copied to local folder and modified there by HDRP wizard on the earlier version (local copy only gets created with HDRP + DXR combo). If you don't force the upgrade for this manually, you'll have mismatching setup.

 

that makes sense, but not everyone with this issue is using DXR/DX12

 

I just tested this with fresh HDRP Template that is set to 7.1.8 by default. I can't repro the crash without DXR being setup (it upgraded to 7.2.0 just fine for me). But once I had DXR setup it does crash the editor when trying to upgrade.

If I wipe library folder it'll reset the default scene on startup and it lets me open the editor again but once I try to open the upgraded scene, it'll crash again.

 

Doing further experiments on this, the crash DXR users see is related to DX12 being enabled and to the upgraded scene from older version.

Even if you don't conf HDRP for raytracing, it'll crash instantly when you open old scene with DX12 set as default renderer in Unity with HDRP 7.2. If you wipe the library and rebuild your scene again (from prefabs etc), it'll stay functional despite DX12 being enabled.

When it crashes you get the same stack trace as in the original post here.

 

Really, rebuilding all scenes from scratch. There must be some way to upgrade the scenes.
Deleting the library folder works, but as soon as I add a Physically Based Sky to a new scene, Unity crashes.

 

I know that all last week the 7.2.0 was delayed for bugs etc but how can this be released when we cant even use our scenes? Ridiculous. Just stop saying when things are being released and release them when they work. So what do i do now that i cant even open my huge scene? Im not rebuilding it from scratch as its not feasible

 

If Unity is aware of this issue since last week, why not informing users, when announcing HDRP 7.2.0?
Also, I really like to know why DirectX12 get not so much care from Unity devs.

 

Would be nice to know how many auto crash reports Unity received yesterday.)
From my side around 50 during 6 hours trying to update some projects with any tricks i could imagine).

Such extreme bugs are vasting lots of dollars when you multiply it with working time invested by unity alpha and beta testers.

 

Yes, DirectX12 and DXR are very experimental, but I like to try out the new tech and give Unity feedback about it, despite I have the feeling you will not really care about it. But I cannot give feedback, if Unity simply crashes. It has to be stable at some point, like I can try things at least for one minute out before everything is crashing. At the moment, this is not the case. I think it was okay to release HDRP 7.2.0 anyway, because non DXR projects need it, like I also have projects that needed some HDRP fixed.

But I kindly ask Unity to be more transparent about very huge bugs if Unity know them before. Now I feel a little bit like you knew everything and just waited for somebody to created a thread like that. Also, I must say this is not the first time.
It really annoys me when I spend my time to report bugs to Unity, just to be informed later that Unity already knows about the bugs but hiding the Issue cases and remain silent.
And if Unity constantly annoys the developers, Unity should not be surprised when devs leaving Unity completely and no longer be your alpha and beta testers. My time is very limited and if wasting time of known bugs can be avoided, I really like to get the chance.

I really looking forward to try out the more stable DirectX12 and DXR. Thank you for the hard work.

 

Upgraded to Unity 2019.3.2f1 and now this:

========== OUTPUTTING STACK TRACE ==================

0x00007FF6F5D80A06 (Unity) GfxDeviceD3D12::BuildTopLevelAccelerationStructure
0x00007FF6F5DB5675 (Unity) GfxDeviceWorker::RunCommand
0x00007FF6F5DC360C (Unity) GfxDeviceWorker::RunExt
0x00007FF6F5DC39F8 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FF6F6C51123 (Unity) Thread::RunThreadWrapper
0x00007FFBF23A7BD4 (KERNEL32) BaseThreadInitThunk
0x00007FFBF27ECED1 (ntdll) RtlUserThreadStart

Guess it's the same random crash I get with DirectX12 since months. But atleast I can continue to work on my project and reach the build button, you just have to be very fast before the editor crashes.
Now, DXR is also working in BUILD, even with reflections. So that is some progress.
Nevertheless, you cannot work in the editor with DirectX12, because it can crash any seconds and will at some random point. But the funny thing is, the build with DirectX12 seems never to be crashing, it is just the editor, that is so unstable.

So work on your project in DirectX11 mode, after work is done save, then switch graphic API to DirectX12, build, and test your changes. Working and testing in editor with DirectX12 is just an unstable waste of time. Sorry.

 

fyi
https://forum.unity.com/threads/unity-experimental-hdrp-dxr.656092/page-13#post-5481054
you have to wait some days

 

I wait since months. I would love to be more productive but the state of the future tech is not there to go on, sadly. I'm not sure to try out the alpha, because I had massive bugs with betas and even RCs, slowing me down. But thank you.

 

Not to rob the thread or anything, but why is DX12 still experimental and unstable? I feel like DX12 has been around long enough.

Just googled it, It was released in July 2015 and there are videos and threads about Unity Dx12 in 2016...I am assuming it was in Unity5.4 beta?

Regardless, I just feel DX12 should be production-ready by now...DX12 doesn't feel like a new thing anymore...
Is there an underlying issue that we are not aware of regarding DX12?

 

I guess the usual "not the highest priority" issue and maybe they thought DirectX12 would not be that important? But now with DXR it is needed and they need to hurry with DirectX12 to satisfy the RTX owners and Nvidia as a partner ...

Yes, I'm using HDRP 7.2.1 and the newest Unity version. Like I'm always told here from the support to get the latest bugfixes in order to run DXR. That is what I'm doing.

Again, I asked several times, but can somebody from Unity clarify what Nvidia driver you are recommending for DXR?
I'm using the latest Nvidia Studio driver. I heard that the newest ones are not so stable, had also issues with Denoising due to a bug, but I think Nvidia fixed it in february. That is the information I got from lightmapper forum.

Regarding that Unreal is also crashing with their DXR demos, I suspect that it is either an issue on Nvidia's side or both engines fail in their implementation. But on the other side, I had zero issues with DXR in Adobe and blender.

 

Sure, here is the log.

 

Thank god I didn't bother upgrading then

 

DX12 is not the default framework for most games. And there is no real reason why it should be. Performance is not better than DX11 and there are not really that many features that make it stand out. Even if there were, the benefits are small, and performance will always beat bells and whistles.

Now with RT Raytrace coming into play, IF it becomes fully adopted by the industry fast, this might change.

But when the most common graphics card on Steam is still 10xx (1060) series and even 9xx.. (970) it is hard to make that assumption.

 

I have to say that all the reasons you stated have nothing to do with DX12 being not ready after all these years.

In fact, if I add my speculation...

DX12 is not the default framework for most games -> for Unity yes, because it is still not ready, and for non Unity games, not really. Most new titles of scale are DX12 or plan to be.

Performance is not better than DX11 and there are not really that many features that make it stand out -> Its a graphics API for improved/advanced features. Performance improvement is not what DX12 is for or for that matter any DX release. DX11 was slower than DX10. DX10 was slower than DX9 - at least that is how everyone felt. Its the latest standard set by Microsoft for windows platform. That standard, of course, aims to fulfill the modern needs of graphics. Also, even if I was wrong by a mile, it has nothing to do with DX12 readiness. It is not like DX11 will be damaged if DX12 is production-ready. DX11 and DX12 should be ready by now, regardless of one's opinion of which one is better.

Now with RT Raytrace coming into play, IF it becomes fully adopted by the industry fast, this might change.-> I think with INTEL, AMD and NVIDIA working together for future Raytracing tech and also the fact that all next gen consoles have RT, the IF you stated has already happened.

But when the most common graphics card on Steam is still 10xx (1060) series -> which supports DX12...

 

I never said DX12 is not ready?

Looks like you just made it up to just add your speculation anyway.
You could do it without disproving things I never said. things never said can't be disproved anyway.

I simply said not many use it because it does not offer anything groundbreaking that justifies the lower performance.

 

It kind of does when you quote my question of "why is it not ready?" and then your response is "its not the default because it's not really faster".

Then I said, it being slow/faster(the API) has nothing to do with Unity's DX12 implementation speed.

Then you said that you never said DX12 is not ready.

I don't think we are talking about same things...
Either way, I am still curious as to why DX12 is still experimental.

 

Because it's not as optimized as DX11 path is now? It's pretty clear that they put initially more focus on renderers that are most commonly used today. @SebLagarde gave estimate earlier that they will address the current DX12 perf issues on 2020.2, I don't know if that estimate is still valid.

If you look at the HDRP release blog post: https://blogs.unity3d.com/2020/02/24/hdrp-out-of-preview-in-2019-3/
and the supported platforms, they marked this on DX12: