Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2021.3.7f1
2022.1.12f1
2022.2.0b3
2023.1.0a4
2023.2.0a1
2023.3.0a3
Issue ID
UUM-11630
Regression
No
Performance, FPS issues when using the MacOS Dedicated Server Build
Reproduction steps:
- Open the attached project
- Open the “/Assets/Cubes/Cubes.unity” Scene
- Change the Build Platform to MacOS (File > Build Settings > Windows, Mac, Linux)
- Press the “Switch Platform” button and then the “Build And Run” button
- Observe the FPS counter in the Player
- Exit the Player and change the Build Platform to Dedicated Server (File > Build Settings > Dedicated Server)
- Press the “Switch Platform” button and then the “Build And Run” button
- Observe the FPS counter in the Dedicated Server’s Console
Expected result: Performance between the different Build Platforms is the same
Actual result: Dedicated Server Build is performing a lot worse than the MacOS Build
Reproducible with: 2021.3.7f1, 2022.1.12f1, 2022.2.0b3, 2023.1.0a4
Could not test with: 2020.3.37f1 - Mac Dedicated Server Build Support module is not available
Reproducible on: M1 MacOS 12.4 (21F79)
Not reproducible on: Windows 10 (21H2), Intel MacOS 12.4
Note: This issue is reproducible on both the Apple Silicon and Intel Editors using the M1 Mac
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
- Crash on ExtractHandles when shutting down the Editor in a specific scene while Burst jobs are in progress
- Unity Hub closes with no "Project is currently open" window when selecting an already open project from the Projects list
- The Hub freezes indefinitely when copy/pasting a lot of characters in the “Set project display name” Hub window since it has no character limit
- Inconsistent “Favorites” icon highlight in Unity Hub
- "Could not connect project. Try again" Hub error is not informative/does not inform the user with the reason why it failed when connecting a project to cloud with a name that's too long
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2023.3.X):
There are no fixes planned for this Bug