JoyPro2 Discord GitHub
GUI pages

Start

Show:

The Start page is where JoyPro opens. It shows what is set up, what to do next, and your games: Import takes the binds you made in a game into JoyPro; Export writes them back. The import step by step: Import a game.

The Start pageThe Start page
The Start page
For beginners

#From top to bottom

  • Notices: missing requirements, command lists to build or update, a crash report to send, an update.
  • Set up your devices: the auto setup card. JoyPro looks (read-only) which of your games have nothing assigned yet and names them: "Set up your devices for War Thunder and Star Citizen". Set it all up for me (the blue button) does it all by itself; Set up step by step... opens the setup wizard with these games ticked. Games where you made binds yourself are listed below it: Import, then fill the gaps takes your binds in first, then the setup only uses the free controls. Games already in your profile: Fill the gaps.... Where is what? shows your devices with what each control does.
  • Profile at a glance: relations (and how many are axes), how many are bound, modifiers, devices connected, games installed.
  • Next steps: what JoyPro suggests now ("3 relations have no button yet: Bind them", "VPforce Rhino FFB Base is not used yet: Auto Assign", "Write your binds into your games: Export").
  • Your games: one card per game with Import, Export, Update (its command list), Undo export, Watch for changes and a hide button. Set up my devices automatically... runs the setup wizard.
  • Your devices: the connected devices with their pictures; a click opens the Layout page. An orange Which grip? or Which model? on a device means JoyPro cannot tell which one it is: a click on it opens the Layout page with the choice open, and your answer stays.
  • Recent activity per game and the game watcher switch; the HUD card.
Advanced

#The import wizard

  1. Pick a game (Import on its card).
  2. Choose how: Add to my profile (recommended) or Start over from this game, the keyboard, devices that are not connected, the DCS aircraft. Look first shows what the game has in the Output panel without changing anything.
  3. Import now: the result stays on top of the cards ("Done: your profile now has 214 relations") with See my relations.

Below the cards, the expert import offers every option per game (DCS, IL-2, Star Citizen, and every other game from Load Games) with Scan / Import / Export.

Technical internals

#Behind the page

MainWindowViewModel.GameHub.cs (cards, wizard), MainWindowViewModel.Design.cs (dashboard), MainWindowViewModel.DbUpdates.cs (command lists), MainWindowViewModel.DeviceCenter.cs (devices), MainWindowViewModel.GameSync.cs (watcher). Engine: engine games installs, engine db check-updates, engine hud devices, engine sync status, engine dcs import / engine dcs scan and the other games' import and scan.

#Reference

The feature documentation behind this page, generated from the repository:

#Every control on this page

110 controls, read from the program’s source: 110 written, 0 with the facts from the source (tooltip, code comment, engine call), 0 still to be expanded.

#Stops the command before it writes anything (JoyPro offers this only while it reads)

Buttonwritten

Cancel in the busy area: asks the running engine command to stop at its next safe point; the label turns to Cancelling.... JoyPro offers it only while the command still reads, so nothing has been written when it stops.

From the code Stops a download (an installer that already runs is not killed; its own window has Cancel).

Source BusyProgressPanel.axaml:20 · CancelCommand in ComponentItem.cs

#Install Missing

Buttonwritten

Downloads and installs the missing components the notice lists (for example a .NET runtime the engine needs), one after the other, then checks again whether the engine starts. Errors are shown in the notice.

Source MainWindow.axaml:457 · InstallMissingRequirementsCommand in MainWindowViewModel.AppServices.cs

#Check Again

Buttonwritten

Check Again in the "Components missing" notice: checks whether the components the engine needs are installed, then whether the engine really starts, as at program start. Use it after you installed a missing component yourself.

From the code "Check Again": the components and then whether the engine really starts, as at program start.

Source MainWindow.axaml:458 · CheckRequirementsCommand in MainWindowViewModel.AppServices.cs

#Report It...

Buttonwritten

Opens Settings > Report a problem with a text started for the last crash ("JoyPro2 ran into an error. What I was doing: ..."). Describe what you did and press Create Report; the crash details are added by themselves.

Source MainWindow.axaml:468 · ReportLastCrashCommand in MainWindowViewModel.AppServices.cs

#Install Update

Buttonwritten

Downloads the new version the notice names, checks the download, then closes JoyPro, installs it and starts it again. If the download or the check fails, your installed version stays as it is and the dialog says why.

From the code The Settings button: the same dialog, straight to installing.

Source MainWindow.axaml:479 · InstallUpdateCommand in MainWindowViewModel.Updates.cs

#Reads the game's commands from its own files into JoyPro's list (DCS is read without starting the game)

Buttonwritten

Refresh DB (Build List when the game has no command list yet): reads the game's commands from its own files into JoyPro's command list, then checks the notice again. DCS is read through its own Lua files without starting the game; its first list also builds the clean profiles. Your profile and the game's files are not changed. Engine: engine dcs refresh id, engine db refresh-il2, engine db refresh-starcitizen or engine <game> refresh-db.

From the code One game: refreshes its DB with the game's own refresh command (which records the build), then checks again.

Engine engine db check-updates · engine dcs refresh id · engine db refresh-il2 · engine db refresh-starcitizen · engine hllv oodle · engine dcs refresh clean

Source MainWindow.axaml:496 · RefreshDbUpdateCommand in MainWindowViewModel.DbUpdates.cs

#Keep DB

Buttonwritten

Tooltip This game's current build counts as known; its DB stays as it is

Keep DB: this game's current build counts as known and its command list stays as it is; the game leaves the notice. Use it when the game update added nothing you need. Engine: engine db check-updates --accept <game>.

From the code One game: its current build counts as known, its DB stays as it is.

Engine engine db check-updates · engine dcs refresh id · engine db refresh-il2 · engine db refresh-starcitizen

Source MainWindow.axaml:499 · AcceptDbUpdateCommand in MainWindowViewModel.DbUpdates.cs

#Build All Missing Lists

Buttonwritten

Tooltip Builds the command list of every installed game that has none yet, from the game's own files

Builds every missing command list, one game after the other, with progress and Cancel.

From the code Builds the command list of every installed game that has none yet, from the game's own files, one after the other (the first-start setup runs it after Done; the Start page notice has a button for it).

Engine engine db check-updates · engine dcs refresh id · engine db refresh-il2 · engine db refresh-starcitizen · engine hllv oodle · engine dcs refresh clean

Source MainWindow.axaml:507 · BuildMissingCommandListsCommand in MainWindowViewModel.DbUpdates.cs

#Keep All DBs, Hide Notice

Buttonwritten

Tooltip Marks the current game builds as known without refreshing the DBs

Marks the current build of every listed game as known without refreshing any command list, and hides the notice. Engine: engine db check-updates --accept-all.

From the code The user saw the hint and keeps the DB as it is (or refreshed it outside JoyPro).

Engine engine db check-updates · engine dcs refresh id · engine db refresh-il2 · engine db refresh-starcitizen

Source MainWindow.axaml:510 · AcceptDbUpdatesCommand in MainWindowViewModel.DbUpdates.cs

#Set it all up for me

Buttonwritten

Tooltip JoyPro does every step by itself and shows you the result. You only press Use these buttons and Write to my game.

Set it all up for me: JoyPro does every step of the setup by itself with its defaults (your devices and their usual jobs, every aircraft equal, no modifier) for the games named in the card, and stops at the review. A box at the top says in plain words what was set up and which device JoyPro does not know (set up like a usual stick or throttle). Then Use these buttons and Write to my game (the export of these games). The same as the first start's Done, and set everything up for me. Engine: engine setup games, engine setup plan, engine setup apply.

From the code From the first start ("Done, and give me binds quickly") and the Start page's card: the games with nothing assigned (else the ones already in the profile), the setup run by itself up to its review, then "Use these binds" and "Write to my game" (QuickExportAsync).

Source MainWindow.axaml:536 · QuickSetupCommand in MainWindowViewModel.AutoSetupStart.cs

#Set up step by step...

Buttonwritten

Tooltip Opens the setup with these games ticked: your devices and their roles, what matters most to you, the plan, and a review before anything changes

The auto setup card's main button: opens the setup wizard with the games ticked where nothing is assigned yet (named in the card's title, "Set up your devices for ..."). Your devices get their roles, the important functions of these games go where pilots expect them, and you review the plan before anything changes. Engine: engine setup games, engine setup plan.

From the code "Set up my devices...": the wizard with the games that have nothing assigned ticked.

Source MainWindow.axaml:538 · OpenAutoSetupCommand in MainWindowViewModel.AutoSetupStart.cs

