Official Book of the Dead: Environment

There were a few reasons, but the main one was that Enlighten focuses on delivering real-time GI in scenes, which have fairly clean geometry. Progressive lightmapper allowed us to bake lightmaps while taking all of the complex geometry of all the trees into account, light transmitting through branches, etc.

The trees are generally not lightmapped, due to their large surface area and complex geometry - but they still influenced the lightmap, light probe and occlusion probe bakes. Enlighten would have to treat all these surfaces as if they were going to be lightmapped, which would blow up pre-computation times.

Additionally, since we have full control over the source code, we were able to quickly fix issues and add new features like Occlusion Probe baking.

 

So when do we get to understand more how these occlusion and light probes work together. The reason I don't like using PLM is because it's to slow on these complicated scenes. At least Enlighten caches the GI so it's alot quicker for more complex scenes then use light probes to help out for the bigger stuff like trees.

To really help us understand this new workflow we need a breakdown of how it all works and why so we can incorporate that into our complicated outdoor scenes as well.

Unity 2018 is already 6 months into the pipeline but doesn't feel like it will be production ready until 2019. Hopefully I'm wrong but I really want to start producing these types of results soon with unity.

 

platform windows 10 64 bit with device Direct3D 11 is not supported no rendering will occur. This is the message I get as soon I enter the editor with this assets . Any solution?

 

Is there anywhere I can download the source already exported out from the package or just the package file itself. I ask so that I can store the source art assets vs. the entire project. I have no interest in the rest of the project other than the 3D models, texture maps and the materials. I would bring these art assets into 2018.1.3f and I have no desire to install yet another beta of 2018.

 

I tried it on a Nvidia geforce GT 705 and I can't see fps, but the still are beautiful

I'm trying to mine the shader for stuff I can use elsewhere, I'm interested in the PreIntegratedFGD, I guess it's reading a texture, but that texture is recompute in real time every time (just not every frame)?
It's hard to track all the dependency, 'im looking for IntegrateGGXAndDisneyFGD right now. It's all screen space lighting? That damn shader code is a huge maze...

 

I dont have any of these settings in the main menu. Take a look to the screenshot.

Alt+Enter restart the demo at the beginning point. I can only maximize on play but sadly fullscreen doesn't work for me. Where i'm going wrong?

 

I’m still confused on how to fix this can you explain step by step that would be wonderful

 

Is AtmosphericScattering from Book of the Dead Environment compatible with github Branch: Master. HDScriptableRenderPipeline?

 

As I mentioned, more is coming on that front. In the meantime feel free to poke around in the code, this feature is really straightforward.

 

Nah, still using unity, but just because it's a hdrp doesn't mean that some optimization can't be imported inside a current shader template. Especially if I can find that texture LUT, if it exist.

 

Thanks, I hadn't thought about looking into the *.cs file, was stucked on *.shader lol

 

thank you and another thing can you not jst only import the the environment prefabs like the trees, rocks etc to a project that’s all I really needed

 

How come there appears to be a time of day cycle running in the editor, without needing to press Play on the project?

Also, I read that this uses the progressive lightmapper, but in several other threads on this forum people are saying that the progressive is for static lightmap baking only, and enlighten is for the mixed gi that you can use a time of day cycle with. Can anyone clarify this (again)?

 

Is the real-time light baked in the lightmaps in any way? Wouldn't that be counter-intuitive?

I'm currently fiddling with a day/night cycle in this project as we speak and I haven't noticed anything sticking out as looking odd with the sun in different positions, and I feel the position changes in the original demo are fairly drastic to begin with.

I thought this approach just baked the sky occlusion into lightmaps and thus you were free to put any real-time lights you wanted into the scene after the fact. Seemed like a really clever approach to me, but I may be misunderstanding how it works or how it needs to work to actually work.

I will look at this more thoroughly with what you just wrote in mind the next time I work on this project.

 

We are not able to import shader graph there? (Cant find option) is it blocked?

 

How can I run the asset

 

Wonderfull package, thanks for that. i was wondering how do you achieve the auto-focus when close to object, as i can't find the camera, well i'm a bit lost with this function.

 

Looks like they removed the Shader Graph code from the SRP on BOTD, you can see the removed files if you click "78 changed files" on the top: https://github.com/0lento/ScriptableRenderPipeline/commit/b8517ee26a7e567803adf0efc107bdb801c4a954

 

It's bad I do not know how to ranning it

 

Hi inside the .rar file u'll have Editor.text.
Tip: Search for "Platform Windows 10..." to find for my message error

 

+1
Would love to know this as well...

 

