Hello all, we’re looking to standardize the code paths for the input action system which means removing place files from being opted out of some sinking fixes. We originally added this option to fix issues with gamepad buttons clashing with our PlayerScript jump and movement bindings and have since released a new three phase rollout workspace.PlayerScriptsUseInputActionSystem to convert our movement to IAS. More details here. We hope this means that your places will work automatically when workspace.PlayerScriptsUseInputActionSystem = Enabled and opted back into standard Roblox. Can you please test your games with this new property enabled in a new placeID? We will prioritize any issues found and can hopefully start opting your placeIDs back into our sinking fix in two weeks, by August 14.
@Vyntrick @SamAntispam @OperatorsManual @HadokeenW @12KaiJie333 @Trainmaster2341 @Vlado_RBLX @Festivereinhard2 @DevAwesomely @DanzLua @Novanixator @lxDumbo @kolhli @71_8e
Hiya!
Yes, this property seems to fix any issues with clashing inputs in my testing branch place (which wasn’t opted in). I would like to ask one thing however: Is there a way to prevent the default Roblox sounds from appearing in the character model? The old method of creating a local script called “RbxCharacterSounds” and placing it in StarterPlayerScripts seems to no longer function with this property enabled, as the local script gets overwritten by the Roblox made script. Maybe I’m doing something wrong? Any help is appreciated!
On a new placeid, I can confirm the MouseWheel is now present again according to the bug report I made on the issue.
My game experiences no issues with the input action system and all keybinds I’d expect to work function as they should. I’ve already been testing this a lot since the addition of the workspace toggle, so I think my experience is pretty much ready to have the filters reverted, since I do intend for an update to drop in august (the below video + some more that is currently missing)
Thank you, your places are being opted back in. Please give it ~an hour to propogate.
Thanks for looking into it! We’re working on some new APIs for sound, but until they’re released, our current recommended flow is to fork PlayerScripts with the CreateDefaultPlayerModule = false which should prevent the RbxCharacterSounds from being injected. I’m curious what your use cases for disabling default sounds are. We could try and design some new PlayerScript APIs so forking the sound scripts may not be necessary.
Hi!
I will be sure to try this in my testing branch, but my purpose for disabling the default Roblox Character sounds is for the fact my game has a custom footstep and jump sound system. The audio for footsteps is synced via Animation Events on the character’s custom walk/run animation, which contains a number that gets sent to the server to play the respective footstep audio!
Edit: I couldn’t find out what you meant by CreateDefaultPlayerModule = false (I probably didn’t look around enough), so I opted to create a LocalScript in StarterPlayerScripts that waits for RbxCharacterSounds to be created to then destroy it.
I can confirm that I no longer have any issues with the Input Action System. Everything works as it should.
It’s fine now it works perfectly, good job
Thanks for the feedback! There’s a new property under StarterPlayer called CreateDefaultPlayerModule. Here’s the docs.
Can IAS get support for gestures and gyroscope inputs? Currently one has to use UserInputService for these making things harder to implement, rather than if IAS just supported them.
Everything has been great since the place filter has been removed on my experience, however there is one more issue that is related to input but not explicitly the Input Action System (or maybe it is?)
My game makes use of UIDragDetectors, especially for volume sliders. Gamepad users cannot interact with UIDragDetectors at all in my experience, forcing me to program additional buttons they have to spam just to do what Mobile & PC players could do.
Here is my bug report on the issue. I’m not sure if this is fully related to Input Action System since it’s been known to conflict with inputs, and whatever manages the input processing for UIDragDetectors should definitely be looked into.
Thank you for any help you can provide!