#Where is what?

Buttonwritten2 ×

Tooltip Shows your stick and throttle with the function on each control, per game and aircraft

Where is what?: opens the layout window with every device and the function on each control for one game and aircraft. While a setup plan waits to be applied it shows that plan; otherwise your profile. See the Layout page.

Source MainWindow.axaml:540 · OpenLayoutPreviewCommand in MainWindowViewModel.LayoutWindow.cs

#Import, then fill the gaps

Buttonwritten

Tooltip Takes your binds from the game into JoyPro first; afterwards the setup only uses the controls that are still free

For a game where you have binds of your own: starts the import of that game first (the usual import steps). Its result then offers Now fill the gaps...: the setup only uses the controls that are still free, your binds stay.

From the code "Import, then fill the gaps": the import wizard for the game first; its result offers the setup.

Source MainWindow.axaml:556 · ImportThenFillGapsCommand in MainWindowViewModel.AutoSetupStart.cs

#Fill the gaps...

Buttonwritten

Tooltip The setup for these games: your binds stay, only free controls get functions

For the games already in your profile: opens the setup wizard with them ticked. Your binds stay where they are; only free controls get functions.

From the code "Fill the gaps": the wizard for one game (or every game already in the profile); the plan keeps the profile's binds.

Source MainWindow.axaml:569 · FillAutoSetupGapsCommand in MainWindowViewModel.AutoSetupStart.cs

#

Buttonwritten

The button of a next step ("Bind them", "Auto Assign", "Export"): it opens the page or runs the action the step names.

Source MainWindow.axaml:647 · Command

#Supported games

Buttonwritten

Tooltip Every game JoyPro knows, what it can do for each (import, export, curves, settings, virtual joystick ...) and how it was tested, in your browser

Opens the list of every game JoyPro knows in your browser: what it can do for each (import, export, curves, settings, virtual joystick ...) and how it was tested. The engine writes the page into your temp folder; nothing else changes. Engine: engine games support --html.

Engine engine games support

Source MainWindow.axaml:664 · OpenSupportedGamesCommand in MainWindowViewModel.SupportedGames.cs

#Set up my devices automatically...

Buttonwritten

Tooltip Binds the most important functions of the games you watch to your devices: roles, priorities, modifiers, where functions go; you review before anything changes

Opens the setup wizard: your games, your devices and their roles, your priorities, then a plan of relations and binds you review before it is applied. Shown here when the auto setup card above is not (no game it could set up).

From the code A wizard the user closed before Apply comes back as it was (devices, priorities, plan); after Apply a new one starts.

Source MainWindow.axaml:668 · OpenSetupWizardCommand in MainWindowViewModel.SetupWizard.cs

#Watch all

Check boxwritten

Tooltip Watch every installed game for changes (tick) or none of them (untick). Each card has its own box.

Ticks or unticks Watch for changes on every installed game card at once (mixed when only some are ticked). Saved at once and kept across restarts; it only has an effect while the Game watcher switch is on.

Source MainWindow.axaml:672 · setting WatchAllGames

#Now fill the gaps...

Buttonwritten

Tooltip The setup for this game: your imported binds stay, only free controls get functions

After an import started with Import, then fill the gaps: opens the setup wizard for that game. The binds you just imported stay; only free controls get functions.

Source MainWindow.axaml:702 · FillGapsAfterImportCommand in MainWindowViewModel.AutoSetupStart.cs

#Try again

Buttonwritten2 ×

Back to the import options after an import failed (or from step 2 back to the game cards), to change a choice and try again. Nothing was changed by the failed import.

Source MainWindow.axaml:705 · ImportWizardBackCommand in MainWindowViewModel.GameHub.cs

#Close

Buttonwritten

Tooltip Hide this result; your games stay below

Close on the import result: hides the result and goes back to the game cards (step 1). The import itself stays in your profile.

Source MainWindow.axaml:706 · RestartImportWizardCommand in MainWindowViewModel.GameHub.cs

#I have read what BYOJoystick is and its license situation, and I want to install it from the Steam Workshop

Check boxwritten

Tick to confirm that you read what BYOJoystick is and want to install it from the Steam Workshop; Install BYOJoystick works only then. JoyPro backs up your BYOJ files and opens Steam; Steam downloads the mod. Without the mod VTOL VR binds only rudder and toe brakes; with it JoyPro writes the binds of stick, throttle and switches per aircraft and seat.

