I don't know if this is a bug or a feature but the translation controls are paired with different inputs.
PC
Pitch, translate forward
Roll, translate Up
Yaw, translate Right
Mobile(IOS)
Pitch, translate up
Roll, translate right
Yaw (left stick all axes) translate forward
Hmmmm.
It's not a huge deal but something to take into account if using translation inputs in a script. I'm tending to use them for jobs other than RCS duties, when RCS is non applicable the inputs are handy as they don't affect anything else. What seems like a logical layout on mobile won't, ahem, translate to PC. Vice versa.
There are no separate bindings for translation. I made a test model with Vizzy using translation inputs to activate beacons alongside RCS nozzles. Just to make sure nothing odd happening from the Vizzy end.
Maybe it's just something to do with the joysticks, that may be configurable in the key bindings
I made a suggestion. For anyone slightly bothered by this please check it out 🙂