Search Issue Tracker
Fixed
Fixed in 2023.3.0b8
Votes
0
Found in
2023.3.0b5
Issue ID
UUM-63204
Regression
Yes
[HDRP] Regression of performance on tansparent rendering
Steps to reproduce:
Look at dashboard
[https://observer.ds.unity3d.com/project?projectID=HDRP&test=&sample=Timing,GPU,ForwardTransparent&changeset=&testVersion=undefined&pivot=project&pinVersions=false&configurations=%5B%22PS4Orbis%20x64GnmIL2CPP%20PlayStation4%22%5D&platform=PS4&offset=0&editorBranch1=trunk&projectBranch1=trunk&fromVersion1=2023-11-15T11:43:47Z&toVersion1=2023-11-20T19:13:43Z&color1=9900ef]
Observe that
On the scene about {{Lighting}} with lot of lightst (area + line), we go from 6.7ms to 7.2ms on PS4
on the scene {{Others}} without area light, we go from 2.42ms to 2.68ms
Result of the bisection give us this PR: [https://github.cds.internal.unity3d.com/unity/unity/pull/39296]. cause the performance regression
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment