Search Issue Tracker
By Design
By Design in 2023.2.X
Votes
0
Found in
2020.3.46f1
2021.3.20f1
2022.2.9f1
2023.1.0b7
2023.2.0a5
Issue ID
UUM-28805
Regression
No
“MultiThreaded” is printed when using “SystemInfo.renderingThreadingMode” if the “Multithreaded Rendering” setting is disabled in the Player Settings
How to reproduce:
1. Open the user’s attached “1487097_MultiThreadRendering.zip” project
2. Press Menu > UnitySupport > Check Rendering Thread Mode
3. Observe the Console window
Expected result: “SingleThread” is printed
Actual result: “MultiThreaded” is printed
Reproducible with: 2020.3.46f1, 2021.3.20f1, 2022.2.9f1, 2023.1.0b7, 2023.2.0a5
Reproduced on: macOS 13.2.1 (Intel)
Note: In 2020.3.46f1 and 2021.3.20f1 editors, the “Multithreaded Rendering” setting is not in the Player settings, but the issue still reproduces
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
- 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
Resolution Note:
by design we use multi threaded rendering, there are issues with it at the moment, which our teams are currently working on.
Resolution Note (2023.2.X):
by design we use multi threaded rendering, there are issues with it at the moment, which our teams are currently working on.