Search Issue Tracker
Won't Fix
Fixed in 5.6.X
Votes
0
Found in
5.6.0b7
Issue ID
880654
Regression
Yes
Quality Settings' Anisotropic Textures set to Forced On will enable anisotropic filtering on texture where it's set to 0
When "Anisotropic Textures" is set to "Forced On" in "Quality Settings" it'll apply anisotropic filtering to all textures, even if a texture explicitly has aniso disabled. This is a problem when you don't want anisotropic filtering (as in this case, for color grading using a LUT).
(note that I stripped the project to a bare minimum and I removed a bunch of shader keyword from the PostProcessing/Uber shader to make compilation times faster)
Repro steps:
- Open the "Test" scene.
- Build a player on mac/metal (the project should already be configured) and run the build.
- The box on screen has a small green outline.
- Go to quality settings, disable Anisotropic Textures or set it to "Per Texture".
- Build & start again.
- No more green outline, expected result.
Reproduces in Metal, DX9, DX11, DX12 and Vulkan
Doesnt reproduce in GLCore
Reproduced: 5.6.0a1, 5.6.0b8
Not reproduced: 5.5.1p3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Add comment