Search Issue Tracker
Fixed in 2017.2.0f3
Votes
0
Found in
5.3.5f1
Issue ID
822397
Regression
No
[Editor] Changing game view size doesn't update Camera.ViewportToWorldPoint value until next frame
Steps to reproduce:
1. Open attached project
2. Open scene "scene"
3. In game view, make sure that Maximize on play is checked and enter play mode
4. Run scene and notice output in the game view - it shows that ViewportToWorldPoint value is same after Screen.width is changed and only updates in the next frame while Screen.width is updated instantly
Note: doesn't happen when resizing game view BUT happens when game view is resized by resizing whole editor. Only reproducible on editor
Reproduced with: 5.2.4f1, 5.3.6p3, 5.4.0p2, 5.5.0a6
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
Add comment