Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0f2
Issue ID
1056057
Regression
No
Script fails to transform Camera position in build only
How to reproduce:
1. Open the attached project and enter the Play mode
2. Select "Singleplayer" -> "New Game" -> "Player - Player" -> "Computer - AI (Normal)" and click "Start"
3. Observe the Camera Position and exit Play mode
4. Build the Project
5. Repeat step two
6. Observe the Camera Position in the Build
Expected result: The camera position is the same as in the Editor
Actual result: The starting camera position shifts in the Build only
Reproduced in: 2018.3.0a4, 2018.2.0b11, 2018.1.7f1
Couldn't test with: 2017.4.6f1, 2017.2.3p2, 2017.1.4p2
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
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
- Crash after the “State comes from an incompatible keyword space“ log when opening the project
- [Android] GameObject are not rendered at all or rendered black when in the custom shader “multi_compile_instancing“ is enabled with two “float4” instance properties are present on older devices
- LineRenderer.BakeMesh generates a box-shaped MeshCollider when the camera's Y-axis rotation is in a specific range
- Different build sizes between Editor build and command-line build when "Static Batching" is enabled
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.