Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.0b5
Issue ID
910538
Regression
Yes
Build path is set to other project's directory instead of current one when building player
To reproduce:
1. Create new Unity project.
2. Go to build settings.
3. Press Build.
4. Notice that build directory is set to other project's directory and not the current one.
Expected result: Build path is set to current project's home folder
Actual result: Build path is set other project's folder
Reproduced with: 2017.1.0b5, 2017.1.0b4
Not reproduced with: 2017.1.0b3, 5.6.1f1
Regression introduced in: 2017.1.0b4
Notes: Reproduces only on windows machines. Directory seems to depend where last project was built or edited.
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
This is a duplicate of issue #909650