Both 2022.2.3f1 and 2022.2.4f1 crash if sceneview or game view are visible upon launch

Unity Engine
, ,
1

For some reason both 3f1 and 4f1 crash straight away if I open a project that has either the scene view or the game view visible when it launches. This started the other day with 3f.1. I spent several hours trying to diagnose if it was something with my project, but eventually just started a new URP project and it crashed with the same issue.

If I open a project that doesn’t have one of those views visible, the editor runs just fine until the scene or game view tabs are opened or clicked on. Opening the same project back up in 2f1, everything is fine again.

Below is the error message that I keep getting:

Here are my system details:

2

would you elaborate on what you meant by both scene and game view open? the default layout is they are all open in the tab, and how do you click on both tabs?

3

My usual layout does not have them visible by default due to getting tons of error messages at times about something not having a handle in the domain. So I loaded a project using a layout of mine that doesn’t have them visible, and it loaded in both 3f1 and 4f1 until I clicked one of the views. I didn’t mean both at once, just that both (either) of those views being or becoming visible would cause it to crash.

4

hmm i just opened a fresh 2d project with 22.2.4f1 without any noticeable issue. would you mind to attach your log file?

5

I didn’t test 2d, but I just did another test in 4f1 and it doesn’t do it when using OpenGL, but once I switch to Vulcan (which I currently use for all projects), load a project (tested just now with a brand new URP demo project) here is what I get: Editor.log · GitHub

I have also submitted a bug report via the crash popup, which is titled the same as this threads title. IN-30532

1 Like
6

Nevermind about the bug report. As usual, it just gets closed saying I am unsupported. Don’t know why I bother submitting them.

7

same as before, i’ve opened the lego tutorial which is a URP project without any problem. Looking through your log, you are indeed not on a supported linux distro.

8

nothing errors out for me on Ubuntu22.04

8770927--1189927--Screenshot from 2023-01-31 10-36-12.png
8770927--1189927--Screenshot from 2023-01-31 10-36-12.png3847×1738 494 KB

9

Lego “works” with OpenGL, but has this artifact that takes half the screen and flashes. (as did the URP demo construction scene)

Then here is the same scene, but with Vulcan, trying to hit the Scene View.

One thing I just noticed, is that game view actually works fine, scene view is where it crashes, at least in 4f1. I will need to see if I see the same behavior in 3f1.

10

Here is the error log from that last video clip.

There seems to be more info in it, at the end. Not sure if it is relevant.

Just for the sake of thoroughness, here is the same project in 2022.2f1

11

@MostHated which distro are you on and which graphic card do you have, could you please tell me?
I have seen this kind of diagonal artifact on MPV and other video players when I tried switching to Fedora 38. Apparently it is a known issue with AMD drivers.

12

I am on Pop_os 22.04 (Ubuntu distro) and an AMD 6900XT. Though, I don’t have, nor have I had that artifact anywhere else or in any other application. Only scene view of 2022.3f1 and 2022.4f1.

13

the flashing issue is known. The vulkan part is not. I tried it again on the tutorial scene with vulkan, nothing crashed for me.

14

Just updating for visibility in case anyone else has more info eventually, this also happens in 2022.2.5f1. I guess I am just stuck with 2f1, which is a shame. A bug I submitted last year was finally fixed… in 3f1.

Even more strange, it runs/play mode works just fine as well. Just so long as I keep the scene view hidden. Something about the scene view is just wonky.

15

I just tried to reproduce it with 2022.2.5 on Fedora 37, KDE, X and an AMD graphic card.
If I use OpenGL I see the diagonal artifact. I didn’t notice any issue when using Vulkan.

1 Like
16

Interesting. As mentioned, everything before 3f1 works perfectly. 3f1 and newer, both existing and new projects fail due to scene view in both URP and HDRP. One of the error logs along the way, near the end I believe mentioned serialization. I am going to have to go back through the 3f1 patch notes to see if anything jumps out as a possible cause. Not sure if any of it is anything I can actually do anything about, though.

17

Same issue, we purchased an AMD card(6700XT I believe) for testing the game and we can’t even get the editor to start on it. Definitely narrowed it down to Vulkan, log is essentially the same as what was already posted by MostHated.
We were using 2022.2.6f1, tried migrating to 2022.2.9f1, still persists.

Also have the same graphical issue with OpenGL as previously mentioned.

Creating a blank URP 3D project with 2022.2.9f1 crashes, 2022.2.1f1 runs fine however.

1 Like
18

I am also experiencing the issue of the diagonal rendering issue switching from 2022.2.0b10 to 2022.2.8f1.
This is especially an issue since I want to work with Entities 1.0 which requires 2022.2.8.

I do however not have an AMD but an NVIDIA card on a notebook (either NVIDIA cards are affected too or the scene view is using the onboard graphics card).

This is really annoying since it makes the new versions basically unusable while the older versions worked without any issues so there must have been some change causing this.

19

I suspect the OpenGL issue is vendor agnostic, if you’re using Nvidia just switch to using Vulkan to work around it.

20

re: the AMD Vulkan issue, it appears to be fixed in Mesa, presumably in 23.0. Using a dev-build so unsure if it’s actually in 23.0.

1 Like