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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment