Search Issue Tracker
By Design
Votes
0
Found in
2020.3.42f1
2021.3.14f1
2022.1.23f1
2022.2.0b16
2023.1.0a20
2023.2.0a1
2023.3.0a3
6000.0.0b11
Issue ID
UUM-19827
Regression
No
Frame count is twice slower in Build than it is in Editor
Reproduction steps:
1. Open the attached “IN-20935_input-system.zip“ project
2. Open “MousePonterRecorder” scene
3. Disable Development Build in Build Settings
4. Enter Play mode
5. Observe Console log. The framerate between two presses is 235 frames
6. Enable Development Build in Build Settings and build the project
7. Run the game and wait for two errors to appear. The framerate between two presses is 470 frames
Expected result: Project runs at the same framerate in Editor and Build
Actual result: Project framerate is twice slower in Build than it is in Editor
Reproducible with: 2020.3.42f1, 2021.3.14f1, 2022.1.23f1, 2022.2.0b16, 2023.1.0a20
Reproduced on: macOS Monterey 12.6 (Intel)
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
This is by design. Framerate is higher in a build compared to editor playmode.
If you measure actual time passed it should come out as a the same.