| Title | Support | Engine command | Bind file | In-game test |
|---|---|---|---|---|
| Hell Let Loose: Vietnam | xbox | engine hllv | %LOCALAPPDATA%\HLLVietnam\Saved\SaveGames\EnhancedInputUserSettings.sav (GVAS; keyboard keys only) | 19/19 |
The game page in plain words: Hell Let Loose: Vietnam. Full matrix: Game support. What an export does in this kind of game: Export flow, in the game.
From docs/games/hll-vietnam.md in the repository (generated, always the current text).
#Summary
- Hell Let Loose: Vietnam (UE 5.5): has helicopters but no joystick input at all. Its exe has no DirectInput, RawInput/HID or GameInput code, only keyboard/mouse and XInput gamepads.
- JoyPro therefore flies it through the virtual Xbox 360 pad (
engine vjoy mode HLLVietnam xbox, needs ViGEmBus; see docs/virtual-joystick.md). The forwarder reads your HOTAS, feeds the virtual pad, and HidHide hides the real devices from the game. - The game's gamepad layouts are fixed. You pick one of three (A, B, C) in Options > Controls, and the gamepad keys cannot be rebound. So JoyPro writes nothing for the gamepad. It puts each physical input on the pad control the selected layout uses for that action.
- Keyboard pilot keys can still be written, and only with
--include-keyboard. - Hell Let Loose (original): nothing flyable. Its
Input.inionly has artillery and vehicle-MG pitch/yaw, so JoyPro does not support it.
#How it works
engine hllv refresh-dbbuildsDB\HLLVietnam\actions.tsvfrom the installed game. See the catalog section below. Rows are of two kinds:Pad_*actions: helicopter gamepad actions. The 5th column holds the default key per layout, e.g.A:Gamepad_LeftY|B:Gamepad_RightY|C:Gamepad_LeftY.Driver_*actions: keyboard pilot keys.
- Bind your HOTAS to the
Pad_*actions in JoyPro (relations) as for any game. engine vjoy mode HLLVietnam xboxplans the virtual pad:- The planner reads
SelectedGamepadLayout=LayoutA|B|Cfrom%LOCALAPPDATA%\HLLVietnam\Saved\Config\Windows\GameUserSettings.ini. For tests,JOYPRO_HLLV_SETTINGSpoints at another ini. - Each action is pinned to its key in that layout (
XboxControls.FromUnrealKey:Gamepad_LeftY→XB_LY,Gamepad_FaceButton_Right→XB_B, ...). - Collective: a relation that holds both
Pad_Helicopter_AscendandPad_Helicopter_Descendon one axis becomesXB_TRIGGERS. Above the axis centre the forwarder pulls RT, below it LT (in layout A, RT ascends). The relation's Invert swaps the two. - Invert on any axis relation reverses that pad axis (target suffix
~). - An action without a gamepad key (for example a keyboard action in Xbox mode) gets the next free pad control.
- What does not fit is listed.
- Switching the layout in the game and running
engine vjoy mapagain moves the pins.
- The planner reads
engine hllv exportwrites the keyboard keys (with--include-keyboard). For thePad_*binds it only says that nothing is written for them.
#Default helicopter gamepad layouts (build of 2026-10)
These come from IMC_Gamepad_ControlScheme_1 (A), _B (B), _C (C) and the helicopter seat contexts.
| Action (catalog id) | A | B | C |
|---|---|---|---|
Collective up Pad_Helicopter_Ascend |
RT | LT | RT |
Collective down Pad_Helicopter_Descend |
LT | RT | LT |
Cyclic pitch Pad_Helicopter_PitchForward |
left stick Y | right stick Y | left stick Y |
Cyclic roll Pad_Helicopter_RollRight |
left stick X | right stick X | left stick X |
Yaw Pad_Helicopter_YawRight_Gamepad |
right stick X | left stick X | - |
Yaw left / right Pad_Helicopter_YawRotateLeft/Right |
- | - | LB / RB |
Stability hold Pad_HelicopterStabilityHold |
B | B | B |
Auto-level toggle Pad_HelicopterStabilityToggle |
LS click | LS click | LS click |
Supply drop Pad_Helicopter_SupplyDrop |
D-pad right | D-pad right | D-pad right |
Recon flare Pad_Helicopter_FireFlare |
D-pad up | D-pad up | D-pad right |
Look left/right Pad_DriverLookRightRate |
right stick X | left stick X | right stick X |
Look up/down Pad_DriverLookUpRate |
right stick Y | left stick Y | right stick Y |
Free look (hold) Pad_EnableSeatFreeLook |
RB | LB | - |
Next seat Pad_SwitchSeat_0 |
Y | Y | Y |
Medic Pad_Helicopter_MedicGamepad |
A | A | A |
Medic radial Pad_Helicopter_MedicRadial |
RB | RB | RB |
In A and B, yaw and look left/right share a stick axis. The game decides by context. The planner pins only one physical axis there and warns about the second one.
#Catalog refresh (engine hllv refresh-db)
JoyPro does not ship extracted game data. In Xbox-pad mode only the pad keys of the three layouts matter, and JoyPro knows them: the catalog is JoyPro's own table (the layouts above and the keyboard pilot keys, JoyPro's wording, action ids and Unreal key names only), unless an Oodle library may be used to read the game's files (see "Oodle").
#Oodle
The game's input assets are Oodle-compressed. JoyPro reads them only with an Oodle library that is already on the PC, and it asks once before it uses another game's library:
- The game's own library (an
oo2core_*_win64.dllinside Hell Let Loose: Vietnam's folder) is used without a question. The current build ships none (Oodle is part of the game's executable: nooo2core*or*oodle*file in the install). - Another installed game's library only with the user's yes.
engine hllv oodlenames it (the other game's folder and the file, found in the same Steam library). When the GUI builds or updates the HLL Vietnam list it asks once whether JoyPro may use that library on this PC to read Hell Let Loose: Vietnam's files. JoyPro never copies or ships it. Yes / No; the answer is remembered for that file (UI settings), Settings > Games changes it ("use the Oodle library of another installed game", "Ask again"). Without a window to ask in nothing is assumed. - With the yes the GUI passes
refresh-db --oodle-dll <path>: the engine checks the name (oo2core_<n>_win64.dll), loads it from where it is (never copied), only in the refresh process, and logs it (steps andJoyProLog). Without it (no yes, no file, orJOYPRO_OODLE_DLL=nonein tests) nothing is loaded. - Fallback: JoyPro's own table (the pad keys of the three layouts and the pilot keys). In Xbox-pad mode only the pad keys matter, so the fallback is complete for that mode. Fresh build without the yes: 28 actions, the same rows the game files give (the two medic pad actions are in the table).
Tests: smoke\hllv.ps1 (a synthetic Steam library with a stand-in library: no load without --oodle-dll, a load
attempt with it, the fallback either way, the game's own library first) and the GUI test
HllvOodle_NoLoadWithoutConsent_LoadAfterYes_AndOwnLibraryNeedsNoQuestion.
The reader (with the game's own library or the allowed one):
- Open
<install>\HLLVietnam\Content\Paks\HLLVietnam-Windows.utoc/.ucas(IoStore TOC version 8) withUnrealIoStore. It reads the directory index, decompresses the Oodle blocks and reads the Zen packages with unversioned properties. - Take the Enhanced Input assets under
/Content/_WFL/Input/:- the mapping contexts
IMC_Gamepad_ControlScheme_1/_B/_CandIMC_Helicopter*; - their
FEnhancedActionKeyMappingentries: Action, Key and PlayerMappableKeySettings name; - the input actions'
ValueType(axis or button).
- the mapping contexts
- Build the rows:
<Action>_Keyboardmapping names becomeDriver_*keyboard rows;- gamepad keys of helicopter actions (plus driver look, free look, seat switch) become
Pad_*rows, with the key per layout. Keys from the helicopter contexts apply to every layout (*:).
- Oodle: the game compresses with Oodle Kraken. JoyPro does not ship Oodle; it uses the game's own
oo2core_*_win64.dll, or another game's only with the user's yes (see above), loaded only in the engine process and only for the refresh. - Without one, JoyPro writes its built-in table of the layouts above (build of 2026-10) and says so in the steps.
Measured with an Oodle library: 313 mappings and 28 actions in 0.26 s.
#Keyboard file
%LOCALAPPDATA%\HLLVietnam\Saved\SaveGames\EnhancedInputUserSettings.sav (UE GVAS). Only changed mappings are stored.
"GVAS" | i32 SaveGameVersion=3 | i32 UE4Ver=522 | i32 UE5Ver=1013
u16 5,u16 5,u16 4 | u32 CL=0 | FString "UE5"
i32 CustomVersionFormat=3 | i32 N | N x (GUID16, i32)
FString "/Script/EnhancedInput.EnhancedInputUserSettings"
UObject: tagged properties (CurrentProfileIdentifier ...), "None", i32 HasObjectGuid=0
EnhancedInput tail: i32 Version=1 ; i32 NumProfiles ; per profile:
FString ProfileKey ; FString "/Script/EnhancedInput.EnhancedPlayerMappableKeyProfile" ; FString object name ;
i32 NumMappings ; per mapping:
FString MappingName, FString CurrentKey (FKey name), FString HW.InputClassName, FString HW.DeviceIdentifier,
u8 + i32 (0,0), u8 Slot
FString "ObjectEnd"
What JoyPro writes:
- Only the
<Action>_Keyboardmappings of theDriver_*pilot actions, and only with--include-keyboard. The mapping list is rewritten on its own; every other byte stays identical (GvasKeyMappings). - Key names are translated to Unreal FKey names (
Space→SpaceBar,D1→One, ...). - One key per pilot action.
addkeeps the game's key and skips a key another pilot action has (listed as a skipped multi-bind);merge/merge-overwriteset the profile's key and drop the key of another pilot action on it (conflict, the game then uses its default there);cleandrops the other changed pilot keys. A mouse button on a pilot action always stays. Infantry and common keys never change. No ownership file any more.
The game only lists keyboard and mouse keys in its key selector, and gamepad keys are not player-mappable. That is why
JoyPro does not write gamepad binds (IGameGamepadBinds is not implemented).
#Menu check with the virtual pad (2026-10-11)
Menus only: JoyPro's xbox mode with vJoy standing in for the HOTAS (relations on
Pad_* actions, vjoy mode HLLVietnam xbox, vjoy map, forwarder-config, JoyPro.VJoy run --xbox-sink vigem).
Checked: the planner pins layout A (Medic = A, Stability hold = B, Supply drop = D-pad right, cyclic pitch = left
stick Y), XInput shows the pad and the forwarded stick, the pad's A passes "PRESS ANY BUTTON TO CONTINUE", B opens QUIT
GAME, D-pad right moves the focus from ACCEPT to DISMISS (the orange focus box), A on DISMISS closes it, and B, A quit
the game. 19/19 on 2026-10-11. vJoy and HidHide were
unchanged afterwards, the save folders restored.
Facts: a pad created before the game starts never reached the game in the first run (Steam Input or the game's startup probably takes pads present at launch); the script creates the pad once the title shows, which works. With a pad the main menu shows "B EXIT"; the main menu has "BROWSE ALL AVAILABLE DLC" (a store link: the script never presses A there).
#Not checked in flight yet
- Layout A with the virtual pad: collective on the triggers, cyclic, yaw, stability (B), supply drop.
- Whether the right-stick yaw/look overlap in layout A disturbs flying.
Sources: the installed game's files and IoStore containers (read-only), worldeka HLLV flight stick guide, hllvtools.com/helicopter-controls.