Search Issue Tracker
Fixed in 2.6.10
Votes
0
Found in [Package]
2.6.9
Issue ID
1359831
Regression
Yes
Cinemachine internal code error "CS1513: } expected", when switching from 2.6.5 to 2.6.9 versions
How to reproduce:
1. Open the attached project "Prj3.5.zip"
2. Open the Package Manager window
3. Change Cinemachine to 2.6.5
4. Change back Cinemachine to 2.6.9
Expected result: No errors
Actual result: Error: "Library/PackageCache/com.unity.cinemachine@2.6.9/Editor/PostProcessing/CinemachineVolumeSettingsEditor.cs(240,2): error CS1513: } expected"
Reproducible with: Cinemachine 2.6.9 (2019.4.30f1, 2020.3.18f1, 2021.1.20f1, 2021.2.0b10, 2022.1.0a7)
Not reproducible with: Cinemachine 2.6.5, 2.6.10 (2019.4.30f1, 2020.3.18f1, 2021.1.20f1, 2021.2.0b10, 2022.1.0a7)
Note: In some versions of the Unity Editor, you can't change the version in the Package Manager, do that by going into Manifest.json in the Packages folder of the project
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 2.6.10):
Fixed in: 2.6.10