Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0b5
Issue ID
993277
Regression
No
Double-clicking a Unity package file in the system opens a new Unity instance, instead of importing the package
To reproduce:
1. Download user's attached Unity package
2. Open any Unity 2018.1 beta version
3. Create a new or open an existing project
4. Right after it has finished loading double-click the package file
Expected result: Unity opens an import window containing the files in the package
Actual result: A new instance of most recently installed Unity is opened
Notes:
- Tested on 8, reproduced with 4 machines;
- The best chance to reproduce this is to install any 2017.2 version, open any 2018.1 beta and then double-click the package file;
- Only reproduces on Windows;
- Not interacting with the Editor window helps to reproduce.
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
mgear
Aug 14, 2020 08:57
found registry fix in forums, copied here: https://gist.github.com/unitycoder/74ed2abca19fa227b0027bdad58ad65f
mgear
Aug 14, 2020 08:47
Any news? This is pretty annoying (seems like it started after i installed 32bit unity version, and removing it didnt restore old behaviour..)