Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.7.5
Issue ID
UVSB-2000
Regression
Yes
[Linux] Builds failing due to Visual Scripting package errors when ran from command line
How to reproduce:
1. Download attached project
2. Open Linux machine terminal and go to existing Unity location (/home/<user>/Unity/Hub/Editor/2021.2.2f1/Editor)
3. Enter command
ProjectPath=<path to downloaded project>
4. Enter command
./Unity -projectPath $ProjectPath -buildLinux64Player $ProjectPath/LinuxBuild -batchmode -logfile $ProjectPath/Editor.log -cleanedLogFile $ProjectPath/Cleaned.log -quit
or you can run tests, that will provide same results
./Unity -runTests -projectPath $ProjectPath -testResults $ProjectPath/results.xml -testPlatform StandaloneLinux64 -batchmode -logfile $ProjectPath/Editor.log -cleanedLogFile $ProjectPath/Cleaned.log
5. Observe editor logs
Reproduced with: 2021.2.2f1 (1.7.5), 2022.1.0a15
Does not reproduce with: 2021.1
Note: Does not reproduce when ran from Editor or Test Runner UI
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
PR https://github.cds.internal.unity3d.com/unity/com.unity.visualscripting/pull/469