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

Asset Import Pipeline

-

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.

Comments (2)

  1. C2864de360f8b628cdbeb396af7e18fd?d=mm

    mgear

    Aug 14, 2020 08:57

    found registry fix in forums, copied here: https://gist.github.com/unitycoder/74ed2abca19fa227b0027bdad58ad65f

  2. C2864de360f8b628cdbeb396af7e18fd?d=mm

    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..)

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.