Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.1.0f2
Issue ID
702370
Regression
No
OSX Standalone Player using -batchmode command line argument uses up about 70% CPU
How to reproduce:
1. Open attached project
2. Open scene main.unity
3. Build to OSX Standalone
4. Run the standalone build with the -batchmode command line argument
- Activity Monitor shows that the standalone build uses up a huge amount of CPU
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment