MissionControl/.github/ISSUE_TEMPLATE/controller_request.yaml
2021-09-03 01:00:47 +02:00

63 lines
3.3 KiB
YAML

name: Controller Request
description: Request support for a new controller.
title: "[Controller Request]: "
labels: [controller request]
body:
- type: markdown
attributes:
value: |
This template is for requesting support for new controllers. Please search the issue tracker for existing open issues, and check the list of [supported controllers](https://github.com/ndeadly/MissionControl#supported-controllers) before opening a new controller request. If your controller is on the list but not behaving correctly, a bug report may be more appropriate.
- type: input
id: name
attributes:
label: Controller Name
description: The name and/or model number of the controller.
validations:
required: true
- type: dropdown
id: behaviour
attributes:
label: Current Controller Behaviour
description: How does the controller behave after placing it into sync mode while on the `Change Grip/Order` menu of the console?
options:
- Controller is not successful in pairing with the console
- Controller successfully pairs with the console but doesn't respond to inputs
- Controller successfully pairs with the console and responds to inputs but control mapping is incorrect
- Other (please specify below)
validations:
required: true
- type: input
id: vid-pid
attributes:
label: Controller vendor and product ID
description: The vendor and product ID of the controller. If your controller can be paired to the console you can dump this information from the pairing database using my [btdb](https://github.com/ndeadly/MissionControl/releases/download/v0.3.0/btdb.nro) application.
placeholder: ex. 057e:2009
- type: checkboxes
id: features
attributes:
label: Supported Features
description: Features supported by this controller
options:
- label: Rumble/Vibration
- label: Motion Controls
- label: Player Number Indicator
- label: Battery Level Reporting
- type: textarea
id: report-format
attributes:
label: Input Report Format
description: If your controller can be paired to the console but the buttons aren't working you can save some time by noting down the raw input format of the controller using my [hid report viewer](https://github.com/ndeadly/MissionControl/files/6950590/hid_report_viewer_mc.0.5.0.zip) application before creating your report.
With no other bluetooth controllers connected, either screenshot or note down the numeric input displayed as you press each button on the controller one-by-one. Do the same for the ±X/Y positions of the analog sticks and post your results here.
placeholder: ex.
01 80 80 80 80 0f 01 00 00 00 00 70 A
01 80 80 80 80 0f 02 00 00 00 00 70 B
01 80 80 80 80 0f 08 00 00 00 00 70 X
01 80 80 80 80 0f 10 00 00 00 00 70 Y
01 80 80 80 80 0f 40 00 00 00 00 70 L
01 80 80 80 80 0f 80 00 00 00 00 70 R
- type: textarea
id: details
attributes:
label: Additional Details
description: Provide any additional details about your controller here. Descriptions, images, links to product website or manual, sync instructions etc.
placeholder: Please enter additional details here.