Black Screen

[aristsevrenis]

I keep getting a black scene when Im editing the world, if I zoom in a bit it works, if I zoom in or out too much it breaks

 

 

Tried in both 2020.3 and 2021.3 HDRP

[aristsevrenis]

I made a video for reproduction steps: http://server.terahard.org:5042/f/60b55bc83ddd4e9886db/?dl=1

[Bryan]

In addition to what I said on discord. 
If you are trying this in 2020.3 and this is still happening I would take a look at your textures. 
Please make sure that you are not exceeding your limit for the terrain. 
 

[aristsevrenis]

1. Bryan (Procedural Worlds) — Today at 12:42

   Hello there, The issue is due to using Gaia Pro in 2021.3. Gaia Pro only works in 2019.3 - 2020.3 Unity versions. If you wanted to use Unity 2021.3 then you will need to upgrade to Gaia Pro 2021.

    

    

    
2. [12:42]

   @_God ΩF War Ares_
3. 

   _God ΩF War Ares_ — Today at 12:46

   this happens on 2020.3 as well
4. [12:46]

   we changed to 2021 last week only
5. [12:47]

   but this has been happening for 2-3 months
6. 

   Bryan (Procedural Worlds) — Today at 12:47

   Just answered in the ticket as well. Can you please check your terrain textures? You might be exceeding your texture limit which is one of the things that could cause this issue.
7. 

   _God ΩF War Ares_ — Today at 12:47

   ah

    

    

    
8. [12:47]

   so if we reduce the size of the ground texture it fixes itself right
9. 

   Bryan (Procedural Worlds) — Today at 12:48

   Its more of how many textures do you have on the terrain.
10. 

    _God ΩF War Ares_ — Today at 12:48

    I see, how many is the limit?

     

     

     
11. [12:48]

    also we're using Gaia 2021 Pro
12. [12:48]

    
13. 

    Bryan (Procedural Worlds) — Today at 12:48

    You can only have 8 terrain layers.
14. [12:49]

    Gaia Pro 2021 works in unity versions 2020.3 - tbd. So that should be fine. Make sure that you remove Gaia Pro before adding in Gaia Pro 2021. This could have broke the project if you imported directly over it.
15. [12:50]

    Make sure that HDRP version you are using is also the correct HDRP version for that Unity project as well sometimes, its possible to import the wrong version which could cause an issue.
16. 

    _God ΩF War Ares_ — Today at 12:52

    no we only imported pro from the get go
17. [12:53]

    we have a separate project for gaia to try stuff before we were going to push things to the main project
18. 

    Bryan (Procedural Worlds) — Today at 12:53

    Then I would check your texture limit, and HDRP.
19. 

    _God ΩF War Ares_ — Today at 12:53

    maybe it's the number of ground textures
20. [12:53]

    give me a sec i ll ask the artist
21. [12:54]

    at the moment we have biomes right
22. [12:55]

    so is more than 8 textures going to break in runtime as well?
23. 

    Bryan (Procedural Worlds) — Today at 12:55

    Yes and no I have seen it both ways.
24. 

    _God ΩF War Ares_ — Today at 12:56

    right, our artist is saying that per biome he doesn't think he's using that many

     

     

     
25. [12:57]

    
26. 

    Bryan (Procedural Worlds) — Today at 12:57

    Per biome doesnt really matter, its more so the case per terrain. While you can spawn multiple biomes on the terrain you cant have more than 8 textures per terrain.
27. [12:58]

    In the video that was sent also I would check because that video shows that you are using Gaia Pro not Gaia Pro 2021.
28. [12:58]

    3.1.4 is Gaia Pro. 3.2.2 is Gaia Pro 2021.
29. 

    _God ΩF War Ares_ — Today at 12:59

    oh really? hmm let's see if there's a problem
30. 

    Bryan (Procedural Worlds) — Today at 12:59

    
31. [13:01]

    im sorry thats my mistake
32. 

    _God ΩF War Ares_ — Today at 13:01

    ?

     

     

     
33. 

    Bryan (Procedural Worlds) — Today at 13:01

    2.2.5 was Gaia Pro last version. 3.1.4 is a really old version of Gaia Pro 2021
