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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
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