Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.2.21f1
2020.1
Issue ID
1221293
Regression
No
csc.rsp references do not work when used with custom assemblies
Steps to reproduce:
1. Open and run User-supplied project
Expected: no errors are thrown
Actual: errors are thrown
Reproduced in: 2018.4.17f1, 2019.2.21f1, 2019.3.3f1, 2020.1.0a24
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2020.2.X):
This behaviour is unsupported by design. If you want to reference a custom assembly it must be located in the Assets or Packages folders, which we scan assemblies for.
You can also un-tick the "Override References" in the asmdef and reference your assembly from there, but it must be loaded.