Vizzy translate command won't work.

@AndrewGarrison Aha so I am not the only one then:) I look forward to the next update! thanks for the help.

Ah, I thought you were on the beta branch on Steam, but you were saying you were on the beta branch on Android. This will be fixed in the next update. It's currently fixed in the beta we have going on Steam.

@AndrewGarrison I play on Android (0.8.402) . Does it make a difference on how crafts respond to commands?

@AndrewGarrison No, I'm using 0.8.402 which is what google play gives me.

@404notfound91 I just realized that I forgot to ask if you were using the latest beta. (Version 0.9.100.0)?

@AndrewGarrison Well that is what I wanted it to do. mine just fires for a fraction of a second. Maybe It's just me ㄟ(▔ ,▔)ㄏ Thank you very much btw, best space game I've ever played.

The program appears to be working for me. It waits for me to input translate forward, zeroizes the input, waits one second, and then resets the translate forward input back to 1 and the RCS appear to be firing correctly for me.

@AndrewGarrison Here is the craft with program in it hopefully:)
https://www.simplerockets.com/c/11auku/Vizzy-translation-mode-test-craft

@AndrewGarrison It is still the test craft. I tested the 2different rcs thrusters. I will try to upload the craft with the program on it.

Can you upload the craft with the program that demonstrates the issue? Or is it the same craft that was part of this initial bug report?

@AndrewGarrison I tried it again with translation mode on first and then activating the program. Rcs did fire but only for less than half a second. my test program is: wait until input slider 1, then set translate right to 1.

This will be improved in the next beta and I've also added an instruction so that you can enable/disable Translation Mode from Vizzy.

@AndrewGarrison Ah thank you very much. I will try it again.

Dev Notes: The RCS does not respond to translate forward unless the craft is in translational mode, but once it is in translational mode it wipes out the currently set input from Vizzy.

This is just a test rocket btw, I was trying to use this command on other rockets, that was how I found out this issue.