Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.5.2
Issue ID
UVSB-1436
Regression
Yes
Collab and Visual Scripting packages throw multiple precompiled assemblies errors when installed
Reproduction steps:
1. Create a new project
2. Install Visual Scripting and activate Collab in the Project settings
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
- Spot Light with 'Box' Shape stops working when it collides with Mesh
- Accepting Asset Store EULA endless loop in Package Manager window
- “InvalidOperationException: Sequence contains no matching element“ error when reenabling a custom Debug Draw Mode
- Prefab that contains a layout group is marked as changed by the Editor when opened
- Emission animation does not appear when the "Emission Map" parameter is set to black in a Lit material
Resolution Note:
The issue was fixed in 1.6.0 on VS side, most probably a fix will also land on Collab side