Search Issue Tracker
By Design
By Design in 2023.3.X
Votes
1
Found in
2021.3.20f1
2022.2.9f1
2023.1.0b6
2023.2.0a4
2023.3.0a3
Issue ID
UUM-29276
Regression
No
[WebGL] Bilinear Upscaling Filter is applied to the Build when Nearest-Neighbor Upscaling Filter is selected
Reproduction steps:
1. Open the attached “repro-project“ project
2. Build And Run project on WebGL
3. Observe the Build
Expected result: Nearest-Neighbor Upscaling Filter is applied to the Build
Actual result: Bilinear Upscaling Filter is applied to the Build
Reproducible with: 12.1.10 (2021.3.20f1), 14.0.6 (2022.2.9f1), 15.0.4 (2023.1.0b6), 16.0.0 (2023.2.0a4)
Could not test with: 10.10.1 (2020.3.45f1) (Due to errors in the Console window)
Reproduced on: Windows 10
Not reproduced on: macOS Monterey 12.6 (Intel)
Note: Not reproducible on Standalone Builds
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- 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
Resolution Note:
Works as expected. Tested with 21.3.32f1. The textures appear to be point sampled as expected. Switching the textures to use bilinear looks clearly different.
Resolution Note (2023.3.X):
Works as expected. Tested with 21.3.32f1. The textures appear to be point sampled as expected. Switching the textures to use bilinear looks clearly different.