Search Issue Tracker
Fixed in 0.16.0
Votes
0
Found in [Package]
0.14.0-preview.18
Issue ID
1258802
Regression
No
Entities rendered are not influenced by volume indirect diffuse intensity
How to reproduce:
1. Open the attached "HDRPSpawnLightingDOTS"
2. Open up the SampleScene
3. Observe in the Scene view there are three cubes bright, less bright, and bright (the middle one (less bright) is part of the subscene 'sub')
Expected: the object from the subscene should look like the rest of the cubes in the scene
Actual: the cube from the subcsene is less bright (see the seneview.png attached in the Edit section)
4. Enter play mode
5. Observe that the cube on the left is converted to an entity and is now less bright (like the one from the subcene)
Expected: in play mode entities converted from game objects should look the same as they do before they are converted
Actual: converted entities look less bright (see the gameview.png attached in the Edit section)
Reproducible with: 2019.3.16f1, 2019.4.3f1, 2020.1.0b15, 2020.2.0a16
Note:
-Different behavior on macOS, cubes brightness looks like in gameview.png
-Could not test with earlier versions because of the thrown errors
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
- Mouse device is disabled in Play Mode when the "Device Simulator" tab is present as an inactive tab and Game view is not maximised
- GameObject with the Visual Effect Component is not rendered in the Scene view when it is reenabled in the Inspector and the Play mode is paused
- Prefab icon blends in when selected in Project window with the Light Editor theme enabled
- Textures from other Sprites in the Assets leak into Sprite Renderer Sprites when Sprite Atlas v2 is used
- Errors “UI Error: Invalid GUILayout state in TestRunnerWindow view“ and “ArgumentException: An item with the same key has already been added“ are present when running tests with names that duplicate after truncation in the Test Runner window
Resolution Note (fix version 0.16.0):
This issue is fixed in the latest DOTS master (it has been for a few weeks)