Search Issue Tracker
Won't Fix
Won't Fix in 2022.1.X
Votes
0
Found in
2021.3.11f1
2022.1.18f1
Issue ID
UUM-15202
Regression
No
[Ubuntu 20.04] Editor does not open when creating Cinematic Studio template project
How to reproduce:
1. Open UnityHub
2. Click Create Project
3. Find Cinematic Studio template and click Download Template
4. Click Create project after download is complete
5. Observe that after loading for some time loading screen just disappears
Expected results: Editor opens
Actual results: Editor does not open
Reproduced on all streams and version that has this template: 2021.3.11f1, 2022.1.18f1. (Other stream does not have Cinematic Studio)
Notes:
- Not 100% reproducible, but was able to consistently reproduce on bokken (Ubuntu 20.04)
- Also was able to reproduce on CentOS
- See attached Editor.log
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Looking at the last two lines of the log:
[Vulkan init] Physical Device 0x559119597b00 [0]: "llvmpipe (LLVM 12.0.0, 256 bits)" deviceType=4 vendorID=10005 deviceID=0
[Vulkan init] Selected physical device (nil)
Linux editor is running on LLVM Software renderer which is not a supported configuration.
Resolution Note (2022.1.X):
Looking at the last two lines of the log:
[Vulkan init] Physical Device 0x559119597b00 [0]: "llvmpipe (LLVM 12.0.0, 256 bits)" deviceType=4 vendorID=10005 deviceID=0
[Vulkan init] Selected physical device (nil)
Linux editor is running on LLVM Software renderer which is not a supported configuration.