Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
1.9.2
Issue ID
UVSB-2539
Regression
No
Cannot change the "Volume" Component's fields through Visual Scripting
How to reproduce:
1. Open the “PostProcessingVolumeVisualScriptingIssue“ project
2. Open the “Post-processVolume” scene
3. Enter Play Mode
4. Press “F1” on the keyboard
5. Observe the “Cube” GameObject “Volume” Component’s Bloom “Intensity” field
Expected result: The “Cube” GameObject “Volume” Component’s Bloom “Intensity” field is changed
Actual result: The “Cube” GameObject “Volume” Component’s Bloom “Intensity” field is not changed
Reproduced with: 1.8.0 (2023.2.16f1), 1.9.2 (2021.3.36f1, 2022.3.22f1, 2023.2.16f1, 6000.0.0b13)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
1. Reproducible in the Player
2. Full error is provided in the internal comments
Comments (2)
-
Ignacii
May 08, 2024 14:54
Haha, good job. Finally. Thanks. Looks like I've never tried this combo. Issue resolved... For now... :D
-
Ignacii
Mar 27, 2024 15:14
Incorrect bug report. Misunderstood by the Customer QA. Updated the case at Unity Bug Reporting Portal.
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:
There are no fixes planned for this Bug