Valid outputs are: Keyboard, Mouse, vJoy Virtual Joystick (Inc virtual XBox), Titan One hardware Valid inputs are: Keyboard, Mouse, Joystick. Plugins may also contain special GuiControls that allow the end user to bind inputs and outputs. It can be used to allow the end user to tweak the behavior of the plugin that it is part of. Plugins can call UCR methods to add a GuiControl to their Gui whose value will be remembered between runs of UCR. Pretty much anything that you could normally put in an AHK class should work inside a plugin. There are varios provided methods and mechanisms to get notification of events (eg the profile containing the plugin went active or inactive) The GuiControls in the Gui can easily be made persistent across runs and you can add special GuiControls that allow the end-user to select the inputs (eg hotkeys) and outputs to configure your script. The script contains an AHK class that derives from a base class which is part of the UCR source code.Įach instance of each plugin gets it's own GUI inside the UCR app when added by a user. The will be selected as fallback if no is found.Įxample: UCR.exe CLI.ahk "MAME" "megaman" PluginsĪt the core of the design of UCR is the idea of an AHK script as a "Plugin".įrom an end-user's perspective, a plugin is a widget which can perform a small task - eg remap one key to another.įrom a plugin author's point of view, a plugin is simply a text file containing AHK script. Passing both and will find and select a profile matching the name with a parent profile matching the name. Passing a string, quoted or unquoted, as will select the first profile matching (all matches are case insensitive). Passing a valid profile GUID as the will find and activate the profile. There are three different methods for changing profiles using the syntax. The syntax for profile switching is UCR.exe CLI.ahk. Profiles can be changed through command line parameters when launching UCR through the CLI tool and subsequently to change the profile of the running instance. In the future, it is also planned to allow profiles to be linked to a specific application - when that application gets the focus, the profile becomes active. This can be used to create "Shift states" to switch the functionality of inputs. Profiles can also have child profiles, and child profiles can "inherit" the plugins of a parent profile. A number of plugins can be grouped together into a Profile. The primary target audience is gamers, UCR is intended to be able to replicate the functionality that comes with programmable keyboards / mice / joysticks etc. The aim of UCR is to allow end-users to easily leverage the power of AHK without having to learn to code.Īt it's basest level, think of it as a way for an end-user to run a number of scripts written by various people, and manage when each script runs, what keys trigger it's functions, tweak each script's parameters, etc - solely by using a GUI application. If this step fails, open an admin command prompt and navigate to UCR's resources folder, there are. On first run of UCR, check the vJoy log to make sure vJoy loaded OKįrom the UCR main menu: IOClasses -> vJoy -> Show vJoy logįrom the UCR main menu: IOClasses -> vJoy -> Install SCPVBus.Install the latest version of vJoy from.If Xbox controllers stop working while UCR is not active, then you are not using XInput mode! Select from the menu, don't use Bind Mode!įor Virtual XBox controllers to work, you must:
0 Comments
Leave a Reply. |