Search Issue Tracker
Fixed
Fixed in 2021.3.29f1, 2022.2.18f1, 2023.1.0b15, 2023.2.0a8
Votes
0
Found in
2021.3.20f1
2022.2.9f1
2023.1.0b7
2023.2.0a5
Issue ID
UUM-30050
Regression
No
"'ApplyMeshModification': no matching 2 parameter function" shader error when VFX uses custom output shaders
How to reproduce:
1. Open the attached project “UnityBugVFXApplyMeshModification.zip“
2. Select the “Hidden/VFX/MyVFX/System/Output Particle Unlit Quad“ shader (Assets/MyVFX)
Expected result: There is no error in the Console
Actual result: “ApplyMeshModification': no matching 2 parameter function“ error in the Console
Reproducible with: 2021.3.20f1, 2022.2.9f1, 2023.1.0b7, 2023.2.0a5
Can’t test with: 2020.3.45f1 (“InvalidOperationException: SystemNames : Model is not registered” error in the Console when opening the project)
Reproduced on: macOS 13.0.1 (Intel), Windows 10 (by reporter)
Note: The outlines of the VFX particles are rendered incorrectly when the “MyVFX” GameObject in the “OutdoorsScene“ Scene is rotated on the Y axis
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment