Search Unity

Bug 2021.1 up Crashes all the time. HDRP/Dx12. Multiple monitors.

Discussion in 'Editor & General Support' started by Mindtoast451, Jul 12, 2022.

  1. Mindtoast451

    Mindtoast451

    Joined:
    Aug 2, 2013
    Posts:
    20
    I have never experienced such instability as with trying to run Unity 2021.1.3f and up. I am using HDRP with DX12. If I attempt to move or resize any window, or sometimes just close a window, the Unity editor starts gliching and then Crashes. This is happening even with an empty project started from the HDRP template. I guess it is possible due to using multiple monitors as it seems it is more stable when the editor is only being used in 1 monitor. I filed a bug report, but I need help quickly as this is really making Unity virtually unusable.
     
    Last edited: Jul 15, 2022
  2. ronJohnJr

    ronJohnJr

    Joined:
    Mar 5, 2015
    Posts:
    106
    Is there a reason you're using dx12? Try dx11
     
  3. Mindtoast451

    Mindtoast451

    Joined:
    Aug 2, 2013
    Posts:
    20
    Yes, I am using raytracing, and unless I'm mistake, that is only available by using DX12. I've been using DX12 for a couple years now without having this issue. I upgraded to make use of some of the new features in 2021.3 that I really needed to use. After doing some more tests, it seems just using a single monitor still crashes Unity. I can only guess that this is some kind of bug that has to do with DX12. I am running another project with 2021.3.2f with udp and DX11 and it does not crash or glitch when moving/resizing windows. I do have a backup of the project with the earlier version of Unity that was stable, but I cannot believe the updates have such an issue, and I would very much like to continue using 2021.3.2f.
     
  4. ronJohnJr

    ronJohnJr

    Joined:
    Mar 5, 2015
    Posts:
    106
    2021.3.2f. is a little old, try the newest one. or even 2022 as a last resort
     
  5. Mindtoast451

    Mindtoast451

    Joined:
    Aug 2, 2013
    Posts:
    20
    I did try 2021.3.6f, but had the same problem. I will go ahead and try 2022. Couldn't hurt to try.
     
  6. ronJohnJr

    ronJohnJr

    Joined:
    Mar 5, 2015
    Posts:
    106
    What the error you get?
     
  7. Mindtoast451

    Mindtoast451

    Joined:
    Aug 2, 2013
    Posts:
    20
    There doesn't seem to be any error reported in the console prior to crashing.
    I'm not great at understanding crash logs.
    This is the editor log just prior to crash...
    ------------------------------------------------------
    AcceleratorClientConnectionCallback - disconnected - 192.168.1.214:10080
    Failed to upload artifact(artifact id=23e8fa66e6059c1fa220422684bdb5f4, static dependencies=c78c0dd0c7ff9b2c005af47ed43c5ed1, content hash=0610a6dabfafa4a37437055f15d0a211) to cacheserver
    AcceleratorClientConnectionCallback - disconnected - 192.168.1.214:10080
    AcceleratorClientConnectionCallback - disconnected - 192.168.1.214:10080
    Failed to upload metadata for artifact(static dependencies=c78c0dd0c7ff9b2c005af47ed43c5ed1) to cacheserver
    [Worker0] Start importing Assets/Settings/HDRP High Fidelity.asset using Guid(36dd385e759c96147b6463dcd1149c11) Importer(815301076,1909f56bfc062723c751e8b465ee728b)
    [Worker0] -> (artifact id: '652489b924a8920882594443a7a4a47e') in 0.012331 seconds
    AcceleratorClientConnectionCallback - disconnected - 192.168.1.214:10080
    Failed to upload artifact(artifact id=652489b924a8920882594443a7a4a47e, static dependencies=16ebc44b1da4ca4cd008e9b319768d13, content hash=380be9bc21a66e6cde50a15367d087e6) to cacheserver
    AcceleratorClientConnectionCallback - disconnected - 192.168.1.214:10080
    AcceleratorClientConnectionCallback - disconnected - 192.168.1.214:10080
    Failed to upload metadata for artifact(static dependencies=16ebc44b1da4ca4cd008e9b319768d13) to cacheserver
    d3d12: upload buffer was full! Waited for COPY queue for 4.055 ms.
    d3d12: upload buffer was full! Waited for COPY queue for 3.609 ms.
    d3d12: upload buffer was full! Waited for COPY queue for 3.638 ms.
    d3d12: upload buffer was full! Waited for COPY queue for 3.579 ms.
    d3d12: upload buffer was full! Waited for COPY queue for 3.558 ms.
    AcceleratorClientConnectionCallback - disconnected - 192.168.1.214:10080
    Launched and connected shader compiler UnityShaderCompiler.exe after 0.05 seconds
    Launched and connected shader compiler UnityShaderCompiler.exe after 0.04 seconds
    d3d12: upload buffer was full! Waited for COPY queue for 3.982 ms.
    d3d12: upload buffer was full! Waited for COPY queue for 3.546 ms.
    d3d12: upload buffer was full! Waited for COPY queue for 3.550 ms.
    d3d12: upload buffer was full! Waited for COPY queue for 3.527 ms.
    d3d12: upload buffer was full! Waited for COPY queue for 3.517 ms.
    AcceleratorClientConnectionCallback - disconnected - 192.168.1.214:10080
    AcceleratorClientConnectionCallback - disconnected - 192.168.1.214:10080
    Crash!!!
     
  8. ronJohnJr

    ronJohnJr

    Joined:
    Mar 5, 2015
    Posts:
    106
    try this:

    Edit->Project Settings-> Editor->Cache Server->Use global settings (stored in preferences)

    And

    Preference->Asset Pipeline->Default Mode->Disabled
     
  9. CodeSmile

    CodeSmile

    Joined:
    Apr 10, 2014
    Posts:
    5,964
    and check for updated video drivers
     
  10. Mindtoast451

    Mindtoast451

    Joined:
    Aug 2, 2013
    Posts:
    20
    I tried creating a new project with Unity 2022.1.0b6, and just changed the settings to use dx12 using the HDRP wizard. Still crashing.
    • Updated video drivers - Confirmed
    • Changed cache server to use global settings - check
    • Disabled asset pipeline - check
    This error seems to always pop up when Unity is started...
    d3d12: Profiler is enabled, but stable power state is not. GPU timing errors are expected.


    Resized a panel... Glitching Editor, then crash...

    Log


    [Project] Loading completed in 18.509 seconds
    Project init time: 15.383 seconds
    Template init time: 0.000 seconds
    Package Manager init time: 0.484 seconds
    Asset Database init time: 7.279 seconds
    Global illumination init time: 0.002 seconds
    Assemblies load time: 0.673 seconds
    Unity extensions init time: 0.001 seconds
    Asset Database refresh time: 0.000 seconds
    Scene opening time: 0.850 seconds
    d3d12: upload buffer was full! Waited for COPY queue for 2.042 ms.
    d3d12: upload buffer was full! Waited for COPY queue for 0.993 ms.
    d3d12: upload buffer was full! Waited for COPY queue for 1.128 ms.
    d3d12: upload buffer was full! Waited for COPY queue for 1.255 ms.
    d3d12: upload buffer was full! Waited for COPY queue for 1.031 ms.
    Launched and connected shader compiler UnityShaderCompiler.exe after 0.04 seconds
    Launched and connected shader compiler UnityShaderCompiler.exe after 0.04 seconds
    EditorUpdateCheck: Failed Cert verify failed: UNITYTLS_X509VERIFY_FLAG_USER_ERROR1
    Created GICache directory at C:/Users/plast/AppData/LocalLow/Unity/Caches/GiCache. Took: 0.026s, timestamps: [26.974 - 27.000]
    gi::BakeBackendSwitch: switching bake backend from 3 to 1.
    Setting up 8 worker threads for Enlighten.
    Launched and connected shader compiler UnityShaderCompiler.exe after 0.04 seconds
    Launched and connected shader compiler UnityShaderCompiler.exe after 0.04 seconds
    <RI> Initialized touch support.

    [LicensingClient] Successfully updated the access token
    [Licensing::Module] Successfully updated access token: "ftq8ZQ5w"... (expires: 2023-07-13 03:41:24 GMT)
    [LicensingClient] Successfully updated the access token
    [Licensing::Module] Successfully updated access token: "ftq8ZQ5w"... (expires: 2023-07-13 03:41:25 GMT)
    AcceleratorClientConnectionCallback - disconnected - 192.168.1.214:10080
    AcceleratorClientConnectionCallback - disconnected - 192.168.1.214:10080
    TrimDiskCacheJob: Current cache size 1mb
    <RI> Initialized touch support.

    Crash!!!
     
  11. ronJohnJr

    ronJohnJr

    Joined:
    Mar 5, 2015
    Posts:
    106
    what windows version are you on? what graphics card do you have?
     
  12. Mindtoast451

    Mindtoast451

    Joined:
    Aug 2, 2013
    Posts:
    20
    Windows 10 Pro 21H2
    Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz 3.60 GHz
    NVIDIA GeForce RTX 3090
     
  13. ronJohnJr

    ronJohnJr

    Joined:
    Mar 5, 2015
    Posts:
    106
  14. Mindtoast451

    Mindtoast451

    Joined:
    Aug 2, 2013
    Posts:
    20
  15. ronJohnJr

    ronJohnJr

    Joined:
    Mar 5, 2015
    Posts:
    106
  16. Mindtoast451

    Mindtoast451

    Joined:
    Aug 2, 2013
    Posts:
    20
    >>try adding -force-d3d12-stablepowerstate as cl flag
    I gave that a try. It did resolve the stable power state error, and it also seemed to make Unity start up really fast:D, but it did not fix the crashes:eek:. I even tried Unity 2022.2.0a18 where dx12 is out of experimental, and it also crashes after resizing or moving windows. I have tried running other dx12 applications and they seem to run perfectly well. I tried installing several different drivers from NVidia, but this did not seem to help either. :confused:
     
  17. ronJohnJr

    ronJohnJr

    Joined:
    Mar 5, 2015
    Posts:
    106
    I'm out of ideas sorry :( what's your desktop resolution?
     
  18. Mindtoast451

    Mindtoast451

    Joined:
    Aug 2, 2013
    Posts:
    20
    No problem. Thanks for the ideas though. My res is 1920x1080. I tried unhooking my other monitors and tested with just one, but the same crashes occurred. If I come up with any solution I'll post.
    It's probably just some dx12 setting somewhere that isn't configured correctly for some strange reason.:confused:
     
  19. Mindtoast451

    Mindtoast451

    Joined:
    Aug 2, 2013
    Posts:
    20
    Update! Never trust NVidia updates!
    I uninstalled my NVidia drivers and installed drivers from 2021. FIXED!!!!
    Fixed on all unity version!
     
  20. ronJohnJr

    ronJohnJr

    Joined:
    Mar 5, 2015
    Posts:
    106
    Glad to hear! Keep in mind the things you have changed here, like the command line flags. I'm not sure if they will have unintended consequences in the future.