Search Issue Tracker
Fixed in 2017.2.0f3
Votes
0
Found in
2017.2.0b7
Issue ID
942659
Regression
Yes
Console "RenderTexture.GenerateMips failed" errors are thrown when entering Play mode
To reproduce:
1. Open the "DefaultScene" in the user-provided project
2. Enter Play mode
3. Observe Console window
Desired outcome: Entering Play mode does not cause Console errors.
Actual result: Entering Play mode causes "RenderTexture.GenerateMips failed: render texture does not have mip maps (set useMipMap to true)" errors.
Reproduced with 2017.1.0p4, 2017.2.0b7, 2017.2.0b8, 2017.3.0a4
Not reproduced with 5.5.4p3, 5.6.3p1, 2017.1.0p3, 2017.2.0b6, 2017.3.0a3
Regression introduced in 2017.1.0p4, 2017.2.0b7, 2017.3.0a4
------------------------------------------------------------------------------------------------
Fixed in: 2017.2.0b11
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
- 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
ArturoOtherside
Nov 15, 2017 20:43
Seems to be a reflection probe data issue. I turned them all to "realtime" and it went away. When I look at any individual image from a reflection probe box bake, it has a "mipmap" box off that I cant turn on.