Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.50f1
Issue ID
UUM-101120
Regression
No
"RenderingCommandBuffer" error is thrown when switching to the tvOS platform
*Steps to reproduce:*
# Create a new Universal 3D Unity project
# Open the Build Settings window (File > Build Settings)
# Switch to the tvOS platform
# Observe the Console window
*Actual results:* "RenderingCommandBuffer" errors are thrown in the Console window
*Expected results:* No errors are thrown in the Console window
*Reproducible with versions:* 2021.3.41f1, 2021.3.50f1
*Not reproducible with versions:* 2021.3.40f1, 2022.3.60f1, 6000.0.44f1, 6000.1.0b12, 6000.2.0a7
*Tested on (OS):* macOS Silicon Sequoia 15.3
Doesn't reproduce on Windows.
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
- "Create Empty Child" Option Creates Root Object When No Parent Is Selected
- Freeze/Crash when entering Play Mode in a specific project
- Lack of documentation regarding VFX Ray Tracing support
- Shader properties do not appear on the GameObject when switching ShaderGraphs during runtime in the Player
- Multiple '-' symbols are allowed to appear in a row when inputting '.' into a non-decimal numeric field
Resolution Note:
The error is shown during shader compilation, but it doesn't break anything. The behavior is the same in newer Unity versions, but the error is simply not logged. We won't change this behavior as it doesn't cause any issues and the error can be easily removed by cleaning the console messages.