Search Issue Tracker
Fixed
Fixed in 3.1.5
Votes
0
Found in [Package]
3.1.4
Issue ID
CMCL-1712
Regression
No
Nothing indicates a missing PixelPerfect Component when using a CinemachinePixelPerfect Extension
How to reproduce:
1. Create a new 2D URP project
2. Create a Cinemachine Camera (any camera works) and select it
3. Add the “CinemachinePixelPerfect“ extension in the Inspector
4. Observe the “CinemachinePixelPerfect“ Component below in the Inspector
Expected result: A warning is shown that indicates that no main Pixel Perfect Component was found in the Scene (or on CinemachineBrain)
Actual result: No warning is shown
Reproducible in: 2.9.0-pre.1 (2023.1.0a1), 3.1.4 (6000.0.57f1, 6000.2.4f1, 6000.3.0b1)
Reproduced on: Windows 11 Pro, macOS 15.3.1
Not reproduced on: No other environment tested
Note: The main PixelPerfect Component is required for the extension to work correctly, so showing a warning when there is no such component detected is crucial for user experience
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 3.1.5):
Fixed in 3.1.5 (next release)