Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0b17
Issue ID
657340
Regression
Yes
[Scripting] Types defined in SampleAssets folder are not easily accessible in user scripts
Types defined in Standard Assets scripts are placed in a SampleAssets folder which is not prioritized during compilation. This leads to missing type exceptions if aforementioned types are used in user scripts.
This can be fixed by moving SampleAssets folder contents to Standard Assets folder.
Steps to reproduce:
1. Create a new project and import Effects package
2. Create UnityScript file which would import UnitySampleAssets.ImageEffects; and reference one of the Image Effects. Compilation will fail reporting missing types.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [UIBuilder] Changes aren't detected on types implementing IList
- [HDRP] Text is rendered with artefacts when using STP and resolution scale is set a float value
- [Settings Search] Search results not matching search term correctly
- Crash on memcpy when opening a project that loads TSS files
- Multiple errors appear when compiling a ShaderGraph shader's code in a specific project
Add comment