Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.3f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131691
Regression
No
Texture rendered at different fidelity with Particle System Renderer when using a different material derived from the same texture with identical settings
How to reproduce:
1. Open the attached “IN-127332” project
2. Open the “StreamingMipmapTestScene”
3. Enter Play mode
4. Click the “Use Quality High” checkbox, in the Game view, to swap between High and Low Quality setting
5. Observe the Game view
Actual result: Both GameObjects at the top remain visibly lower fidelity
Expected result: All four GameObjects appear the same high fidelity
Reproducible on: 2023.1.0a3, 6000.0.65f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Reproducible with: macOS 26.2 (M1 Pro), Windows 11 (by the user)
Not reproducible with: No other environments tested
Notes:
- Two GameObjects at the top use Particle Renderer, while the ones at the bottom use Mesh Renderer
- Does not reproduce when the same exact material is used for Particle and Mesh renderers, in the example two materials are used, both derived from the same texture with identical settings
- The issue stops reproducing in the Editor, if the materials used are selected in the Project window, reopening the project or building a Player will cause the issue to reproduce again
- Also reproducible in Player
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
Add comment