-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display project name in list of debuggable Unity processes #1009
Comments
Unity team mentioned that they have a related item on their backlog for 2019.3. "Add more information to the multi-cast messages for Unity." |
@citizenmatt I guess, you have some new info from Rareș about this, right? |
Yep. Will implement today, hopefully. Although this will be Unity 2019.2 only |
Currently, the list of debuggable process will show the project name for players built with Unity 2019.2. It doesn't yet show project name for editor instances. This will come as a separate PR, after speaking with Unity next week. |
Project name is found in most scenarios, except when the Unity editor is launched on Windows as standalone, rather than via Unity Hub. Fixes #1009, fixes RIDER-31184
When attaching to a Unity process, the dialog will list all players found on the network, as well as any local Unity editor instances. If there is more than one instance of the editor running, it's very difficult to tell them apart - it would be very useful to list the project name next to the process name.
Unfortunately, the project name isn't easily available, and there isn't an API to fetch it. Our plugin could write the project name to a file with exe name and pid to a shared location (somewhere under the user's profile) and delete it on exit. The dialog could read this and show the project name.
And/or, we could use the currently open project's
Library/ProjectInstance.json
to at least mark the current project's Unity editor instance.The text was updated successfully, but these errors were encountered: