Search Issue Tracker
Fixed
Fixed in 1.0.0
Votes
0
Found in [Package]
1.0.0
Issue ID
BASST-561
Regression
No
Shader code is saved as .cs file and includes Unity namespaces when generated by the AI Assistant
How to reproduce:
1. Create a new project
2. Install and open the AI Assistant
3. Ask the Assistant to generate glsl code for a new shader
4. Save the file with the Save button
5. Observe the file type
6. Open the saved file
7. Observe the result
Expected result: The shader code is saved as a .glsl file and does not contain the Unity namespaces
Actual result: The shader code is saved as a .cs file and contains the Unity namespaces
Reproducible with: 1.0.0-pre.4 (6000.2.0a9), 1.0.0-pre.8 (6000.2.0b9, 6000.3.0a1)
Could not test with: 2022.3.64f1, 6000.0.53f1, 6000.1.11f1 (AI Assistant package not supported), 1.0.0-pre.3 (6000.2.0a9) (Could not open the Assistant - “ExecuteMenuItem failed because there is no menu named 'Muse/Chat'“)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak occurs when focused on Player while using Direct3D12
- 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
Add comment