Source MainWindow.axaml:742 · ByojConsent in MainWindowViewModel.Byoj.cs · setting ByojConsent

#Install BYOJoystick

Buttonwritten

Works only after you ticked the consent box. JoyPro backs up your BYOJ files (Export > Game config backups) and opens Steam: install the VTOL VR Mod Loader if asked, then press Subscribe on the BYO Joystick page; Steam downloads the mod. The consent counts once: a second install asks again. Engine: engine vtolvr mod prepare.

From the code After the consent: back up the BYOJ files, then let Steam install the Mod Loader and the mod (the user subscribes on the Workshop page). The consent is used up: a second install asks again.

Engine engine vtolvr mod prepare

Source MainWindow.axaml:745 · InstallByojCommand in MainWindowViewModel.Byoj.cs

#Check again

Buttonwritten

Tooltip Look for the installed mod and build JoyPro's VTOL VR command list from it

Looks again whether BYOJoystick is installed (engine vtolvr mod status); once it is, builds JoyPro's VTOL VR command list from the mod. Press it after Steam finished the download. Engine: engine vtolvr refresh-db.

From the code Reads the status again; once the mod is there, builds the target list from it.

Engine engine vtolvr refresh-db · engine vtolvr mod status

Source MainWindow.axaml:746 · CheckByojCommand in MainWindowViewModel.Byoj.cs

#Hide this game: it leaves the cards, the export, the watcher and the setup suggestions (your binds for it stay). 'Hidden games' below the cards shows it again.

Buttonwritten

Hides this game everywhere in JoyPro (it counts as not installed). Your relations for it stay; Settings > Games > Show again brings it back.

From the code The hide button on a Start page card.

Engine engine games install

Source MainWindow.axaml:771 · HideGameCardCommand in MainWindowViewModel.GameInstalls.cs

#Watch for changes

Check boxwritten

Watch this game's control files: after the game closes, JoyPro asks whether to take changes you made in the game into your profile. Off: changes in this game are ignored.

From the code "Watch for changes" (docs/sync-watcher.md#which-games-are-watched): JoyPro's watcher offers to take over binds the user changes in the game. Ticked for installed games unless the user unticked it; a game not found has nothing to watch (the box is off and greyed, and ticks itself once the game is installed unless the user unticked it).

Source MainWindow.axaml:789 · Watch in GameCardItem.cs · setting Watch

#Update

Buttonwritten

Tooltip Read the game's new commands (after a game update). The game is not started.

Builds or updates this game's command list from your installation (DCS: the command list and the clean profiles, run with DCS's own Lua, no game window). Needed after a game update adds aircraft or commands.

From the code Reads the game's new commands into JoyPro's command list (engine dcs refresh id / db refresh-il2 / db refresh-starcitizen / <game> refresh-db), then checks the games for updates again.

Engine engine db check-updates · engine dcs refresh id · engine db refresh-il2 · engine db refresh-starcitizen · engine hllv oodle · engine dcs refresh clean

Source MainWindow.axaml:809 · UpdateGameCommandListCommand in MainWindowViewModel.GameHub.cs

#Install BYOJoystick

Buttonwritten

Tooltip Full HOTAS support in VTOL VR needs the BYOJoystick mod (Steam Workshop). JoyPro shows what it is and its license first; Steam downloads it.

On the VTOL VR card: opens the BYOJoystick panel with what the mod is, its official source, its size and license, and what is on this PC already (engine vtolvr mod status). Nothing is installed or changed yet.

From the code Opens the panel and reads what is on this PC (engine vtolvr mod status; nothing is changed).

Engine engine vtolvr mod status

Source MainWindow.axaml:815 · OpenByojCommand in MainWindowViewModel.Byoj.cs

#Show them in Settings > Games

Buttonwritten2 ×

Tooltip Settings > Games lists your hidden games; Show again brings one back on the cards, in the export and the watcher

Opens Settings with its section open: from the hidden games note the Games section, which lists your hidden games (Show again there brings a game back on the cards, in the export and in the watcher); Manage next to Your devices opens the Devices section, where binds move to another device and an old device is removed.

From the code The Settings page with the section open (a tab at the top, About from the version in the corner, ...).

