Search Issue Tracker
Fixed in 2022.3.60f1
Fixed in 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X, 6000.2.0a5, future release
Votes
0
Found in
2021.3.45f1
2022.3.52f1
6000.0.26f1
6000.1.0a3
6000.2.0a1
Issue ID
UUM-86941
Regression
No
Graphic components errors when running Dedicated Server Build/Standalone build at headless runtime
Steps to reproduce:
1. Open the attached user's project "Particles1973892.zip"
2. Build for MacOS or Windows Standalone
3. Run "<Path_To_Project> -batchmode -nographics -logFile <Path_To_Project>\Particles1973892.log --args" in CMD or Terminal
4. Open the generated "Particles1973892.log" and observe "Invalid VFX Particle System. It is skipped" error printed
Expected results: since the build is in headless, it shouldn't get that far into graphics stacks, or at least not throw graphic errors
Actual results: particle system is being generated at headless runtime
Reproducible with: 2021.3.45f1, 2022.3.52f1, 6000.0.26f1, 6000.1.0a3
Testing Environment: Windows 11 23H2, macOS 14.5 (user)
Not reproducible on: no other environment tested
Notes:
-Issue reproduces in Standalone player an Dedicated Server Build
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
Add comment