Search Issue Tracker
Third Party Issue
Third Party Issue in 2022.3.X
Votes
0
Found in
2022.3.46f1
Issue ID
UUM-78585
Regression
No
"System.DllNotFoundException" error for "Unity.VisualScripting.sqlite3" when loading Visual Scripting
Reproduction steps:
1. Open the attached “repro_IN-75124“ project
2. Observe the Console window
Expected result: No errors appear
Actual result: “System.DllNotFoundException: Unity.VisualScripting.sqlite3 assembly:<unknown assembly> type:<unknown type> member:(null)“ error appears
Reproducible with: 1.9.4 (2021.3.38f1, 2022.3.29f1, 6000.0.2f1)
Reproducible on: Windows 10 (22H2)
Not reproducible on: macOS Sonoma 14.4.1
Note: Without relocating the “sqlite3.dll“, the Visual Scripting window in the Project Settings and the Script Graph tab appears empty when opened
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The user's project path contains a semicolon which is a reserved character for paths in some windows APIs. In this case LoadLibraryW is unable to find the dll in question due to the semicolon. The recommended workaround for now is to not use semicolons in project paths.
Resolution Note (2022.3.X):
The user's project path contains a semicolon which is a reserved character for paths in some windows APIs. In this case LoadLibraryW is unable to find the dll in question due to the semicolon. The recommended workaround for now is to not use semicolons in project paths.
Resolution Note:
The user's project path contains a semicolon which is a reserved character for paths in some windows APIs. In this case LoadLibraryW is unable to find the dll in question due to the semicolon. The recommended workaround for now is to not use semicolons in project paths.