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

Space Engineers

Store Page
Space Engineers >  Workshop > Vermillion's Workshop > Vector Thrust 2 [old] > Discussions
Vector Thrust 2 [old]
Description Discussions18 Comments1282 Change Notes
Rubezagel 24 Apr, 2020 @ 5:12am
Issues with standby on docked ships
Got some weird problems on my dedicated server related to docking. When in standby mode, certain actions (locking and unlocking the connector, exiting the cockpit, also upon joining the server), will cause thrusters zu turn on, rotors to start spinning (to the point were the blow up sometimes), possibly more weird behaviour, hard to keep up. All the while, the script remains in standby mode.

Couldn't do too much testing for now since its a surival world. What I did try though: I disconnected the docking area (connector) from the rest of my base grid. Not a 100% sure, but that seemed to have solved the problem. I honestely have no idea what could be causing that, I turned off all programmable blocks in my base.
I am using unique tags for VT by the way, as well as high torque rotors with high values set.


For now, I just worked around by not using the standby mode at all, I am using a group to turn off the programmable block and thrusters all together and I modified the script settings to boot directly to jetpack mode. But its less than ideal and kind of suspectible to user error, and unnecessarily complicated to set up right.
< >
Showing 1-4 of 4 comments
Rubezagel 24 Apr, 2020 @ 7:00am 
so I downloaded the save to try it locally. Had less problems there - entering/exiting cockpit didn't cause thrusters to go on all the time, but still rarely it did. (Un)locking connectors still did. Disconnecting the coking area from the bigger grid helped, like on the server, but still not a 100%.

But: I found out that setting "controlModule" to false in the script, as well as disabling "read all input" on the programmable block itself, seemed to eleminate the problem all together!
Its noticable, that with control module enabled, the spinning symbol (\|/)changes whenever I move there is some input, like moving the mouse.Of course, ideally I'd prefer to keep control module functionality.

Since the misbehaviour could be somehow related to computing timeing (worse on servers, maybe related to overall grid size/amount of stuff on it?), perhaps a small delay within the script could be an easy fix?
#1
Majca 31 May, 2020 @ 1:53pm 
I do have the same issue on my private server.
#2
Miguel 28 Jul, 2020 @ 6:21am 
I can confirm that the problem still exists. @Raegenhere, how did you modify to temporarily solve this?
#3
WynterPaladin 25 May, 2021 @ 7:05pm 
Still an issue. Was having a ton of issues, so set up a timer block that would:
1) Connect connector
2) Engage Rotor Lock
3) Reset Rotor Velocity to 0 (needed for lock to engage)
4) Power off all Thrusters
5) Put script in standby (if it wasn't already which it usually was)

Then I log off the dedicated server, and when I come back, the ship has ripped itself in half and taken the connector with it. Even though the thrusters were off, the script was in standby, and the rotors were locked.
#4
< >
Showing 1-4 of 4 comments
Per page: 1530 50