Search Issue Tracker
By Design
By Design in 6000.0.X
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.
Resolution Note (6000.0.X):
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.