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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 3.1.5):
Fixed in 3.1.5 (next release)