View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0031209||Runner||Mac||Public||2019-07-22 14:59||2019-07-23 14:43|
|Reporter||Dan||Assigned To||Russell Kay|
|Priority||High||Severity||C - General||Reproducibility||100%|
|Platform||macOS||OS||Mojave||OS Version||Pro x64|
|Target Version||2.2.4||Fixed in Version|
|Summary||0031209: Mac: gamepad_test_mapping() does not work, pads continue using their original map|
|Description||Using the attached sample you can see that gamepad_test_mapping() does not work on macOS (Mojave and Catalina, VM and YYC). Instead, pads continue using their original mapping, ignoring your changes.|
This is my own test sample and works correctly on Windows, but does not work on macOS.
We have a user reporting this only affects pads which are in the SDL library and so are detected with their name set properly in the runner and if you use an unknown no-name pad then your mappings will work.
|Steps To Reproduce||1. Run the attached project for macOS.|
2. Plug in a pad (if one wasn't already connected), observe the pad details are shown along with the original mapping.
3. Press the spacebar once to write the mapping string to a text file.
4. Open the text file (~/Library/Application Support/com.yoyogames.macyoyorunner/mapFile.txt if VM, ~/Library/Application Support/com.company.game/mapFile.txt if YYC) and edit the string to swap some buttons of your choice around.
5. Close the text editor, saving your changes.
6. Back in the game, press the spacebar again and observe your new mapping will be loaded and set active.
7. Press your gamepad buttons and observe the mapping is still as per the original, not your custom one.
|Additional Information||Spaces have been inserted for readability when drawing the mapping strings to the screen, but are not actually part of the mapping string saved/loaded - doing this will break all mapping support.|
|1.4 Found In|
|2.x Runtime Found In||22.214.171.1244|
|2.x Runtime Verified In|