34. 

    _God ΩF War Ares_ — Today at 13:02

    ok so I checked the projects, inside our gaia_demo project I had 3.1.4, inside our normal project we have 3.2.2
35. [13:02]

    I exported the biomes from the 3.1.4 and put it inside the 3.2.2
36. 

    Bryan (Procedural Worlds) — Today at 13:03

    I dont think that would cause any problems doing that.

    

    1

     
37. 

    _God ΩF War Ares_ — Today at 13:03

    you saw our spawn rules though right, do these count as 7?
38. 

    Bryan (Procedural Worlds) — Today at 13:04

    Yes that should be fine as long as your not adding anymore than 1 texture to the terrain.
39. 

    _God ΩF War Ares_ — Today at 13:04

    ok so ideally we need to have smaller terrains when biomes blend right

     

     

     
40. [13:05]

    in the sense to not get 8 textures apply

     

     

     
41. [13:05]

    on the same terrain
42. 

    Bryan (Procedural Worlds) — Today at 13:06

    You can have up to 8 textures per terrain. In the case where you need more than 8 textures per terrain the best option is to do a multi-terrain setup. Then you can use an additional 8 textures on the next terrain.

     

     

     
43. 

    _God ΩF War Ares_ — Today at 13:07

    I ll send it to our artist, I hope it's not too technical for him

     

     

     
44. [13:08]

    also let's say that we have 2 biomes that share textures, is the system smart enough for that? or is each one considered a unique one
45. 

    Bryan (Procedural Worlds) — Today at 13:08

    Having the terrain go black like this indicates there is an issue with the terrain shader. Which usually suggests that the texture limit has / is the issue. At the end of the day we utilize the standard Unity terrain system. So any rules such as this we follow ( unless you are using a 3rd party terrain shader ) For example when we had CTS you could use 16 textures per terrain.

     

     

     
46. @_God ΩF War Ares_

    also let's say that we have 2 biomes that share textures, is the system smart enough for that? or is each one considered a unique one

    

    Bryan (Procedural Worlds) — Today at 13:11

    This kinda depends ( you would see the same texture pop up twice in the terrain texture window in the inspector of the terrain - than this is an issue ). If its the same textures in two biomes I would remove that texture spawner from the biome or turn it off. If you spawn the biome and you are seeing duplicated textures on the terrain textures in the inspector this is defiantly the issue.

     

     

     
47. 

    _God ΩF War Ares_ — Today at 13:11

    Got it

     

     

     
48. [13:12]

    Didn’t know that unity’s terrain shader had the 8 texture limit

     

     

     
49. [13:12]

    Btw it’s working ok on runtime, just the editor goes nuts

     

     

     
50. 

    Bryan (Procedural Worlds) — Today at 13:14

    The only other thing I can think of which I have seen a long time ago, havent witnessed it since was the shadows issue Unity used to have. This issue would look like a black circle when getting close to the terrain, it wouldnt make the entire scene go black though.

     

     

     
51. [13:15]

    Hopefully this helps. Please let me know if any of this was the case! If you need further assistance please send me a pm as I am signing off for the night as its 5am here.

     

     

     
52. 

    _God ΩF War Ares_ — Today at 13:16

    it sounds like this is the case as if you see in the video, in my attempt to reproduce this I had to add multiple biomes to get it to break

     

     

     
53. [13:16]

    obviously my artist has used the tool a lot more than myself so he might be getting something similar

     

     

     
54. [13:16]

    but at least we have something to go on

     

     

     
55. [13:17]

    maybe we should copy paste this conversation in canopy for others to benefit from

     

     

     
56. 

    Bryan (Procedural Worlds) — Today at 13:17

    Yeah let me know if thats the issue! If not we can keep looking into it.

[Josh]

HDRP sometimes has a bug where it stops rendering and goes black, this has been reported directly to Unity HDRP team and they are trying to find the source of the issue. Wil let you know when they get back to us. Only way around fixing this is to restart the editor so it refreshes HDRP DLL and recompiles.

[Bryan]

This was solved, just wanted to post the notes from it.