Search Issue Tracker
Fixed
Fixed in 2023.3.X, 2023.3.0a13
Votes
0
Found in
2023.3.0a7
Issue ID
UUM-49770
Regression
Yes
HLSL node breaks compilation
How to reproduce:
- Create a new graph and add it to the scene
- Add custom HLSL block to Update context
- Save graph
Observe that vfx is no longer rendered and error is thrown to the console
Note: couldn't repro on 2023.3.0a3
Unity cannot compile the VisualEffectAsset at path "Assets/TEST hlsl/Main Graph.vfx" because of the following exception:
UnityEngine.UnassignedReferenceException: The variable m_ShaderFile of CustomHLSL has not been assigned.
You probably need to assign the m_ShaderFile variable of the CustomHLSL script in the inspector. at UnityEngine.Object+MarshalledUnityObject.TryThrowEditorNullExceptionObject
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- Long Sprite names are not truncated in the Inspector window name label and the preview labels when a Sprite with a long name is selected
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
Add comment