Adding screen space component turns block invisible

[Mukna]

Every time I have added a screen space component, the entire block turns invisible. As in the uiblock is still in the hierarchy and I can control all options, yet it does not display anything.

I ran in to this issue in my own scenes and wondered if I was just using it wrong, however even opening the sample scenes that utilise it, I get the same issue.

I'm using Unity 2021.3.16f1 and Nova Trial v1.1.8

[Mukna]

Repro:

1. Add a UIBlock2D (though this happens with any UIBlock). This shows default color and size.
2. Add Screen Space component to the block.

After adding the Screen Space component, I have even tried using the fitting options to expand and shrink and still nothing is visible

[Mukna]

Also, would like to add that removing the component does not bring back the visibility. I have to either reload the scene or create a new UIBlock object

[dkonik]

Thanks for checking out Nova! I just tried the importing the trial into 2021.3.16f1 and was not able to reproduce the issue. It's hard to say what might be going on without some additional info, would you mind providing some more details:

1. Are you able to see the UIBlock with the ScreenSpace component in scene view, or does it disappear from there as well?
2. Did you import the trial into a new project, or an existing project with some modified rendering/camera settings? If the latter, could you try importing it into a new project and see if the error still occurs? Also, it might be useful to see a screenshot of your Camera component.

[Mukna]

It doesn't work in scene view, nor play mode. As far as I'm aware I have not added any custom render settings or anything of that nature but will try to import it in to a new project

[Mukna]

Adding to a brand new project, this is the outcome

[dkonik]

We managed to reproduce both of the issues you're seeing (the burst error as well as the ScreenSpace issue). The missing piece to reproduce it was using HDRP. It looks like the default HDRP project imports a newer version of Burst, which could be causing the burst error. We're still investigating what's causing the ScreenSpace issue, but we will follow up here when we have more info!

[Mukna]

Sorry! Should have mentioned I was using HDRP too!

[dkonik]

Apologies for the delay in response. For the screen space issue you are seeing, it appears it is related to how HDRP uses the render queue values of materials. We will be submitting an update for this, but in the meantime you can fix the issue locally by changing the Render Queue value of the SortGroup component (that was added by the ScreenSpace component, so it will be on the same gameobject) to something like 3050.

With respect to the burst errors you are seeing, this seems to be a bug with burst 1.8.2, and upgrading to 1.8.3 resolves the issue. If you are unable to upgrade burst through the package manager UI, you can do so via the manifest.json file in the Packages folder of your project. Just modify the burst entry to "com.unity.burst": "1.8.3" (or if there is no com.unity.burst entry, simply add it).

[Mukna]

Confirmed this has fixed all the issues for me :)

[dkonik]

Thanks for the confirmation, v1.1.9 has been published with the HDRP change!