Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.19.19
1.20.5
Issue ID
ADDR-2985
Regression
No
[Addressables][Windows] Object is colored incorrectly in Game view when using addressables
Reproduction steps:
# Open the “Viewer Test” Project contained in “ShaderBug.zip”
# Open “TestScene” Scene
# Enter the Play mode
Expected result: Grey colored cube is visible in the Game view
Actual result: Rainbow colored cube is visible in the Game view
Reproducible with: 1.19.19 (2021.3.10f1), 1.20.5 (2022.1.17f1, 2022.2.0b8, 2023.1.0a11)
Could not test with: 2020.3.40f1 (“Partial constant buffer not found.” when entering Play mode)
Reproducible on: Windows 10
Not reproducible on: macOS 12.5
Note: This works as expected in build. The issue is only reproducible in Editor.
-
TechCor2
Jan 25, 2023 21:50
The resolution says:
"The issue is that the build target is a non-standalone platform in the editor"
This is not true. The bug occurs when the platform is set to Windows, Mac, Linux with Target set to Windows.
"Due to how shader compilation works across various platforms, AssetBundles built for platform (like Android) won't display correctly inside of the Editor."
The bundles are built for Windows 64-bit standalone platform.
In other words, the Windows 64-bit bundles do not display correctly in the Windows 64-bit Editor with the platform set to Windows 64-bit standalone.
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
- Blue highlights appear when some of the UI Builders panels are focused
- Property fields overlap in the Override window when comparing changes
- "Timeflow Animation System" custom package appears twice in the Package Manager
- Sprite Atlas Override for iOS setting remains disabled when saving its change to enabled
- Increased Memory usage when Update Mode 'On Demand' Realtime lights are used and DX12 API is selected
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.