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
- Source Generation with GeneratePropertyBag fails when using reserved keywords as variable names with @ prefix
- Prismatic ArticulationBody moves in opposite direction when using targetVelocity
- Shader Graph skybox material is rendered inccorrectly in builds when "Allow Material Override" or "Cast Shadows" are enabled and the "Deferred" Rendering Path is used
- Object motion is affected by incorrectly added rotation motion when importing animations
- Base class's Context Menu method is called when calling it in the Editor from the child class and the child class overrides this method
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.