IAS Keybind Resetting to "Unknown"

I haven’t touched Studio in a week so I’m not sure when this issue started happening. Basically; my old IAS MouseButton keycodes stopped working in the live branch, so I checked Studio in order to debug.

The InputBindings that were binded to mouse inputs were set to Unknown and setting them back to their original values(MouseButtonLeft) and publishing still didn’t apply any changes although a part’s position updated normally. Even saving and relaunching the experience reverted the InputBindings to Unknown

Expected behavior

I’ve used IAS since the Client Beta and everything worked fine until now. It sets the MouseInputs to Unknown in every experience. I haven’t even touched the bindings and they were reverted to Unknown.

A private message is associated with this bug report

2 Likes

I got the exact same issue yesterday after not opening the place for a month or so. And it was MouseButtonLeft keybind.

1 Like

Hi,

Thanks for the report. This is a known issue with the Input Action System, see this post [Client Beta] Input Action System is now available to publish in experiences! - #137 by runitbackrolfo. Affected developers will need to re-set the KeyCode and save/publish experiences. We are very sorry about the inconvenience.

Regarding the other issue about the new InputBinding’s KeyCode not saving correctly, we couldn’t reproduce this issue. Can you make sure that you are on the latest version of Roblox Studio (version 696) and have no conflicting plugins, then restarting your computer / Studio and save / publish again?

Updating to version 697.x has fixed the KeyCode(MouseButtonLeft specifically!) disappearance, now the KeyCode is saved correctly and doesn’t revert to Unknown.

1 Like

Great to hear that it’s working now, sorry again about the inconvenience this caused. I’m going to close this report, thanks for updating us!

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.