Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.2.X
Votes
0
Found in
5.4.0p1
Issue ID
827127
Regression
No
Colliding points are always different after reloading scene with f1.
Steps to reproduce:
1. Open attached project in the 5.5.0b1
2. Open test scene
3. Go into the play mode
4. Adjust screen layout so you could see scene mode
5. press mouse left mouse button.
6. press f1(scene reload)
7. press mouse button again
- Arrow hits different points
If you are unable to reproduce just keep repeating steps 6,7.
The red dot indicates where the collision was detected.
Note: in 5.4.x arrow collision with "Tower_Normal" has big offsets but it does not reproduce in 5.5
Expected result: arrow should always hit the same place.
Current result: Colliding points are always different after reloading scene.
Reproduced on: 5.5.0b1, 5.4.0p2,5.4.0f3
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