Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
1.5.2
Issue ID
UVSB-1431
Regression
Yes
[Visual Scripting] Plastic SCM and Visual Scripting packages throw multiple precompiled assemblies errors when installed
Reproduction steps:
1. Create a new project
2. Install Visual Scripting and Plastic SCM from the asset store (https://assetstore.unity.com/packages/tools/utilities/plastic-scm-plugin-for-unity-beta-169442)
3. Observe multiple console errors relating to precompiled assemblies
Expected result: No errors are thrown when installing these 2 packages
Actual result: multiple precompiled assemblies errors are thrown
-"Multiple precompiled assemblies with the same name Antlr3.Runtime.dll included on the current platform. Only one assembly with the same name is allowed per platform. (D:/Cases/New Unity Project (4)/Library/PackageCache/com.unity.visualscripting@1.5.2/Runtime/VisualScripting.Flow/Dependencies/NCalc/Antlr3.Runtime.dll)"
-Multiple precompiled assemblies with the same name Antlr3.Runtime.dll included on the current platform. Only one assembly with the same name is allowed per platform. (Assets/Plugins/PlasticSCM/Editor/PlasticLib/Antlr3.Runtime.dll)
Reproduces on: Visual Scripting 1.5.2 (2021.1.2f1, 2021.2.0a12)
Does not reproduce on: Visual Scripting/Bolt 1.4.15 (2018.4.33f1, 2019.4.24f1, 2020.3.4f1)
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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
The issue was fixed on Plastic's side and can't be reproduced on VS side anymore.
Customer QA has also validated this status