As I saw in this project, directional light is realtime and SkyBox is set. So the lightmap baking result is actually just the sky occlusion map. And this technique not allows us to get some light bounces Enlighten can give. But you can get the dynamic day/night cycle with darkness in occluded areas and bright ambient in some clear places.

 

Yep, seems like it. There may be some directionality to the lightmap based on the skybox used to bake it etc., but I can't tell, especially when post process ambient occlusion is enabled as well.

You can easily make it full night by tweaking the other settings of the scene. Most of the brightness in the scene comes from the auto exposure post processing.

It's actually really clever. It works really well for a forrest scene like this, but you'd probably want the bounced light if it was an indoor scene or a scene with more vibrant colors.

This is easily one of the most fun and flexible projects Unity has released. Everything is so straight forward and easy to tweak.

 

One question that came to my mind while discovering your amazing assets was how you rendered the tree billboards properly. I haven't found a simple efficient solution to this yet.

 

I talk at unite with hd srp dev. Seams that its almost ready. Does the wind inside pack is this final idea (close to it) or not? I hear there was changes planed and I see you have really extended wind shader here.

Not cool is that the trees are baked into unity assets. No chance to dig what happend and why it was made and how it affect the setup.

 

how can i using these components that exists inside this awesome package?
1- baking of Grass occlusion
2- using and baking Occlusion Probes
3- Baking Sky
4- lightmap occlusion doesn't affect to anything??

and why did not you use an better ao method like as HBAO+ for exterior lighting??

 

That's not quite correct.

Direct contribution from the Sun and direct shadows are real-time. (That's what allows us to move it somewhat, change the temperature, etc. Check Light Properties on the game object with AV in the name)

Everything else is baked:

• Lightmaps (on the terrain, some rocks, fallen trees, etc.), storing indirect Sun contribution and direct+indirect sky contribution.
• Light probes, storing indirect Sun contribution and indirect sky contribution.
• Ambient probe, storing direct sky contribution.
• Occlusion Probes, storing sky visibility.
• Various other occlusion types.

If this was an architectural visualisation with white walls and a red sofa, we wouldn't have been able to move the Sun even a little bit without it being apparent, than the indirect light doesn't match any more. But it's a forest with dark albedos killing the bounce and complex shapes making it hard to tell how lighting should look like. That's why we're able to get away with moving the Sun, even though the bake is completely static.

 

I have downloaded the version but all I have to do is script how can I show the models and scene

 

I was wondering, given that the sky is englobing the whole scene, assumed the scene is mostly static, wand we are baking it's contribution in various way, I mean it's globally "unchanging" if it's a single color. For example, if the light is white, we could just multiply it by a color and get the proper contribution, even with indirect light.

Now what if we color code the sky so that each direction has a different color, we would have encoded directionality in the contribution of direct and indirect. Maybe we could use that color to retrieve the direction and project any "sky" into the baked lightmap, indirect too.

Of course that wouldn't work for dynamic contribution.

 

How do you check to see if it has HDRP exactly because I’ve just tried importing the Art folder into my project and it says I have everything but when I drag it into my terrain it’s invisible

 

What's the reason this approach was chosen when the indirect sun contribution is so hard to spot in this scene anyway? At least I feel it is. I can't really tell if it looks wrong if I rotate the sun 180 degrees away from the baked position. Couldn't you just set the sun to be realtime and not have it contribute any indirect lighting to the baked results, and thus freely be able to move the sun afterwards?

I assume this would be accomplished by just changing the sun from "Mixed" to "Realtime" in the inspector?

I'm not even getting a progress indicator when I try to rebake this scene so I'm not sure if it was baked on a render farm or not, which is stopping me from attempting this myself. Whenever I mess up the lighting I've found it to be much faster to reimport a fresh copy of the project rather than try to bake the lighting.

Btw, I love how this scene looks if you just disable the sun. The overcast look, along with everything else of course, has such a realistic feel to it.

Edit: Apparently after a fairly hefty wait the progress indicator appears and it's claiming it "only" takes 2 hours to bake the lighting so I guess I'll try baking it with the sun set to "Realtime" and maybe find the answer to my question.

Edit 2: Okay, so I experimented a bit and it seems to work the way I expected it to, but I honestly can't tell any difference in the baked lightmaps or the scene itself whether or not I bake it with the sun included or not. I almost can't tell a difference if I clear all the baked data.The only major difference I see when baking is the occlusion probes which make the foliage look a lot better, but the ground, props etc. don't seem to change at all.

Which is really cool in my opinion because I hate baking stuff. It's the reason I switched from offline 3D to realtime 3D... and the reason I hate baking.

 

I was thinking for publishing it on android / iOS ?

 

what about the first of the scene in the trailer video why it is not included in the package?