Skip to content

How To Use Controller Priest

Jump to bottom
Terminality edited this page Aug 23, 2020 · 3 revisions

How To Use Controller Priest

Introduction

So here you are, ready to pass the controller between friends as you play a good ol' video game. Fantastic, however before we begin there's some things you should note.

Before Starting

  1. Make sure all controllers are off.

We need to make sure that when we start our emulated controller, it binds itself to Port 1. Most games look for primary input on Port 1, so having one of the player's controllers instead of the emulated controller means we won't be able to successfully pass control.

  1. Make sure the program can actually start.

If you have problems, it might be because you don't have ViGEm installed. If you have Parsec installed I believe it should be fine, but just to be on the safe side it can be a good idea to install the driver anyway.

I'm going to assume you already have a program like Parsec or Steam Remote Play to connect to your friend and that the tool creates a controller for them on your computer.

Starting Controller Priest

Once you have booted up Controller Priest you will be created by a horrifically amateur looking interface. Picture Of Tool Layout

Layout

Here we will quickly outline the different part of the tools.

Tool Labelled

  1. The menu bar. Currently it has no particular function, you can exit or see the about section but that's about it. It's mainly there, should I wish to expand the tool with options and such.

  2. This is our status checker. It monitors to see what controllers (if any) are currently connected ot the computer. This updates automatically and will also indicate if a controller is OUTPUT, MASTER or CONNECTED.

OUTPUT - This is the emulated controller that accepts input from the master controller and sends the input commands it receives through the port it is currently connected to. Generally, you want to see this on Port 1 unless you have a particular reason not to have it on Port 1. There can only be one OUTPUT controller.

MASTER - This indicates the controller master is currently attached to. The master controller is one of the player controllers connected to the PC. The OUTPUT controller can not be made the MASTER, any attempts to do so will either fail to assign it or it will skip over the OUTPUT controller until reaching the next valid controller. There can only be one MASTER controller.

CONNECTED - This is a generic message indicating that a controller is connected to the Port that is neither a MASTER controller or OUTPUT controller.

  1. Here you can start or stop the emulated/OUTPUT controller. When started it will bind itself to the first available Port. Should OUTPUT find itself on a port that is not Port 1 a dialog box will appear warning the user that this is ill advised. Stopping and starting the emulated controller can help get it to a different port, but you may find it cycles through the other ports before ending back up at one. XInput does not (as far as I have investigated) allow us to directly assign controllers to specific ports and is simply a first come, first serve basis. This can make things rather tedious, but that's the way it goes.

  2. Shows who the current MASTER is or a new MASTER can be selected through the dropdown if for some reason you can't pass control using the controller shortcut.

  3. A message, this doesn't currently change throughout the controller execution. Hopefully I will end up updating this to actually function in some way, but for the time being it reminds you of the button combination to pass control.

Getting Going

  1. Click "START" under the label Emulated Controller. Hopefully you should see OUTPUT appear on Port 1. If you don't, click stop and start until it cycles around to Port 1.

  2. If the emulated controller has successfully bound to Port 1 then you can turn on your controllers and begin using Parsec or Steam Remote Play.

  3. Your controllers should appear in the other ports. Whoever is going to be in control of the game first will need to be set as the MASTER controller. There is two ways you can do this. When the program starts and no master has been set yet, a controller can take control by pressing LS + RS + LB + RB (XBOX) or L3 + R3 + L1 + R1 (PlayStation) ALL TOGETHER AT THE SAME TIME. You can also use the Current Master dropdown box and select the controller you wish to have control.

  4. When you have grown tired of playing, you can then pass the controller. The MASTER controller can press the button combination LS + RS + LB + RB (XBOX) or L3 + R3 + L1 + R1 (PlayStation) ALL TOGETHER AT THE SAME TIME. The tool will then look for the next valid controller (a controller that's not OUTPUT and is currently connected) and pass control to them. If no valid controller is found, control will remain with the controller that triggered the change.

Final Words

Hopefully you find this tool to be of some use. If you wish to make some suggestions, have questions or you are having problems then feel free to use the GitHub Issues page to post these messages.

Thanks and happy gaming!

Clone this wiki locally