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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
This is a duplicate of issue #909650