Search Issue Tracker
Fixed in 5.10.0-preview
Votes
0
Found in [Package]
4.10.0-preview
Issue ID
1140863
Regression
No
Visual Effect Graph logs warnings everytime when Unity finishes compiling
Reproduction steps:
1. Create an empty Unity Project
2. Using the Package Manager, install Core RP Library and Visual Effect Graph
3. Wait for the Packages to download and for Unity to recompile
Expected: after recompiling Unity does not throw any warnings
Actual: after recompiling Unity throws warnings regarding Visual Effect Graph
Reproduces on: Unity Version 2018.3.12f1 and Package Version 4.10.0-preview
Does not reproduce on: Unity Version 2019.1.0b9, 2019.2.0a10 and Package Version 5.10.0-preview
Note:
- Visual Effect Graph version 5.10.0 is not available on Unity Version 2018.3.12f1
- Warnings:
Library\PackageCache\com.unity.visualeffectgraph@4.10.0-preview\Editor\Models\Operators\Implementations\ChangeSpace.cs(12,28): warning CS0649: Field 'ChangeSpace.m_targetSpace' is never assigned to, and will always have its default value
Library\PackageCache\com.unity.visualeffectgraph@4.10.0-preview\Runtime\Utilities\Playables\VisualEffectActivation\VisualEffectActivationBehaviour.cs(39,26): warning CS0649: Field 'VisualEffectActivationBehaviour.clipExitEventAttributes' is never assigned to, and will always have its default value null
Library\PackageCache\com.unity.visualeffectgraph@4.10.0-preview\Runtime\Utilities\Playables\VisualEffectActivation\VisualEffectActivationBehaviour.cs(37,26): warning CS0649: Field 'VisualEffectActivationBehaviour.clipEnterEventAttributes' is never assigned to, and will always have its default value null
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment