Search Issue Tracker
Won't Fix
Won't Fix in 1.0.X
Votes
0
Found in [Package]
1.0.0
Issue ID
DANB-1121
Regression
No
The default version of the Generators package (dependency of 2D Enhancer) is incompatible with the AI Assistant default dependency versions
How to reproduce:
1. Create and open a new project
2. Open Window → Package Manager
3. Install the 2D Enhancers package
4. Press on the “+” symbol at the top left of Package Manager window then press “install package by name“
5. Enter “com.unity.ai.assistant“ and press Install (Can be installed through the AI button in the Editor as well)
6. Wait for the package to install and observe the Console
Expected result: No errors are thrown in the Console
Actual result: Package errors are thrown in the Console
Reproducible in: 1.0.0 (6000.2.3f1, 6000.3.0b1)
Could not test in: 6000.0.57f1 (AI workflow packages have not been introduced yet)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Workaround: Upgrade the Generators package to at least 1.0.0-pre.13 version
Notes:
- AI Assistant (1.0.0-pre.12) uses the default version of 1.0.0-pre.18 of the AI Toolkit package as a dependency
- The 2D Enhancers package uses the default version of 1.0.0-pre.12 of the Generators package as a dependency. If Generators is upgraded to at least 1.0.0-pre.13, the packages become compatible.
- The 2D Enhancers package is compatible with later versions of the Generators package (does not create package errors in the Console), so raising the required version of the Generators package would likely solve this problem
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.0.X):
There are no fixes planned for this Bug