Search Issue Tracker
Not Reproducible
Votes
1
Found in
5.4.0f3
Issue ID
854587
Regression
Yes
When vSync is off, and Maximize on Play is on, Gfx.WaitForPresent makes fps to stay only at ~100-200fps
To reproduce:
1. Open project "Hydroform Water".
2. Go to Edit -> Project Settings -> Quality. And set "V Sync Count" to "Don't Sync".
3. In Game View enable "Maximize On Play" and "Stats".
4. Open and Play "storm" scene. (Fps is at around 100-200 FPS)
5. Open new Window (Asset Store, Profiler or any other) and drag it around. (FPS increases to the normal fps)
2nd way to reproduce (was possible to repro in this way only on win7 and win8.1 PCs):
1. Create new project.
2. Go to Edit -> Project Settings -> Quality. And set "V Sync Count" to "Don't Sync".
3. In the Game window, press "Maximize on Play" and "Stats".
4. Play scene. You should be getting around 150-200 fps or less.
5. Open "Asset Store" (or other window).
6. Move "Asset Store" window around. FPS will increase a lot (to 1000-2000 fps at least). Basically you get FPS which should be normal, when vSync is off.
Actual result: When vSync is off, and game is "maximized" fps is capped at 100-200fps, because of Gfx.WaitForPresent.
Expected result: When vSync is off, fps is not capped.
Reproducible with: 5.4.2f2, 5.5.2p4, 5.6.0f2, 2017.1.0a4
Not reproducible: 5.2.3f1, 5.3.4f1
Reproduced on:
Windows 8.1 Enterprise 64-bit, NVIDIA GeForce GTX 660, directx 11
Windows 7 Pro, AMD Radeon HD 6670, directx 11
Windows 10 Pro, NVIDIA GeForce GTX 570, directx 12
-
SilverStorm
Dec 09, 2017 06:56
*Update I can confirm building the project does contain this bug.
I downloaded an fps script so I could see my frame rate.
While in windowed mode full screen the fps is about 1300 on average.
While not in windowed mode, so full screen the fps becomes 140.Keep in mind that this scene example only has some simple Textmesh Pro stuff in it no 3d objects or effects. (TMP is not the cause of this bug).
-
SilverStorm
Dec 09, 2017 05:33
So this same error which was reproduced a year ago still hasn't been found? Jesus....
For now a temporary workaround is to leave your editor almost maximized but not quite.
As long as the editor is not maximized fully - and you can tell this because you get two small windows next to the close editor window "x" button then your fps should not be impacted.I am as of yet unsure if this issue occurs in a published build.
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
- Only the left screen is rendering when using Render Graph Fullscreen Blit in Meta Quest 2
- Context menu with the "Revert" option doesn't appear when pressing the right mouse button on a "Vector2" or "Vector3" property in the Inspector of a custom shader
- Missing Render Feature "Full Screen Pass Render Feature" in any “Universal Renderer Data” asset when upgrading from 2022.3
- Inconsistent ParticleSystemVertexStream.PercentageAlongTrail data range in Trail Texture Modes except "Stretch"
- The Graph Debug Window can be right clicked through and the Node Workspace is manipulated instead
Resolution Note:
Does not seem to affect Unity 2017.4 or above.