Skip to content

Fixed using the wrong method to define if a light should be included in the light cluster depending on its baking status. #2932

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 17, 2020
Merged

Fixed using the wrong method to define if a light should be included in the light cluster depending on its baking status. #2932

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
54e1b1f
- Fixed using the wrong method to define if a light should be include…
anisunity Dec 17, 2020
96a6421
Update CHANGELOG.md
sebastienlagarde Dec 17, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...r-pipelines.high-definition/Runtime/RenderPipeline/Raytracing/HDRaytracingLightCluster.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -269,7 +269,7 @@ void BuildGPULightVolumes(HDCamera hdCamera, HDRayTracingLights rayTracingLights
continue;

// If the light is flagged as baked and has been effectively been baked, we need to skip it and not add it to the light cluster
if (light.lightmapBakeType == LightmapBakeType.Baked && light.bakingOutput.isBaked)
if (light.bakingOutput.lightmapBakeType == LightmapBakeType.Baked && light.bakingOutput.isBaked)
continue;

// If this light should not be included when ray tracing is active on the camera, skip it
Expand Down