Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.2.16f1
2021.2.17f1
2021.3
2022.2.0a8
Issue ID
1416268
Regression
Yes
Shaders takes a long time to compile when using the Volumetric Lights
How to reproduce:
1. Open the attached project "ShaderCompLong.zip"
2. Open the "Demo" Scene (Assets/VolumetricLights/Demos/Minimal/Scene)
Expected result: The Shader compilation takes a few seconds to finish
Actual result: The Shader compilation takes around 20min. to finish
Reproducible with: 2021.2.16f1, 2021.2.19f1, 2021.3.0f1, 2022.2.0a8, 2022.2.0a10
Not reproducible with: 2019.4.37f1, 2020.3.33f1, 2021.2.15f1, 2022.1.0b15, 2022.2.0a7
Comments (1)
-
Kronnect
Apr 27, 2022 05:23
This issue only happened in 2021.x and was fixed in latest version (5.0) of Volumetric Lights.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Resolution Note (2022.2.X):
I double-checked, the time is spent inside the FXC compiler, so there's nothing we can really do about it.
Adding a "[loop]" attribute before the loop with many iterations in Raymarch.hlsl fixes the issue.