Download the latest release for your operating system from the Download page.
One note that affects all OSes: make sure that neither the folder you run VUEngine Studio from, nor your project’s folder contain whitespaces. Otherwise you won’t be able to build your code.
Run the installer. It will take a little moment to install VUEngine Studio to
C:\VUEngine, then automatically launch it when done.
Note that binaries are not signed and Windows might warn you about it.
Run the installer to install
VUEngine.app to your Applications folder.
Note that binaries are are neither signed nor authored and macOS might warn you about it. If that is the case for you, hold down the Options (⌥) key while double clicking and macOS will allow you to still run the setup and not warn you again in the future.
You may need to install additional libraries to be able to build your code.
brew reinstall libmpc
# Apple Silicon (ARM)
To work on devices running Apple Silicon, you will also need a
libmpc, but instead of
arm64 version installation of
x86_64 is required. In order to accomplish that you will need
x86_64 machines (feel free to skip to step 2 if you already have it installed).
- Install brew with command:
arch -x86_64 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
arch -x86_64 /usr/local/bin/brew install libmpc
You can read more about using x86 libraries on Apple Silicon Macs here.
VUEngine Studio can be run in different ways on Linux systems. Either install the
deb using your favorite method, e.g.
sudo dpkg -i VUEngine-Studio-X-X-X-Setup.deb
Or use the AppImage without an installation. e.g. with
// make the appImage executable
chmod a+x VUEngine-Studio-X-X-X.AppImage
# Bleeding Edge
To enjoy the newest additions, which might not be included in the latest stable release, you can always check out and compile VUEngine Studio yourself from the GitHub repository, or grab pre-compiled WIP versions if available (you’ll need to be signed in to a Github account for the latter).
Note, thought, that there might be compatibility problems with VUEngine Core, Templates and/or other sample code. We only ensure compatibility at time of releases.