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
- RenderTexture content from 'Depth Only' camera is not rendered correctly on UI RawImage when Multithreaded Rendering is enabled on specific MediaTek devices.
- Weight Brush Overlay text is clipped in Sprite Editor
- GameObject Transform scale values reset to their previously saved values when proportions are constrained and certain decimal values are entered in the Inspector
- Asset thumbnails in the Project window stay white when a referenced texture file is deleted and restored
- Crash on PersistentManager::ReadObjectThreaded when calling AssetDatabase.ForceReserializeAssets() multiple times in a row
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.