Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.0f3
Issue ID
830160
Regression
No
Grass mipmaps does not switch after adding a certain number of grass textures
(Check the attached *.gif file to see the bug)
Reproduction steps:
1. Open the attached project
2. Navigate to Assets
3. Open the main scene
4. Hit play
5. Observe the bug
or
1. Create a project
2. Create a terrain
3. Add grass texture (painted mipmaps, (*.DDS))
4. Add grass texture (*.PSD)
5. Repeat 'Step 4', till mipmapping will not work
Expected result: myWheat-1(*.DDS texture) color depends on the distance (DDS texture has colored four biggest mipmaps)
Actual result: myWheat-1(*.DDS texture) do not change the color
Reproduced with: 5.5.0b4, 5.4.0f3, 5.4.0f1, 5.3.1p3
Notes:
- This bug repro for custom mipmaps and for regular grass textures
- This bug repro in standalone builds as well
- 6 or more textures should be added in order to break mipmaps
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
- TreeView Child display toggle styling becomes reversed when clicking and dragging it
- Null is returned when using FocusOutEvent.relatedTarget
- Unity_BaseInstanceID is always zero when rendering multiple meshes and instancing with the same buffer
- UI Document button's text does not resize relatively when size in percentage (%) is used
- Event.current.mousePosition has an offset of 1px along the y-axis in WebGL build when the mouse button is released
Kusras
Dec 17, 2016 23:10
It is quite a while I reported this bug, so I have to ask if any progress is done? I would like to note that not only custom mipmaps does not work, I saw that regular grass (png textures) does not work properly if that limit is broke. This leads to extra performance as mipmap system does not working, and also lowering quality for nearby grass. And of course custom dds are impossible. I needed it for wheat as automatic mipmap did not show halm of the wheat, and it was not looking good looking on only flying top parts. custom mipmaps just lead me to discover this bug.