Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.23.1
2.3.16
Issue ID
ADDR-3887
Regression
No
PixelPerfectCamera Component's "Crop Frame" field resets to "None" when transitioning to an Addressable Scene
How to reproduce:
1. Open the “IN-94722.zip“ project
2. Open the “MainMenu” Scene
3. Open the Window > Asset Management > Addressables > Groups
4. Change the Play Mode Script to “Use Existing Build“ and build the Addressables
5. Enter Play Mode
6. Press on the button in the Game view
7. Select the “Main Camera“ GameObject in the Hierarchy
8. Scroll down and observe the Pixel Perfect Camera Component in the Inspector
Expected result: The “Crop Frame“ field stays at “Stretched Fill”
Actual result: The “Crop Frame“ field changes to “None”
Reproducible in: 1.23.1 (2022.3.58f1), 2.3.16 (6000.0.40f1, 6000.1.0b7, 6000.2.0a5)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- Other fields of the same Component or other Components do not change
- Not reproducible if “Use Asset Database“ is used for the Play Mode Script
- After Scene transition, some Components (most noticeably Cinemachine) seem to have corrupted icons, and I believe it is related to the reported issue
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
- Location tooltip in the Viewport of UI Builder window does not update when the UI Document Asset is moved to a different location
- Audio Clip Volume and Avoid Repeating Last fields values cannot be changed in Audio Random Container window
- Setting a variable in the root selector via an imported USS file in a theme does not work
- No character limit when creating a new Scene with excessively long name, Editor can be forced to crash
- URP Decal Projector flickers/glitches when added to Cube or Quad GameObjects as a Component
Resolution Note:
Hey,
Thank you sincerely for raising this report and bringing it to our attention.
We’ve discussed the dropdown issue a few times, but we’re continuing to focus on higher-priority areas within Addressables. Those priorities are guided by the severity, frequency, and overall impact on users.
Given that, it’s hard to see when we’ll have the dedicated time to investigate a fix properly. I’m going to close the issue for now, but we’ve kept your notes and sample project on hand for when we next revisit this part of the codebase.