Source MainWindow.axaml:832 · OpenSettingsSectionCommand in MainWindowViewModel.SettingsPage.cs

#Add to my profile (recommended)

Optionwritten

Adds the game's binds to the open profile (the safe default). Relations with the same name or input are merged.

From the code true: add to the open profile (engine --merge); false: the profile's relations are replaced by the game's.

Source MainWindow.axaml:853 · ImportWizardAddToProfile in MainWindowViewModel.GameHub.cs · setting ImportWizardAddToProfile

#Start over from this game

Optionwritten

Replaces the relations of the open profile with what the game has. JoyPro asks first and keeps a copy of the profile.

Source MainWindow.axaml:859 · setting ImportWizardStartOver

#Turn on watching from import

Buttonwritten

"Turn on watching for ": switches on the game watcher for this game (and the watcher itself if it was off). From then on, binds you change in the game are offered to your profile after the game closes.

Source MainWindow.axaml:873 · TurnOnWatchingFromImportCommand in MainWindowViewModel.ExportDefaults.cs

#Report a watcher problem

Buttonwritten

Opens Settings > Report a problem with the description started as "Watcher: ...". Describe what the watcher did and create the report there.

From the code "Report watcher problems": Settings > Report a problem with the text started.

Source MainWindow.axaml:874 · ReportWatcherProblemCommand in MainWindowViewModel.ExportDefaults.cs

#Also take the keyboard keys (flight commands only; device binds are always taken)

Check boxwritten

Also imports the game's keyboard keys of flight commands (device binds are always imported). Off: only devices.

Source MainWindow.axaml:879 · ImportWizardKeyboard in MainWindowViewModel.GameHub.cs · setting ImportWizardKeyboard

#Also import devices that are not connected

Check boxwritten2 ×

Tooltip MSFS keeps the binds of every device it ever saw. Off: only the devices connected now.

MSFS import (wizard step 2 and the expert import): also takes the binds of devices that are not connected now. MSFS keeps the binds of every device it ever saw; off, only the connected devices are imported (--include-disconnected). Remembered with the import and export settings.

From the code MSFS keeps the binds of every device it ever saw: import takes the connected devices unless the user asks for the others too (engine --include-disconnected; remembered with the import/export settings).

Source MainWindow.axaml:881 · ImportIncludeDisconnected in MainWindowViewModel.RegistryGames.cs · setting ImportIncludeDisconnected

#Also import default presets the sim may not use

Check boxwritten2 ×

Tooltip Devices you never changed in MSFS run on a preset the sim ships. JoyPro takes it when the sim records that it uses it. On: also when that is not known (this can add binds the sim does not have).

MSFS import: devices you never changed in the sim run on a preset MSFS ships. JoyPro takes it when the sim records that it uses it; on, also when that is not known, which can add binds the sim does not have (--include-sim-defaults). Remembered with the import and export settings.

From the code MSFS runs an untouched device on a default preset it ships; JoyPro takes it when the sim's device records show it is used. On: also when that is not known (engine --include-sim-defaults; remembered like the one above).

Source MainWindow.axaml:884 · ImportIncludeSimDefaults in MainWindowViewModel.RegistryGames.cs · setting ImportIncludeSimDefaults

#Treat devices with the same name as one device (their ID changed over time)

Check boxwritten2 ×

Tooltip Windows gives a device a new ID now and then. On: its binds are read as one device, on the connected ID (else the newest). Two identical devices plugged in at once stay apart.

DCS import (on by default): Windows gives a device a new ID now and then. On, the binds of its IDs are read as one device, on the connected ID (else the newest); two identical devices plugged in at once stay apart (--merge-same-name). Saved in the settings.

Source MainWindow.axaml:889 · ImportDcsSameNameAsOne in MainWindowViewModel.cs · setting ImportDcsSameNameAsOne

#Only import connected devices

Check boxwritten2 ×

Tooltip Off: devices that are not plugged in now are imported too (useful for a stick you connect later). On: they are skipped and counted.

DCS import: on, devices that are not plugged in now are skipped and counted. Off (the default), they are imported too, useful for a stick you connect later (--only-connected). Saved in the settings.

From the code DCS import (saved in the settings): only the devices connected now (off: devices that are not plugged in are imported too), and one device under several Windows IDs read as one (on: the connected ID, else the newest file's).

Source MainWindow.axaml:894 · ImportDcsOnlyConnected in MainWindowViewModel.cs · setting ImportDcsOnlyConnected

#All my DCS aircraft

Check boxwritten2 ×

Imports every DCS aircraft that has binds. Off: only the aircraft ticked in the list below.

Source MainWindow.axaml:898 · ImportAllDcsPlanes in MainWindowViewModel.cs · setting ImportAllDcsPlanes

#Is selected

Check boxwritten4 ×

Ticks this DCS aircraft for the import (used when All my DCS aircraft is off).

Source MainWindow.axaml:909 · IsSelected in SelectableTagItem.cs · setting IsSelected

#Look first

Buttonwritten

Tooltip Shows what the game has, without changing your profile

"Look first": runs the game's scan and shows what it has in the Output panel. Nothing changes in the profile or the game. Engine: engine <game> scan.

From the code "Look first": what the game has, without changing the profile (engine ... scan), in the output panel.

Engine engine dcs scan · engine il2 scan · engine starcitizen scan · engine games integrations

Source MainWindow.axaml:918 · PreviewImportWizardCommand in MainWindowViewModel.GameHub.cs

#Import now

Buttonwritten

Imports the game with the choices of step 2. It first asks if you changed binds in JoyPro that this game does not have yet (an import would bring the old ones back), and before Start over it keeps a copy of your profile. The game's files are only read. Engine: engine dcs import --merge ..., engine il2 import, engine starcitizen import or engine <game> import.

#Use selected devices only

Check boxwritten

Expert import: imports only the devices ticked in the list below (--device per device). Off: every device.

Source MainWindow.axaml:971 · ImportUseSelectedDevices in MainWindowViewModel.cs · setting ImportUseSelectedDevices

#Merge into profile

Check boxwritten

Expert import: adds the game's binds to the open profile (--merge). Off: the profile's relations are replaced by the import.

Source MainWindow.axaml:1005 · ImportMerge in MainWindowViewModel.cs · setting ImportMerge

#Include defaults

Check boxwritten

Tooltip DCS: also takes the binds DCS gives by default to actions you have not bound yourself: the keyboard keys, and the binds DCS has for your exact device model. Only for aircraft and devices you already have binds for. Your own binds always win. DCS general joystick defaults, which it puts on every device, are left out.

Expert DCS import and scan (on by default): also takes the binds DCS gives by default to actions you have not bound: the keyboard keys and DCS's binds for your exact device model, only for aircraft and devices you already have binds for. Your own binds win; DCS's general joystick defaults are left out (--include-defaults). Remembered.

Source MainWindow.axaml:1006 · ImportIncludeDefaults in MainWindowViewModel.cs · setting ImportIncludeDefaults

#DCS: import keyboard commands

Check boxwritten

Expert DCS import: also reads the keyboard binds (--include-keyboard true).

Source MainWindow.axaml:1008 · ImportKeyboardCommands in MainWindowViewModel.cs · setting ImportKeyboardCommands

#Star Citizen: include keyboard commands (ship controls only)

Check boxwritten

Expert Star Citizen import: also reads the keyboard binds of ship controls (--include-keyboard true).

Source MainWindow.axaml:1009 · ImportStarCitizenIncludeKeyboard in MainWindowViewModel.cs · setting ImportStarCitizenIncludeKeyboard

#DCS: ignore *_easy aircraft

Check boxwritten

Expert DCS import: leaves out the *_easy variants of the aircraft (game-flight-mode copies), so they do not double the relations (--ignore-easy-planes true).

Source MainWindow.axaml:1010 · ImportIgnoreEasyPlanes in MainWindowViewModel.cs · setting ImportIgnoreEasyPlanes

#Import inverted

Check boxwritten

Expert import: takes the axis "invert" setting from the game into the bind's tuning (--import-inverted).

Source MainWindow.axaml:1015 · ImportInverted in MainWindowViewModel.cs · setting ImportInverted

#Import slider

Check boxwritten

Expert import: takes the axis "slider" setting from the game (--import-slider).

Source MainWindow.axaml:1016 · ImportSlider in MainWindowViewModel.cs · setting ImportSlider

#Import curvature

Check boxwritten

Expert import: takes the axis curvature from the game (--import-curvature).

Source MainWindow.axaml:1017 · ImportCurvature in MainWindowViewModel.cs · setting ImportCurvature

#Import deadzone

Check boxwritten

Expert import: takes the axis dead zone from the game (--import-deadzone).

Source MainWindow.axaml:1018 · ImportDeadzone in MainWindowViewModel.cs · setting ImportDeadzone

#Import sat-x

Check boxwritten

Expert import: takes the axis saturation X from the game (--import-saturation-x).

Source MainWindow.axaml:1019 · ImportSaturationX in MainWindowViewModel.cs · setting ImportSaturationX

#Import sat-y

Check boxwritten

Expert import: takes the axis saturation Y from the game (--import-saturation-y). Binds JoyPro exported itself always come back with their curves, whatever these boxes say.

Source MainWindow.axaml:1020 · ImportSaturationY in MainWindowViewModel.cs · setting ImportSaturationY

#Export

Buttonwritten

Exports to IL-2 with the Export page's mode (engine il2 export). In the game: data\input\global.actions holds your binds (Settings > Key mapping shows them).

Engine engine il2 export

Source MainWindow.axaml:1039 · ExportIl2Command in MainWindowViewModel.cs

#Detect

Buttonwritten

Looks for the picked game's control file (engine <game> paths) and fills File / Folder with it (the newest when there are several; the others are in the Output panel).

Source MainWindow.axaml:1067 · DetectRegistryGamePathCommand in MainWindowViewModel.RegistryGames.cs

#Scan

Buttonwritten

Shows what the picked game's control file has in the Output panel without changing anything (engine <game> scan).

Source MainWindow.axaml:1081 · ScanRegistryGameCommand in MainWindowViewModel.RegistryGames.cs

#Export

Buttonwritten

Exports to the picked game with the Export page's mode (engine <game> export; with the dry run box only shows what would change). Only flight controls are written; everything else in the game's file stays.

Source MainWindow.axaml:1083 · ExportRegistryGameCommand in MainWindowViewModel.RegistryGames.cs

#Export as dry run (show changes only)

Check boxwritten

The export of the picked game only shows what would change (--dry-run); nothing is written.

Source MainWindow.axaml:1084 · RegistryGameDryRun in MainWindowViewModel.RegistryGames.cs · setting RegistryGameDryRun

#Include keyboard binds (flight actions only)

Check boxwritten

Expert import and export of the picked game: also reads or writes the keyboard binds of flight actions (--include-keyboard). Off: only device binds. Remembered per game.

From the code Keyboard binds are only imported and exported when the user asks for them (flight actions only).

Source MainWindow.axaml:1085 · RegistryGameIncludeKeyboard in MainWindowViewModel.RegistryGames.cs · setting RegistryGameIncludeKeyboard

#Nuke: remove all binds from devices JoyPro does not use

Check boxwritten

With the expert export of a game: connected devices that have no bind in your profile lose all their binds in that game (--nuke-untouched-devices). The same setting as Also clear my other devices on the Export page.

Source MainWindow.axaml:1090 · ExportNukeUntouchedDevices in MainWindowViewModel.cs · setting ExportNukeUntouchedDevices

#Write into my MSFS profiles

Check boxwritten

Tooltip The export puts the binds into the profile MSFS 2024 uses for each device and category (Steam or Microsoft Store), backed up first. Off: only import files.

MSFS 2024 export (on by default): writes the binds into the profile the sim uses for each device and category (Steam or Microsoft Store), backed up first. Off: JoyPro writes only import files (--user-profiles false). The same setting as on the Export page. In the game: your MSFS 2024 controls profiles hold the binds.

From the code On: the export writes into the user's MSFS 2024 profiles (engine default; off: --user-profiles false).

Source MainWindow.axaml:1091 · MsfsWriteUserProfiles in MainWindowViewModel.MsfsProfiles.cs · setting MsfsWriteUserProfiles

#Also write MSFS import files for every device

Check boxwritten

Tooltip Off: import files only where JoyPro could not write your profile.

MSFS 2024 export: also writes an import file for every device and category (--import-files). Off: import files only where JoyPro could not write your profile. Import them in MSFS 2024 under Settings > Controls.

From the code On: import files for every device and category (--import-files), not only where the profile could not be written.

Source MainWindow.axaml:1093 · MsfsAlwaysImportFiles in MainWindowViewModel.MsfsProfiles.cs · setting MsfsAlwaysImportFiles

#Open folder

Buttonwritten

Opens the folder with the MSFS 2024 import files (one per device and category), for profiles JoyPro could not write itself. Import them in MSFS 2024 under Settings > Controls.

Source MainWindow.axaml:1113 · OpenMsfsImportFilesFolderCommand in MainWindowViewModel.RegistryGames.cs

#Refresh DB

Buttonwritten

Rebuilds the picked game's command list from its files (engine <game> refresh-db, from DB Source when set). Games whose list ships with JoyPro say so.

Source MainWindow.axaml:1120 · RefreshRegistryGameDbCommand in MainWindowViewModel.RegistryGames.cs

#Answer device card question

Buttonwritten

The orange Which grip? or Which model? on a device card: opens the Layout page with this device and its choice open. Which grip?: a base does not say which grip is on it. Which model?: several products report the same USB id. Your answer is kept for this device, also after a restart, and the chip goes away.

Engine engine layout suggest

Source MainWindow.axaml:1162 · AnswerDeviceCardQuestionCommand in MainWindowViewModel.DeviceCenter.cs

#Yes

Buttonwritten

Yes on a device card: downloads the maker's photo of this device model from the maker's site and shows it on the card. The answer is kept for this model; Settings > Privacy changes it.

From the code The answer on a card to "Download the maker's photo?": yes / no for its model, always / never for every device; the cards' pictures follow at once (a photo is downloaded only after a yes).

Source MainWindow.axaml:1175 · CardPhotoYesCommand in MainWindowViewModel.DeviceCenter.cs

#No

Buttonwritten

No maker's photo for this device; JoyPro's drawing stays. Asked again only from Settings > Privacy.

Source MainWindow.axaml:1176 · CardPhotoNoCommand in MainWindowViewModel.DeviceCenter.cs

#Always for all my devices

Buttonwritten

Downloads the maker's photo of every device from now on without asking (Settings > Privacy: always).

Source MainWindow.axaml:1177 · CardPhotoAlwaysCommand in MainWindowViewModel.DeviceCenter.cs

#Never

Buttonwritten

Never downloads makers' photos of devices; JoyPro's drawings are shown (Settings > Privacy changes it back).

Source MainWindow.axaml:1178 · CardPhotoNeverCommand in MainWindowViewModel.DeviceCenter.cs

#Download

Buttonwritten

Downloads the 3D views of the connected devices from JoyPro's releases; the Layout page and the Bind page's picture then have 3D view.

Source MainWindow.axaml:1191 · AcceptDevice3DCommand in MainWindowViewModel.Device3D.cs

#Download

Buttonwritten

Downloads every reference photo JoyPro knows for the connected devices, in the background; each is checked against JoyPro's record. It counts as your yes for these devices.

Source MainWindow.axaml:1199 · AcceptReferencePhotosCommand in MainWindowViewModel.ReferencePhotos.cs

#Always download

Buttonwritten

Tooltip Download the reference photos of every device that appears, in the background (Settings > Privacy)

Always download: downloads the offered reference photos now and, from now on, the photos of every device that appears, in the background. It also allows the photos to be shown (Settings > Privacy switches it off).

Source MainWindow.axaml:1201 · AlwaysReferencePhotosCommand in MainWindowViewModel.ReferencePhotos.cs

#No

Buttonwritten

Tooltip Do not download photos of these devices; JoyPro's drawings stay

No on the reference photo offer: no photos for these devices, JoyPro's drawings stay. The answer is kept per device model; Settings > Privacy forgets the answers.

Source MainWindow.axaml:1203 · NeverReferencePhotosCommand in MainWindowViewModel.ReferencePhotos.cs

#On

Switchwritten

Tooltip After a game closes, JoyPro asks whether to take the binds you changed in the game into your profile

The game watcher's main switch (on by default, kept across restarts): after a game closes, JoyPro asks whether to take the binds you changed in the game into your profile. Only games ticked Watch for changes are watched; off, none is. The same as Settings > Games > Watch game configs.

Source MainWindow.axaml:1250 · WatchGameConfigs in MainWindowViewModel.GameSync.cs · setting WatchGameConfigs

#Toggle overlay

Buttonwritten

Shows or hides the HUD overlay over your game (the label says which). It shows your devices live as designed on the HUD page.

Source MainWindow.axaml:1267 · ToggleOverlayCommand in MainWindowViewModel.Overlay.cs