Search Issue Tracker
Fixed
Fixed in 2022.3.67f1, 6000.0.58f1, 6000.2.6f1, 6000.3.0a5
Votes
0
Found in
2022.3.61f1
6000.0.48f1
6000.1.1f1
6000.2.0a10
6000.3.0a1
Issue ID
UUM-104071
Regression
No
Cubemap mipmaps display differently between Editor and Player when using custom mipmaps
Reproduction steps:
1. Open the attached “IN-99968“ project
2. Build and run for any platform
3. Observe the Player, compare to the Editor
Expected result: The spheres look just like in the Editor
Actual result: The spheres look slightly different
Reproducible with: 2022.1.0a5, 2022.3.61f1, 6000.0.48f1, 6000.1.1f1, 6000.2.0a10
Reproducible environments: macOS 15.4.1 (M3 Max)
Not reproducible environments: No other environments tested
Reproducible with these devices:
Standalone Player - macOS 15.4.1 (M3 Max)
VLNQA00516 - samsung Galaxy Fold (SM-F900F), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 10
VLNQA00558 - iPad mini 4 (WiFi) (MNY12B/A), CPU: Apple A8, OS: 10.3.1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment