Troubleshooting: Accessing and Configuring Unity


Unity is game engine used in courses covering interactive media design, game development as well as used as part of various student projects. This software/toolset can be found both within the Emerging Media Lab (EML) as well as the Digital Post Labs (DPL). This article will cover how to access and setup Unity for a given work session within the DPL.

Signing into Unity Hub

If you are in another DPL lab such as the VEL or PCLsearch for just the Unity editor application itself and launch it.


Then you may either create or open an existing project!


If you are in DPL1 (Ansin 809), you will need to access Unity through the Unity Hub.


For DPL1: You will be prompted to sign in, and will be brought to a web login screen on a browser window.


You are able to sign in via Google using your Emerson login or if you already have a personal account, that is also an option, if you find it more preferable.


You will be asked to go through Duo authentication. Once complete, you will be prompted to return to Unity Hub, press "Allow".


With that, you will now be able to create or access your project directories through the Hub.

Issue: No version of the Unity Editor is installed!

When launched for the first time on a given, Unity Hub may not immediately see the Unity installation. Either search for the Unity standalone application, or press "Locate existing installation".


Or press "Locate" if the message was dismissed.


And navigate through Applications > Unity, then select the Unity Editor.


Confirm that the Unity installation is identified by Unity Hub, and you should be all set to create/open your project(s).


Issue: Unity's Script Editor/IDE is launching the wrong program

If you will be scripting, then you may find that the default code editor that is launched when attempting to open a C# Script from Unity is Adobe Dreamweaver. This may not be the most ideal toolset for most; however, this can be fixed by heading to Unity Preferences.


Head over to External Tools, and under External Script Editor, change it from Open by file extension to your program of choice. We recommend Visual Studio for Mac as it includes auto-completion/IntelliSense setup by default which may be found helpful by some.14_Unity_ExternalEditor.png

Close the Preferences window, attempt to open a script or open Assets C# Project. Confirm that you are able to successfully launch your editor of choice, and that you are able to script, save, and have your code update/compile back in the Unity editor.


If you encounter any issues or have any questions, please reach out to for further assistance!

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a ticket