Search Issue Tracker
Won't Fix
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
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.