Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2022.2.1f1
2023.1.0a23
2023.2.0a14
Issue ID
UUM-30997
Regression
No
Lighting is not rendered on a BatchRendererGroup mesh when the scale is less than 0.01
Reproduction steps:
1. Open the attached project “BRGProject”
2. Open the “Assets/Scenes/SampleScene.unity” scene
3. In the Hierarchy window select the “boat” GameObject
4. Observe its scale value from the Inspector window
5. Enter Play Mode
6. On a Keyboard, adjust the scale of the “middle boat” (Entity) and “right boat” (GameObject) by pressing NumpadPlus and NumpadMinus
7. Observe the Light rendering on the “middle boat” Entity in the Game View
Expected result: Lighting is rendered correctly on the “middle boat” when the scale is <0.01
Actual result: Light is not rendered on the “middle boat” Entity when the scale is <0.01
Reproducible with: 1.0.0-pre.14( 2022.2.1f1, 2023.1.0a23)
Could not test with: 1.0.0-pre.15 ( 2022.2.1f1, 2023.1.0a23) (users scripts errors with entity graphic package version), 2022.2.0b4 and below ( Entities Graphics Package is not supported)
Reproducible on: Intel macOS 13.0.1
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.