GPC 3
GPC 3 compiles .gpc3 source, runs .gbc3 bytecode, and applies optional .ipt Input Translator profiles in the Helios controller path. The plugin is included free with Helios and does not require an account.
Script Slots
GPC 3 provides one to eight configured slots. Use the add/remove controls to choose how many you need; at least one slot remains. Each slot remembers its script and optional Input Translator profile, including empty slots. When available, a slot also shows the scriptโs embedded name, version, and credited author, taken from its #pragma METAINFO line.
| Step | Action |
|---|---|
| 1 | Select an existing numbered slot, or add one. |
| 2 | Right-click it and choose Select Script for .gpc3 source or .gbc3 bytecode. Source is compiled into the selected slot. |
| 3 | Optionally choose Select Input Translator and select an .ipt profile. |
| 4 | Click Connect. |
| 5 | Check the measured frequency and use Device Monitor to compare controller input and output. |
GPC 3 runs at a fixed 1000 Hz. The frequency shown in the panel measures the VM loop, not device polling or console receipt. It is not a selectable setting.
Selecting another slot while connected activates its contents. Clicking the slot that is already selected, or activating it with the keyboard, leaves it loaded without restarting it. A slot can contain a script, a translator, both, or neither. A translator-only slot applies its mappings without a script. Selecting an empty slot stops the active contents while leaving GPC 3 connected.
Wait for a connection, compilation, or slot change to finish before making another change. Right-click a slot to clear its script or translator. Use Restart VM to reconnect and reload the selected slot, or Disconnect to stop GPC 3.
Recompile older .gpc3 sources with the current Helios release. Bytecode from an earlier GPC3 format is intentionally not loaded as though it were current.
Saved slots are validated when Helios restores them and again before a script starts or a running slot changes. An incompatible or failed script or translator leaves a persistent red status on that slot; details appear in the slot tooltip and Output Panel. If no slot is running, a rejected load stops the VM; a failed switch keeps the previously running slot.
Drag and Drop
You can drag compatible files from File Explorer or Online Resources directly onto a slot:
.gpc3: compiles and loads into that slot;.gbc3: loads as bytecode;.ipt: becomes the slot's Input Translator profile.
Imported .gbc3 bytecode must be no larger than 4 MiB. Imported .ipt profiles must be no larger than 1 MiB.
Imports keep the filename in the shared GPC 3 cache. Importing the same filename replaces that cached file for every slot that references it, and those slots refresh their status immediately.
Online Resources updates
Bytecode downloaded from Online Resources can keep an update association for that resource. Occupied slots are checked when Helios loads them, when sign-in or configuration changes, and when Helios becomes active again. When a higher published version of the same resource is available, a download button appears on the slot. Clicking it downloads that resource again, validates the file, and replaces the cached copy. Checks never install an update automatically. Same-version and older uploads remain allowed when publishing; versions do not advance on their own.
Files loaded or modified outside that Online Resources path are not matched for updates. Downloading the resource again records its association for future checks.
Compile a Script
Assign a .gpc3 source file to a slot using Select Script... or drag and drop. File Explorer โ Compile into GPC 3 Slot targets the current slot. Compilation is part of the slot workflow and does not require Developer Mode. Compiler messages appear in Output Panel.
Input Translator Profiles
Create and edit .ipt profiles in Input Translator. A profile can remap controller, keyboard, and mouse controls and provide Helios Pulse mouse-to-stick tuning. Select the finished profile in the desired GPC 3 slot rather than editing its file contents manually.
A slot's translator name, including in the slot-selection menu, starts with letters that summarize what the profile does:
| Letter | Meaning |
|---|---|
R |
Controller remapping |
K |
Keyboard mappings |
M |
Mouse mappings |
C |
Mouse-to-stick conversion (Helios Pulse) |
Letters combine in that order, for example [KMC] DayZ. [IT] marks a translator with no mappings or conversion; it is also shown, with the slot's error, for a translator that cannot be read. A controller control used only to activate ADS does not add R. Hover over a slot to see what the letters mean. Script names are unchanged.
Troubleshooting
- Compile fails: use the exact signatures in the GPC3 documentation and review Output Panel.
- Script is missing: select the intended slot, then choose it again or drag the file from File Explorer.
- Translator is missing: clear it or select an existing
.iptfile. - Slot shows a red error: open the slot tooltip or Output Panel for details, then reload a compatible script or translator.
- Slot cannot be changed: wait for the current connection, compilation, or selection operation to finish.
- Connected but no script runs: check the selected slot; empty and translator-only slots do not run a controller script.
- Update button missing: confirm the script came from Online Resources and was not replaced by a local copy, then refresh after signing in.
- Measured frequency is low: close unnecessary high-rate tools and check overall system load.
- Script runs but output does not change: verify the input and destination paths in Device Monitor.