Overview

EmVoy came about to solve a few issues when using zipped gamefiles where you need to use different emulators for the same system. It's designed to sit between your Front End and your emulators. It needed to:

This was hard to achieve with the front end alone, the difficulties being illustrated below:

 

This is the way my setup originally worked. A few problems:

Emvoy solves this, thus:

 

Explanation: EmVoy accepts a number of command line parameters (gamepath, gamefile, preferred gamename, emulator and BootProfile). This means your FrontEnd can send the specific gamefile (zipped or unzipped) and preferred emulator (although this can be managed in EmVoy). It then unzips the gamefile to a Quicklaunch folder and gives you the option to keep or discard on game exit (auto or user prompt).

When a game is passed, a game profile is created. Within this you can also specify:

EmVoy can run silently between your FrontEnd and your emulators; can update the user on any operations (e.g. unzipping gamefiles or de-ecm'ing files) or there is a full GUI allowing you to set up games in batches.

It uses DTools and PakkIso. It is being developed to work with different systems.