Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
Issue ID
561569
Regression
No
4.3b1 doesn't auto-generate solution files when opening C# scripts in OSX
Operating System:
OSX 10.8.4
Version:
Unity pro 4.3b1
Steps to duplicate:
1. Open Unity in OSX
2. Create a new project (parameters don't seem to make a difference, bug happens regardless)
3. Create an empty game object in the scene
4. Add a script to empty game object
5. Open script -> MonoDevelop launches
6. in terminal browse to project directory
Expected Result:
Solution files are generated and visible in project directory
Actual Result:
No solution files are generated.
Notes:
The project in OSX compiles, however autocomplete in MonoDevelop does not function for Unity specific classes.
This bug is also duplicated on projects which were created in 4.2. I have validated the 4.2 project autogenerates project files. I have also validated the 4.2 folder contains solution files. These solution files are not visible in the 4.3b1 version of mono-develop.
This bug is not present in windows 7 x64 unity build 4.3b1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment