-
Notifications
You must be signed in to change notification settings - Fork 0
Web Config Mapping Config
Up to 128 mapping can be added. Simply click on +/- buttons to add or remove a mapping. The label used by default are quite generic. You can use the Src label and Dst label to select the actual controller type you are currently mapping from and to. The labels selection is only to help you translate the default BlueRetro labels in something more meaningful. It help making the mapping process easier and has no effect on the config at all and is not saved. You can also consult the mapping reference chart.
The Select Bluetooth device dropbox let you select the active Bluetooth input for which the setting will be saved to. You need to save for each modified device mapping setting.

For each mapping you can configure various options which might or not be used base on what the source and destination end up to be a button or an axis and vice versa.
If all you want to do is a simple button remapping, all you need to touch is the src and dest colums, leave everything else to default value.
- Src: This is the source button/axis on the Bluetooth controller
- Dest: This is the destination button/axis on the wired interface.
- Dest ID: This is the ID of the wired interface.
-
Max: If source & destination is an axis then this is the scaling factor base on the
destination maximum.
If source is a button & destination is an axis then this is the value base on destination maximum that the axis will be set. - Threshold: If source is an axis and destination is a button, this is the threshold requires on the source axis before the button is pressed.
- Deadzone: This is the axis dead zone around reset value.
- Turbo: Turbo function base on the system frame rate.
- Scaling: Various response curve for scaling. (Only Passthrough and Linear available, others not yet implemented)
-
Diagonal: (Not yet implemented)
Diagonal scaling options between joystick type.
BlueRetro turbo feature is probably one of the most over-engineered one around. You got 50 possible options. Not only you can choose the rate but you can also select the duty cycle.

The rate is base on the console controller polling rate which is most of the time 60hz. Using for example "1/2 frames" give a button pulsing at 30Hz, one frame it's pressed and it's unpressed for 1. "2/4 frames" give a button pulsing at 15Hz, 2 frames on, 2 frames off. etc..
As I said you can select the duty cycle. "1/4 frames" still give a button pulsing at 15Hz but it's 1 frames on and 3 frames off. This allow to tweak your turbo to work well in any game.
A lot of games filter out buttons press that are only 1 frames long, so often the "1/X frames" look like they do nothing.
For example on PC-Engine/TG16 original controller the slow turbo is the equivalent of "4/8 frames" and the fast one is "2/4 frames".
You can also set the turbo on a axis, in that case the axis will toggle between it's neutral value (off) and it's current position (on).
You can map the same buttons multiple time with different turbo settings aswell.
-
RE notes
- ESP32 RTOS + Bare Metal: Best of Both Worlds?
- Learning Bluetooth Classic (BR/EDR) with HCI traces
- Xbox One Adaptive controller
- Evolution of SEGA's IO Interface from SG-1000 to Saturn
- Famicom & NES controller shift register: Parallel-in, Serial-out
- SNES 2P & Super Multitap
- PlayStation & PlayStation 2 SPI interface
- 3DO interface
- PC-FX interface
- CD-i interface
- PCE & TG16 interface
- Jaguar Interface
-
Deprecated content