I have followed the instructions to upgrade a project to HDRP and all was going well untill material conversion.
After converting all the materials they became high contrasted black and white and my scene turned all black meshes.
Attached is a screenshot showing the issue, is there anything anyone can think of I may have done wrong? Also creating a new material has the same issue of having a black and white high contrast preview.
My colour space at the moment is linear if that makes a difference.
is HDRP asset correctly setup in the GraphicSettings? Also it seems you have error in the console on the screenshots, so maybe the HDRP doesnāt compile?
Have you try to use playmode or restart the editor?
I have followed a guide to set it up creating the hdrp asset, attaching it as the scriptable render asset in the graphics settings, then the materials turned pink as advertised and then I use the tool to upgrade materials to hdrp and this happens. The error is about emissive number on the converted materials. I have tried restarting the editor to no luck. I am about to try the process again in the latest beta to see if there is any difference.
Also to add when creating a new scene with hdrp in the beta, the āenvironment lightningā settings do not appear where as in my converted scene they are still there even tho these settings are not reflected in the preview
Do you have an ETA for the next release? Weāre using 2018.2.8f1 at uni and need to be able to use version control and changes to the package via package manager doesnāt seem to get versioned
While Iām not certain this is the exact problem. I, too, am experiencing something similar. I upgraded to 2019.2.18 but that did not fix the problem.
All objects are white in linear, and if I disable āVisual Environmentā it is very high contrast black and white.
If I change to RGB, it is high contrast, but I see more color.
EDIT: So, I think the problem occurred when I selected the āCenterEyeAnchorā in the Hierarchy. The Camera had Volume Layer Mask set to Default, I changed it to Post Processing, and I think itās back to normal.
I am having the same issue. I converted my project to HDRP, if the Emission ā Intensity is low then the scene renders as the above image. If I remove the directional light the entire scene is grayed out. The material clearly has the color in the Material tab in the Inspector.
Unity 2020.1.0f1 HDRP 8.2.0. Same issue. @LadyDeathKZN thanks for the link, however:
I am still seeing an unexpected result when converting a project to HDRP, which requires the metallic value of materials to be set (I think) unreasonably high. Following scene has emissive lights and HDRI sky, plus direct light that seems to be behaving properly. Thereās exposure control and a number of post-effects, all of which seem to be doing what they should be doing. The HDRP/Lit material though only seems to light as expected with metallic values above 0.4 (approx)
For the below Iāve just grabbed all materials and dragged the metallic value to zero to illustrate. Itās entirely possible Iām doing something wrong, but this seems different from HDRP intensity issues. I think what is confusing me is that this feels like it should be a pretty straightforward set-up, but it isnāt behaving that way.
Iām not clear why changing the resolution of a planar reflection probe should change what the probe reflects? So please excuse the ramped up metallic and smoothness, but in the first image you can see the floor is clearly reflecting the cabinets sitting on it, as it should. Itās too dark (difficult to remedy this because of metallic problem mentioned above) but itās broadly correct. In the second image all Iāve done is increase the planar reflection resolution to 2048, but as you can see itās now reflecting the HDRI sky. I donāt see why changing res should cause this? The cut-off seems to be between 1024 and 2048 - lower renders correctly, higher renders what I guess is the outer extremity of the scene (sky). I do however understand why even thinking about using 16k res causes Unity to disappear in a blink!
Iād be interested to know if this is an underlying issue or just user-error.
