Search Issue Tracker
By Design
Votes
0
Found in
Issue ID
1417899
Regression
No
[HDRP APV] Probe values change when subdivision levels are adjusted
We discussed with Adrien and not sure if this is an intended behaviour so making a report to track and clarify. When subdivision level is changed, some probes dont change position (which is expected) but for some reason the value of captured light changes.
Repro:
1) Open spotlight tunnel project apv branch https://github.com/iM0ve/Spotlight-HDRP/tree/APV
2) Load main scene, then add Day
3) Bake lighting.
4) Switch to the first camera
5) Take a screenshot of the probes
6) Reduce the APV simplification levels from 27m to 9m
7) Bake
8) Take screenshot
9) Compare the results
Expected: The probes that did not move, should not change visually because they receive the same amount of light as before.
Actual: The probes that did not move get brighter/darker, sometimes light angle changes.
Note: In the screenshots red brick outlines are missing for a portion of probes, im not sure whats this about but its not the core problem of this fogbuz.
Tested on apv-staging2
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Number of steps is not high enough so result doesn't converge
When order of probes changes ie when subdiv count changes, values changes