Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2018.4
2019.2
2019.3
2019.3.0b7
2020.1
Issue ID
1196495
Regression
No
Baking Reflection Probes results in an error message when a Reflection Probe's type is set to Realtime
How to reproduce:
1. Open the attached 'project-1196495.zip' project
2. In the Lighting window select 'Bake Reflection Probes' (found in the 'Generate Lighting' drop-down menu)
3. Observe the Console window
Expected result: an error message is thrown (Unknown reflection probe mode: 1)
Actual result: no error message is thrown
Reproducible with: 2017.4.35f1, 2018.4.13f1, 2019.2.14f1, 2019.3.0b12, 2020.1.0a14
Full error message:
'Unknown reflection probe mode: 1
UnityEditor.GenericMenu:CatchMenu(Object, String[], Int32)'
Additional note: baking the Reflection Probes for the first time does not result in the mentioned error and only the following bakes results in the error. Clearing Baked Data and then baking for the first time does not result in the error message.
-
djarcas
Jul 15, 2024 15:01
So what's the workaround? I can bake a reflectionprobe manually, but if I select 'bake all light probes' from the lighting tab, it fails with that error.
-
glenneroo
Feb 05, 2022 14:06
I don't understand the "resolution note" - are they saying this is not a bug?
-
xraycaster
Jun 28, 2020 06:09
Could you please at least remove the error logging if this is not an actual issue?
I also got the error messages and they are not boosting my confidence if the error messages are working or not.
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
- Profiling information icon does not update for Light Mode
- [Linux] Type to select functionality is missing for drop down menus
- TextMeshPro calculates Width Compression incorrectly when using certain values in the WD% field
- VFX Graph link contrasts fail WCAG guidelines
- D3D12 PSO disk cache feature crashes if paths contain non-ASCII characters
Resolution Note (2020.1.X):
This issue has been identified as having low priority and has been closed without a fix. If the bug has no workaround and is blocking your production, please feel free to reopen it with any additional information you might have. Sorry for the inconvenience this might cause.