Search Issue Tracker
Fixed
Votes
0
Found in
5.5.0f2
Issue ID
863256
Regression
Yes
Using OverrideGeometry on instantiated sprite produces different results in build than in editor
How to reproduce:
1. Open user provided project
2. Enter play mode and note that all sprites change to yellow
3. Build for Standalone
5. Launch built application
5. Notice the sprite that gets instantiated is different from others
Expected behaviour: OverrideGeometry behaviour is consistent between editor and built app
Actual behaviour: Using OverrideGeometry on instantiated sprite produces unexpected results.
Reproduced on: 5.4.2p1, 5.4.3f1, 5.4.4f1, 5.5.0p3, 5.6.0b2
Not reproduced on: 5.3.7p3, 5.4.0f1, 5.4.1f1, 5.4.2f1, 5.4.2f2
Regression introduced in: 5.4.2p1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment