DCS World Wiki - Hoggitworld.com - User contributions [en]

User:Sodaplayer/linux-sandbox

2023-01-03T22:40:30Z

Sodaplayer: Add modding command

DCS: World can be played on a Linux machine along with supporting programs like [http://dcssimpleradio.com/ SimpleRadio Standalone] and [https://www.tacview.net/ TacView]. This article serves as a collection of how-to guides for setting up DCS and its supporting programs on Linux, and it this article contains guides for troubleshooting peripherals like joysticks and face-tracking devices.

The guides assume you have some basic Linux command line skills. You should be comfortable navigating to and viewing the contents of directories, with user permissions, editing files with a text editor, using symbolic links and environment variables.

Some conventions will be used in this guide. When specifying a directory path that may vary from user to user, it will be surrounded by angled brackets: <code><nowiki><example></nowiki>/rest/of/path</code>.

== Peripherals ==
There are other good resources for configuring and troubleshooting joysticks on Linux. This section will be focused on being a streamlined reference for getting peripherals working through Wine/Proton and cover common issues.

: ''See also: [https://wiki.archlinux.org/title/Gamepad ArchWiki Gamepad Article] for how joysticks work in Linux''

=== Troubleshooting ===

==== Permissions ====
If your joystick isn't appearing in DCS, check if you have permission to access it. Most modern joysticks are available through the [https://docs.kernel.org/input/input.html#evdev evdev] interface and will appear as a device in <code>/dev/input/event*</code>. To see what device is mapped to your joystick, list the files inside <code>/dev/input/by-id/</code> to see the names of each device mapped to a <code>/dev/input/event*</code> entry.

===== Example =====
In this example, the user has a Logitech Extreme 3D Pro (X3D) and a pair of Saitek Pro Flight Rudder Pedals. They're able to use the X3D, but are unable to see the pedals in game.

Here, you can see that the X3D is linked to <code>/dev/input/event0</code> and that the pedals are linked to <code>/dev/input/event1</code>.
<nowiki>
$ ls -l /dev/input/by-id | grep event

... Dec 13 13:37 usb-Logitech_Logitech_Extreme_3D-event-joystick -> ../event0
... Dec 13 13:37 sb-Saitek_Saitek_Pro_Flight_Rudder_Pedals-event-if00 -> ../event1</nowiki>

When we look at the permissions of the events, we can see '''event0''' is marked with a plus symbol, but '''event1''' isn't.

<nowiki>
$ ls -l /dev/input | grep event

crw-rw----+ 1 root input ... Dec 13 13:37 event0
crw-rw---- 1 root input ... Dec 13 13:37 event1</nowiki>

The plus symbol means that there's additional permissions being managed by an access control list (ACL). We can compare the ACLs for both devices and confirm a difference. The user, '''john''' has access to '''event0''', but not '''event1'''.

'''/dev/input/event0:'''
<nowiki>
$ getfacl event0

# file: event0
# owner: root
# group: input
user::rw-
user:john:rw-
group::rw-
mask::rw-
other::---</nowiki>

'''/dev/input/event1:'''
<nowiki>
$ getfacl event1

# file: event1
# owner: root
# group: input
user::rw-
group::rw-
other::---</nowiki>

We can fix this with a '''udev''' rule.

'''/etc/udev/rules.d/70-saitek-rudder.rule'''
<nowiki>
SUBSYSTEM=="input", ATTRS{idProduct}=="0763", ATTRS{idVendor}=="06a3", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"</nowiki>

Use <code>lsusb</code> to get the values for ''idProduct'' and ''idVendor''.
<nowiki>
$ lsusb

Bus 001 Device 014: ID '''06a3:0763''' Saitek PLC Pro Flight Rudder Pedals</nowiki>

=== Virtual Inputs ===
You may want to bind joystick controls to mouse buttons and key-presses. In Linux, the [https://www.kernel.org/doc/html/latest/input/uinput.html uinput] module can be used to create virtual keyboards, mouses, and joysticks inputs.

==== Useful Applications ====
Some applications can read joystick inputs and configure virtual devices:
* [https://github.com/AntiMicroX/antimicrox AntiMicroX] - Maps controllers to mouse and keyboard buttons.
* [https://github.com/jgeumlek/MoltenGamepad MoltenGamepad] - Allows you to combine or split controllers into virtual gamepads.

== Saved Game / Profile ==
Your DCS settings are saved in ''Saved Games/DCS'' folder. On Windows, this is typically located at <code>C:\Users\<username>\Saved Games\DCS</code>. When using Wine, this folder will be placed inside a Wine prefix.

''TODO''

== Modding without JSGME/OVGME ==
''TODO''

<nowiki>
$ fuse-overlayfs -o lowerdir=<modfolder>/<mod1>:<modfolder>/<mod2>:<DCS Installation> <DCS Installation>
</nowiki>

== Simple Radio Standalone ==

<ref>https://old.reddit.com/r/linux4noobs/comments/firqs9/getting_windows_wpf_applications_to_run_with_wine/</ref>
<references />

== See Also ==

User:Sodaplayer/linux-sandbox

2023-01-02T19:11:33Z

Sodaplayer: Fix formatting

DCS: World can be played on a Linux machine along with supporting programs like [http://dcssimpleradio.com/ SimpleRadio Standalone] and [https://www.tacview.net/ TacView]. This article serves as a collection of how-to guides for setting up DCS and its supporting programs on Linux, and it this article contains guides for troubleshooting peripherals like joysticks and face-tracking devices.

The guides assume you have some basic Linux command line skills. You should be comfortable navigating to and viewing the contents of directories, with user permissions, editing files with a text editor, using symbolic links and environment variables.

Some conventions will be used in this guide. When specifying a directory path that may vary from user to user, it will be surrounded by angled brackets: <code><nowiki><example></nowiki>/rest/of/path</code>.

== Peripherals ==
There are other good resources for configuring and troubleshooting joysticks on Linux. This section will be focused on being a streamlined reference for getting peripherals working through Wine/Proton and cover common issues.

: ''See also: [https://wiki.archlinux.org/title/Gamepad ArchWiki Gamepad Article] for how joysticks work in Linux''

=== Troubleshooting ===

==== Permissions ====
If your joystick isn't appearing in DCS, check if you have permission to access it. Most modern joysticks are available through the [https://docs.kernel.org/input/input.html#evdev evdev] interface and will appear as a device in <code>/dev/input/event*</code>. To see what device is mapped to your joystick, list the files inside <code>/dev/input/by-id/</code> to see the names of each device mapped to a <code>/dev/input/event*</code> entry.

===== Example =====
In this example, the user has a Logitech Extreme 3D Pro (X3D) and a pair of Saitek Pro Flight Rudder Pedals. They're able to use the X3D, but are unable to see the pedals in game.

Here, you can see that the X3D is linked to <code>/dev/input/event0</code> and that the pedals are linked to <code>/dev/input/event1</code>.
<nowiki>
$ ls -l /dev/input/by-id | grep event

... Dec 13 13:37 usb-Logitech_Logitech_Extreme_3D-event-joystick -> ../event0
... Dec 13 13:37 sb-Saitek_Saitek_Pro_Flight_Rudder_Pedals-event-if00 -> ../event1</nowiki>

When we look at the permissions of the events, we can see '''event0''' is marked with a plus symbol, but '''event1''' isn't.

<nowiki>
$ ls -l /dev/input | grep event

crw-rw----+ 1 root input ... Dec 13 13:37 event0
crw-rw---- 1 root input ... Dec 13 13:37 event1</nowiki>

The plus symbol means that there's additional permissions being managed by an access control list (ACL). We can compare the ACLs for both devices and confirm a difference. The user, '''john''' has access to '''event0''', but not '''event1'''.

'''/dev/input/event0:'''
<nowiki>
$ getfacl event0

# file: event0
# owner: root
# group: input
user::rw-
user:john:rw-
group::rw-
mask::rw-
other::---</nowiki>

'''/dev/input/event1:'''
<nowiki>
$ getfacl event1

# file: event1
# owner: root
# group: input
user::rw-
group::rw-
other::---</nowiki>

We can fix this with a '''udev''' rule.

'''/etc/udev/rules.d/70-saitek-rudder.rule'''
<nowiki>
SUBSYSTEM=="input", ATTRS{idProduct}=="0763", ATTRS{idVendor}=="06a3", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"</nowiki>

Use <code>lsusb</code> to get the values for ''idProduct'' and ''idVendor''.
<nowiki>
$ lsusb

Bus 001 Device 014: ID '''06a3:0763''' Saitek PLC Pro Flight Rudder Pedals</nowiki>

=== Virtual Inputs ===
You may want to bind joystick controls to mouse buttons and key-presses. In Linux, the [https://www.kernel.org/doc/html/latest/input/uinput.html uinput] module can be used to create virtual keyboards, mouses, and joysticks inputs.

==== Useful Applications ====
Some applications can read joystick inputs and configure virtual devices:
* [https://github.com/AntiMicroX/antimicrox AntiMicroX] - Maps controllers to mouse and keyboard buttons.
* [https://github.com/jgeumlek/MoltenGamepad MoltenGamepad] - Allows you to combine or split controllers into virtual gamepads.

== Saved Game / Profile ==
Your DCS settings are saved in ''Saved Games/DCS'' folder. On Windows, this is typically located at <code>C:\Users\<username>\Saved Games\DCS</code>. When using Wine, this folder will be placed inside a Wine prefix.

== Simple Radio Standalone ==

<ref>https://old.reddit.com/r/linux4noobs/comments/firqs9/getting_windows_wpf_applications_to_run_with_wine/</ref>
<references />

== See Also ==

User:Sodaplayer/linux-sandbox

2023-01-02T19:08:23Z

Sodaplayer: Add article introduction

DCS: World can be played on a Linux machine along with supporting programs like [http://dcssimpleradio.com/ | SimpleRadio Standalone] and [https://www.tacview.net/ | TacView]. This article serves as a collection of how-to guides for setting up DCS and its supporting programs on Linux, and it this article contains guides for troubleshooting peripherals like joysticks and face-tracking devices.

The guides assume you have some basic Linux command line skills. You should be comfortable navigating to and viewing the contents of directories, with user permissions, editing files with a text editor, using symbolic links and environment variables.

Some conventions will be used in this guide. When specifying a directory path that may vary from user to user, it will be surrounded by angled brackets: <code><nowiki><example></nowiki>/rest/of/path</code>.

== Peripherals ==
There are other good resources for configuring and troubleshooting joysticks on Linux. This section will be focused on being a streamlined reference for getting peripherals working through Wine/Proton and cover common issues.

: ''See also: [https://wiki.archlinux.org/title/Gamepad ArchWiki Gamepad Article] for how joysticks work in Linux''

=== Troubleshooting ===

==== Permissions ====
If your joystick isn't appearing in DCS, check if you have permission to access it. Most modern joysticks are available through the [https://docs.kernel.org/input/input.html#evdev evdev] interface and will appear as a device in <code>/dev/input/event*</code>. To see what device is mapped to your joystick, list the files inside <code>/dev/input/by-id/</code> to see the names of each device mapped to a <code>/dev/input/event*</code> entry.

===== Example =====
In this example, the user has a Logitech Extreme 3D Pro (X3D) and a pair of Saitek Pro Flight Rudder Pedals. They're able to use the X3D, but are unable to see the pedals in game.

Here, you can see that the X3D is linked to <code>/dev/input/event0</code> and that the pedals are linked to <code>/dev/input/event1</code>.
<nowiki>
$ ls -l /dev/input/by-id | grep event

... Dec 13 13:37 usb-Logitech_Logitech_Extreme_3D-event-joystick -> ../event0
... Dec 13 13:37 sb-Saitek_Saitek_Pro_Flight_Rudder_Pedals-event-if00 -> ../event1</nowiki>

When we look at the permissions of the events, we can see '''event0''' is marked with a plus symbol, but '''event1''' isn't.

<nowiki>
$ ls -l /dev/input | grep event

crw-rw----+ 1 root input ... Dec 13 13:37 event0
crw-rw---- 1 root input ... Dec 13 13:37 event1</nowiki>

The plus symbol means that there's additional permissions being managed by an access control list (ACL). We can compare the ACLs for both devices and confirm a difference. The user, '''john''' has access to '''event0''', but not '''event1'''.

'''/dev/input/event0:'''
<nowiki>
$ getfacl event0

# file: event0
# owner: root
# group: input
user::rw-
user:john:rw-
group::rw-
mask::rw-
other::---</nowiki>

'''/dev/input/event1:'''
<nowiki>
$ getfacl event1

# file: event1
# owner: root
# group: input
user::rw-
group::rw-
other::---</nowiki>

We can fix this with a '''udev''' rule.

'''/etc/udev/rules.d/70-saitek-rudder.rule'''
<nowiki>
SUBSYSTEM=="input", ATTRS{idProduct}=="0763", ATTRS{idVendor}=="06a3", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"</nowiki>

Use <code>lsusb</code> to get the values for ''idProduct'' and ''idVendor''.
<nowiki>
$ lsusb

Bus 001 Device 014: ID '''06a3:0763''' Saitek PLC Pro Flight Rudder Pedals</nowiki>

=== Virtual Inputs ===
You may want to bind joystick controls to mouse buttons and key-presses. In Linux, the [https://www.kernel.org/doc/html/latest/input/uinput.html uinput] module can be used to create virtual keyboards, mouses, and joysticks inputs.

==== Useful Applications ====
Some applications can read joystick inputs and configure virtual devices:
* [https://github.com/AntiMicroX/antimicrox AntiMicroX] - Maps controllers to mouse and keyboard buttons.
* [https://github.com/jgeumlek/MoltenGamepad MoltenGamepad] - Allows you to combine or split controllers into virtual gamepads.

== Saved Game / Profile ==
Your DCS settings are saved in ''Saved Games/DCS'' folder. On Windows, this is typically located at <code>C:\Users\<username>\Saved Games\DCS</code>. When using Wine, this folder will be placed inside a Wine prefix.

== Simple Radio Standalone ==

<ref>https://old.reddit.com/r/linux4noobs/comments/firqs9/getting_windows_wpf_applications_to_run_with_wine/</ref>
<references />

== See Also ==

User:Sodaplayer/linux-sandbox

2022-12-29T19:06:42Z

Sodaplayer: test ref tag

== Peripherals ==
There are other good resources for configuring and troubleshooting joysticks on Linux. This section will be focused on being a streamlined reference for getting peripherals working through Wine/Proton and cover common issues.

: ''See also: [https://wiki.archlinux.org/title/Gamepad The ArchWiki Gamepad Article] for how joysticks work in Linux''

=== Troubleshooting ===

==== Permissions ====
If your joystick isn't appearing in DCS, check if you have permission to access it. Most modern joysticks are available through the [https://docs.kernel.org/input/input.html#evdev evdev] interface and will appear as a device in <code>/dev/input/event*</code>. To see what device is mapped to your joystick, list the files inside <code>/dev/input/by-id/</code> to see the names of each device mapped to a <code>/dev/input/event*</code> entry.

===== Example =====
In this example, the user has a Logitech Extreme 3D Pro (X3D) and a pair of Saitek Pro Flight Rudder Pedals. They're able to use the X3D, but are unable to see the pedals in game.

Here, you can see that the X3D is linked to <code>/dev/input/event0</code> and that the pedals are linked to <code>/dev/input/event1</code>.
<nowiki>
$ ls -l /dev/input/by-id | grep event

... Dec 13 13:37 usb-Logitech_Logitech_Extreme_3D-event-joystick -> ../event0
... Dec 13 13:37 sb-Saitek_Saitek_Pro_Flight_Rudder_Pedals-event-if00 -> ../event1</nowiki>

When we look at the permissions of the events, we can see '''event0''' is marked with a plus symbol, but '''event1''' isn't.

<nowiki>
$ ls -l /dev/input | grep event

crw-rw----+ 1 root input ... Dec 13 13:37 event0
crw-rw---- 1 root input ... Dec 13 13:37 event1</nowiki>

The plus symbol means that there's additional permissions being managed by an access control list (ACL). We can compare the ACLs for both devices and confirm a difference. The user, '''john''' has access to '''event0''', but not '''event1'''.

'''/dev/input/event0:'''
<nowiki>
$ getfacl event0

# file: event0
# owner: root
# group: input
user::rw-
user:john:rw-
group::rw-
mask::rw-
other::---</nowiki>

'''/dev/input/event1:'''
<nowiki>
$ getfacl event1

# file: event1
# owner: root
# group: input
user::rw-
group::rw-
other::---</nowiki>

We can fix this with a '''udev''' rule.

'''/etc/udev/rules.d/70-saitek-rudder.rule'''
<nowiki>
SUBSYSTEM=="input", ATTRS{idProduct}=="0763", ATTRS{idVendor}=="06a3", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"</nowiki>

Use <code>lsusb</code> to get the values for ''idProduct'' and ''idVendor''.

$ lsusb
Bus 001 Device 014: ID '''06a3:0763''' Saitek PLC Pro Flight Rudder Pedals

=== Virtual Inputs ===
You may want to bind joystick controls to mouse buttons and key-presses. In Linux, the [https://www.kernel.org/doc/html/latest/input/uinput.html uinput] module can be used to create virtual keyboards, mouses, and joysticks inputs.

==== Useful Applications ====
Some applications can read joystick inputs and configure virtual devices:
* [https://github.com/AntiMicroX/antimicrox AntiMicroX] - Maps controllers to mouse and keyboard buttons.
* [https://github.com/jgeumlek/MoltenGamepad MoltenGamepad] - Allows you to combine or split controllers into virtual gamepads.

== Simple Radio Standalone ==

<ref>https://old.reddit.com/r/linux4noobs/comments/firqs9/getting_windows_wpf_applications_to_run_with_wine/</ref>
<references />

User:Sodaplayer/linux-sandbox

2022-12-29T00:00:49Z

Sodaplayer: Dumping some references before I forget them

== Peripherals ==
There are other good resources for configuring and troubleshooting joysticks on Linux. This section will be focused on being a streamlined reference for getting peripherals working through Wine/Proton and cover common issues.

: ''See also: [https://wiki.archlinux.org/title/Gamepad The ArchWiki Gamepad Article] for how joysticks work in Linux''

=== Troubleshooting ===

==== Permissions ====
If your joystick isn't appearing in DCS, check if you have permission to access it. Most modern joysticks are available through the [https://docs.kernel.org/input/input.html#evdev evdev] interface and will appear as a device in <code>/dev/input/event*</code>. To see what device is mapped to your joystick, list the files inside <code>/dev/input/by-id/</code> to see the names of each device mapped to a <code>/dev/input/event*</code> entry.

===== Example =====
In this example, the user has a Logitech Extreme 3D Pro (X3D) and a pair of Saitek Pro Flight Rudder Pedals. They're able to use the X3D, but are unable to see the pedals in game.

Here, you can see that the X3D is linked to <code>/dev/input/event0</code> and that the pedals are linked to <code>/dev/input/event1</code>.
<nowiki>
$ ls -l /dev/input/by-id | grep event

... Dec 13 13:37 usb-Logitech_Logitech_Extreme_3D-event-joystick -> ../event0
... Dec 13 13:37 sb-Saitek_Saitek_Pro_Flight_Rudder_Pedals-event-if00 -> ../event1</nowiki>

When we look at the permissions of the events, we can see '''event0''' is marked with a plus symbol, but '''event1''' isn't.

<nowiki>
$ ls -l /dev/input | grep event

crw-rw----+ 1 root input ... Dec 13 13:37 event0
crw-rw---- 1 root input ... Dec 13 13:37 event1</nowiki>

The plus symbol means that there's additional permissions being managed by an access control list (ACL). We can compare the ACLs for both devices and confirm a difference. The user, '''john''' has access to '''event0''', but not '''event1'''.

'''/dev/input/event0:'''
<nowiki>
$ getfacl event0

# file: event0
# owner: root
# group: input
user::rw-
user:john:rw-
group::rw-
mask::rw-
other::---</nowiki>

'''/dev/input/event1:'''
<nowiki>
$ getfacl event1

# file: event1
# owner: root
# group: input
user::rw-
group::rw-
other::---</nowiki>

We can fix this with a '''udev''' rule.

'''/etc/udev/rules.d/70-saitek-rudder.rule'''
<nowiki>
SUBSYSTEM=="input", ATTRS{idProduct}=="0763", ATTRS{idVendor}=="06a3", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"</nowiki>

Use <code>lsusb</code> to get the values for ''idProduct'' and ''idVendor''.

$ lsusb
Bus 001 Device 014: ID '''06a3:0763''' Saitek PLC Pro Flight Rudder Pedals

=== Virtual Inputs ===
You may want to bind joystick controls to mouse buttons and key-presses. In Linux, the [https://www.kernel.org/doc/html/latest/input/uinput.html uinput] module can be used to create virtual keyboards, mouses, and joysticks inputs.

==== Useful Applications ====
Some applications can read joystick inputs and configure virtual devices:
* [https://github.com/AntiMicroX/antimicrox AntiMicroX] - Maps controllers to mouse and keyboard buttons.
* [https://github.com/jgeumlek/MoltenGamepad MoltenGamepad] - Allows you to combine or split controllers into virtual gamepads.

== Simple Radio Standalone ==
https://old.reddit.com/r/linux4noobs/comments/firqs9/getting_windows_wpf_applications_to_run_with_wine/

User:Sodaplayer/linux-sandbox

2022-12-27T10:09:51Z

Sodaplayer: /* Example */

User:Sodaplayer/linux-sandbox

2022-12-27T09:44:14Z

Sodaplayer: /* Peripherals */ Correct name

== Peripherals ==
There are other good resources for configuring and troubleshooting joysticks on Linux. This section will be focused on being a streamlined reference for getting peripherals working through Wine/Proton and cover common issues.

: ''See also: [https://wiki.archlinux.org/title/Gamepad The ArchWiki Gamepad Article] for how joysticks work in Linux''

=== Troubleshooting ===

==== Permissions ====
If your joystick isn't appearing in DCS, check if you have permission to access it. Most modern joysticks are available through the [https://docs.kernel.org/input/input.html#evdev evdev] interface and will appear as a device in <code>/dev/input/event*</code>. To see what device is mapped to your joystick, list the files inside <code>/dev/input/by-id/</code> to see the names of each device mapped to a <code>/dev/input/event*</code> entry.

===== Example =====
In this example, the user has a Logitech Extreme 3D Pro (X3D) and a pair of Saitek Pro Flight Rudder Pedals. They're able to use the X3D, but are unable to see the pedals in game.

Here, you can see that the X3D is linked to <code>/dev/input/event0</code> and that the pedals are linked to <code>/dev/input/event1</code>.
<nowiki>
$ ls -l /dev/input/by-id | grep event

... Dec 13 13:37 usb-Logitech_Logitech_Extreme_3D-event-joystick -> ../event0
... Dec 13 13:37 sb-Saitek_Saitek_Pro_Flight_Rudder_Pedals-event-if00 -> ../event1</nowiki>

When we look at the permissions of the events, we can see '''event0''' is marked with a plus symbol, but '''event1''' isn't.

<nowiki>
$ ls -l /dev/input | grep event

crw-rw----+ 1 root input ... Dec 13 13:37 event0
crw-rw---- 1 root input ... Dec 13 13:37 event1</nowiki>

The plus symbol means that there's additional permissions being managed by an access control list (ACL). We can compare the ACLs for both devices and confirm a difference. The user, '''john''' has access to '''event0''', but not '''event1'''

'''/dev/input/event0:'''
<nowiki>
$ getfacl event0

# file: event0
# owner: root
# group: input
user::rw-
user:john:rw-
group::rw-
mask::rw-
other::---</nowiki>

'''/dev/input/event1:'''
<nowiki>
$ getfacl event1

# file: event1
# owner: root
# group: input
user::rw-
group::rw-
other::---</nowiki>

=== Virtual Inputs ===
You may want to bind joystick controls to mouse buttons and key-presses. In Linux, the [https://www.kernel.org/doc/html/latest/input/uinput.html uinput] module can be used to create virtual keyboards, mouses, and joysticks inputs.

==== Useful Applications ====
Some applications can read joystick inputs and configure virtual devices:
* [https://github.com/AntiMicroX/antimicrox AntiMicroX] - Maps controllers to mouse and keyboard buttons.
* [https://github.com/jgeumlek/MoltenGamepad MoltenGamepad] - Allows you to combine or split controllers into virtual gamepads.

User:Sodaplayer/linux-sandbox

2022-12-27T09:43:19Z

Sodaplayer: Continue working on permission example

== Peripherals ==
There are other good resources for configuring and troubleshooting joysticks on Linux. This section will be focused on being a streamlined reference for getting peripherals working through Wine/Proton and cover common issues.

: ''See also: [https://wiki.archlinux.org/title/Gamepad The Arch Linux Wiki Gamepad Article] for how joysticks work in Linux''

=== Troubleshooting ===

==== Permissions ====
If your joystick isn't appearing in DCS, check if you have permission to access it. Most modern joysticks are available through the [https://docs.kernel.org/input/input.html#evdev evdev] interface and will appear as a device in <code>/dev/input/event*</code>. To see what device is mapped to your joystick, list the files inside <code>/dev/input/by-id/</code> to see the names of each device mapped to a <code>/dev/input/event*</code> entry.

===== Example =====
In this example, the user has a Logitech Extreme 3D Pro (X3D) and a pair of Saitek Pro Flight Rudder Pedals. They're able to use the X3D, but are unable to see the pedals in game.

Here, you can see that the X3D is linked to <code>/dev/input/event0</code> and that the pedals are linked to <code>/dev/input/event1</code>.
<nowiki>
$ ls -l /dev/input/by-id | grep event

... Dec 13 13:37 usb-Logitech_Logitech_Extreme_3D-event-joystick -> ../event0
... Dec 13 13:37 sb-Saitek_Saitek_Pro_Flight_Rudder_Pedals-event-if00 -> ../event1</nowiki>

When we look at the permissions of the events, we can see '''event0''' is marked with a plus symbol, but '''event1''' isn't.

<nowiki>
$ ls -l /dev/input | grep event

crw-rw----+ 1 root input ... Dec 13 13:37 event0
crw-rw---- 1 root input ... Dec 13 13:37 event1</nowiki>

The plus symbol means that there's additional permissions being managed by an access control list (ACL). We can compare the ACLs for both devices and confirm a difference. The user, '''john''' has access to '''event0''', but not '''event1'''

'''/dev/input/event0:'''
<nowiki>
$ getfacl event0

# file: event0
# owner: root
# group: input
user::rw-
user:john:rw-
group::rw-
mask::rw-
other::---</nowiki>

'''/dev/input/event1:'''
<nowiki>
$ getfacl event1

# file: event1
# owner: root
# group: input
user::rw-
group::rw-
other::---</nowiki>

=== Virtual Inputs ===
You may want to bind joystick controls to mouse buttons and key-presses. In Linux, the [https://www.kernel.org/doc/html/latest/input/uinput.html uinput] module can be used to create virtual keyboards, mouses, and joysticks inputs.

==== Useful Applications ====
Some applications can read joystick inputs and configure virtual devices:
* [https://github.com/AntiMicroX/antimicrox AntiMicroX] - Maps controllers to mouse and keyboard buttons.
* [https://github.com/jgeumlek/MoltenGamepad MoltenGamepad] - Allows you to combine or split controllers into virtual gamepads.

User:Sodaplayer/linux-sandbox

2022-12-27T08:45:33Z

Sodaplayer: Update permissions section

User:Sodaplayer/linux-sandbox

2022-12-27T08:00:02Z

Sodaplayer: Update description and list for applications

== Peripherals ==
There are other good resources for configuring and troubleshooting joysticks on Linux. To avoid a replication of those other resources, this section will be focused on getting peripherals running through Wine/Proton and cover common issues.

=== Permissions ===

=== Virtual Inputs ===
You may want to bind joystick controls to mouse buttons and key-presses. In Linux, the [https://www.kernel.org/doc/html/latest/input/uinput.html uinput] module can be used to create virtual keyboards, mouses, and joysticks inputs.

==== Useful Applications ====
Some applications can read joystick inputs and configure virtual devices:
* [https://github.com/AntiMicroX/antimicrox AntiMicroX] - Maps controllers to mouse and keyboard buttons.
* [https://github.com/jgeumlek/MoltenGamepad MoltenGamepad] - Allows you to combine or split controllers into virtual gamepads.

User:Sodaplayer/linux-sandbox

2022-12-27T07:36:20Z

Sodaplayer: Start peripharels draft

User:Sodaplayer/linux-sandbox

2022-12-25T23:55:52Z

Sodaplayer: Creating a space to draft and preview contributions.

Creating a space to draft and preview contributions.