Search Issue Tracker
Fixed
Votes
5
Found in
4.2.0f4
Issue ID
560137
Regression
No
New scripts are not detected first time when running editor with -batchmode flag
To reproduce:
1) Create new project
2) Create an editor script which would have a static method (for example:
public static void Test() { Debug.Log ("EditorScript"); }
3) Close Unity
4) Make a new script in the Assets folder and also give it a public static method
5) Change the editor script so it would call the newly created method
6) Run Unity in batch mode with following arguments:
Unity -quit -batchmode -projectPath "YourProjectPath" -executeMethod "EditorScript.Test"
7) Notice in Editor.log that it could not find the new method you made
8) Rerun the command
9) Now Editor.log shows it ran everything successfully
Comments (3)
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
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
- Unity Version Control server textfield’s text overlaps with the dropdown triangle button in the Explore repositories window when an organization with a long name is selected
- [Usability] Selecting Animations Clips in a Blend Tree's Motion List does not Visualize their Weight if all Weights have been enabled previously
sparedes
Mar 21, 2016 23:06
This is also happening to us running in batch mode. Please fix!!!
BenHymers
Jan 07, 2016 10:41
This is not fixed.
It's a 100% repro for me. In my case it's on a continuous integration server - any time someone on the team adds or removes source files, the Unity build will fail on the build server. The workaround is to open Unity twice, once to import assets (ignoring the logs and return code completely), and again to run the build. This is far from ideal as it's slow, and loses much of the useful log information from the first import.
I've seen it in various versions from 5.0.1 onwards, up to and including 5.3.1.
There's a related bug in FogBugz here, also reported in August 2013, marked as resolved in May 2015:
https://fogbugz.unity3d.com/default.asp?560137_5p90morai1utgu6o
davisben85
Jul 30, 2015 18:15
This happens with ANY assets that are moved into the Asset directory without going through Unity. We build custom plugins and drop them in, outside of Unity, through build scripts. We then have to open the project in Unity to have it update the assetDatabase and then quit. From there, we can kick off another Unity batchmode process and build the project.