Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.57f1
6000.2.3f1
6000.3.0b1
Issue ID
UUM-116108
Regression
No
Adaptive Probe Volume “No Adaptive Probe Volume in Scene” warning is shown only on the first time and is never shown again when baking the Adaptive Probe Volumes with all the Adaptive Probe Volume components disabled
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Create a new "Adaptive Probe Volume" GameObject (GameObject > Light > Adaptive Probe Volume)
- Select the newly created Adaptive Probe Volume in the Hierarchy window
- Press the "Open" button in the Inspector window under the Adaptive Probe Volume component
- Change the Light Probe System to "Adaptive Probe Volumes" in the opened Lighting settings
- Open the Lighting window (Window > Rendering > Lighting)
- Open the Adaptive Probe Volumes tab in the Lighting window and close the Lighting window
- Repeat step 3 and disable the Adaptive Probe Volume component
- Press the "Bake Probe Volumes" button in the Inspector window
- Press "No" in the popup warning
- Repeat step 9
- Observe the Editor
Actual results: The warning popup never appears again
Expected results: A warning popup appears again or the "Bake Probe Volumes" button is greyed out like with Reflection Probes
Reproducible with versions: 6000.0.57f1, 6000.2.3f1, 6000.3.0b1
Tested on (OS): macOS Silicon Sequoia 15.6.1
Notes:
- Does not reproduce with Reflection Probes, the “Bake” button is greyed out when the component is disabled
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.