Store Page
Space Engineers
All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Space Engineers

Store Page
Space Engineers >  Workshop > Wicorel's Workshop > Wico Gimbal Rotors > Discussions
Wico Gimbal Rotors
Description Discussions1 Comments169 Change Notes
Sapioit 10 Nov, 2017 @ 4:32am
A better guide! (can be found here)
Hi,

Could you, please, make either a video of, or example ships and put on the workshop, using the minimal amount of everything needed to work? I'm struggling to make a "flying seat" small ship work on a planet, and I think it would explain better than a lot of text, if people could see the config of something already working.

Edit: I finally got it working. I might make a video, soon-ish™.

I would suggest you to change the following, so the script can be easier to use:

- Variable names: Why have GimbalZMinus, GimbalZPlus, GimbalYPlus, GimbalYMinus, GimbalXMinus, GimbalXPlus when you can have GimbalForward (GimbalW), GimbalBackwards (GimbalS), GimbalLeft (GimbalA), GimbalRight(GimbalD), GimbalUp (GimbalSPACE), GimbalDown (GimbalC). This way, people won't have to visit this page EVERY TIME they want to use the script on a new ship, or change a ship.

- Add support for dampening. Currently, a ship won't stay in place, with this script, so one has to have thrusters in every direction, instead of needing enough thrusters for every direction.

- Make a easy-to-follow guide, both in text format, and as a recording, to this page. Here, have an example:

1. Have Whip's Rotor Thruster Manager script installed (requires 1 programmable block and 1 timer)
2. Have Wico Gimbal Rotors script installed (requires another 1 programmable block and another 1 timer) [You could use the same timer for both, but is not recommended]
3. Have the timer used to activate the Wico Gimbal Rotors script have the actions (a) Timer -
Start, (b) Programmable Block - Run
4. Add [GIMBAL] to the name of the Timer used to run Wico Gimbal Rotors script
5. Add to the control block(s) (Remote Control, Control Station, Cockpit, etc.) the name Gimbal Control
6. Add to the rotor's name or custom data, or both, [GIMBAL]
7. Add to the rotor's custom data the angles the rotor has to take to move in each direction it can (X is left-right, Y is up-down, Z is forwards-backwards, Minus is for before the -, Plus is for after the -, so XMinus is left and ZPlus is backwards; I know, those variable names make no sense whatsoever!)
8. Compile the Wico Gimbal Rotors script.
9. Save the game, or make a backup, if you can; if something can go wrong, it's better to be safe, than sorry.

7.Example for a thruster in relation with the Reference:
7.a On top, thruster(s) facing forwards:
[GIMBAL] GimbalZMinus=0 GimbalZPlus=180 GimbalXMinus=270 GimbalXPlus=90 GimbalAutoDampen=true GimbalGravity=true
Last edited by Sapioit; 13 Nov, 2017 @ 6:34am
< >
Showing 1-10 of 10 comments
ronidude 2 Mar, 2018 @ 6:25pm 
this still dosent work for me for some reason :(
#1
Sapioit 4 Mar, 2018 @ 1:16pm 
It have been updated since I made this post.
At the time I posted this, it worked for me. I last edited the post on 13 Nov 2017, and it was last updated on 4 Dec 2017, at the moment I posted this comment.

Edit: Apparently, Minus and Plus seem to have been changed.
So at 7. it would be
[GIMBAL] GimbalZMinus=180 GimbalZPlus=0 GimbalXMinus=90 GimbalXPlus=270 GimbalAutoDampen=true GimbalGravity=true
Last edited by Sapioit; 4 Mar, 2018 @ 1:18pm
#2
ronidude 4 Mar, 2018 @ 1:29pm 
ah ok tnx
#3
ronidude 4 Mar, 2018 @ 1:41pm 
do i need to put this in a programable block?

#4
ronidude 4 Mar, 2018 @ 1:53pm 
Originally posted by Sapioit:
It have been updated since I made this post.
At the time I posted this, it worked for me. I last edited the post on 13 Nov 2017, and it was last updated on 4 Dec 2017, at the moment I posted this comment.

Edit: Apparently, Minus and Plus seem to have been changed.
So at 7. it would be
[GIMBAL] GimbalZMinus=180 GimbalZPlus=0 GimbalXMinus=90 GimbalXPlus=270 GimbalAutoDampen=true GimbalGravity=true
wait so does this go into the programable block or the rotors?
#5
Sapioit 6 Mar, 2018 @ 7:50pm 
The code/script in the programmable block, and that in the rotor's custom data (as is written in point 7).
#6
ronidude 7 Mar, 2018 @ 7:49am 
ok tnx
#7
ronidude 11 Mar, 2018 @ 8:57am 
hey just one more qestion what if i want to control just one rotor but mkae it spin forever eg for turning left and right
#8
Sapioit 12 Mar, 2018 @ 10:38am 
No idea if it's possible. That's how I initially thought something like this would work, but it seems that the way it's currently working is more efficient.
#9
ronidude 12 Mar, 2018 @ 2:52pm 
Originally posted by Sapioit:
No idea if it's possible. That's how I initially thought something like this would work, but it seems that the way it's currently working is more efficient.
mmmk
#10
< >
Showing 1-10 of 10 comments
Per page: 1530 50