Search Issue Tracker
Won't Fix
Won't Fix in 6000.4.X
Votes
0
Found in
6000.0.65f1
6000.4.0b6
Issue ID
UUM-132746
Regression
Yes
Baking APV using Linux/rusticl/Vulkan generates no probes
Steps to reproduce:
- Using Linux with Rusticl drivers installed, extract and open the attached project.
- Make sure Graphics API is set to Vulkan (may require restart).
- Open the “Assets/Scenes/TestWorld1.unity” scene
- Open Window → Rendering → Lighting
- Select “Adaptive Probe Volumes“
- Press “Generate Lighting“
Actual results: The process finishes successfully and no errors are thrown.
Expected results: Baking partially succeeds, APV baking silently fails
{}Reproducible on{}: 6000.2.0a4, 6000.2.10f1, 6000.3.0b9, 6000.4.0a4
{}Not reproducible on{}: 2023.1.0a4, 6000.0.61f1, 6000.2.0a3
{}Reproducible with{}: Ubuntu 24.04 (AMD 9070XT), Ubuntu 22.04 (Nvidia RTX 3500)
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
- Invalid Clip Method
- WebGPU error with Fantasy Kingdom and GPU Resident Drawer
- WebGPU fails with height fog in Fantasy Kingdom
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
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.
Resolution Note (6000.4.X):
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.