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

Space Engineers

Store Page
Space Engineers >  Workshop > Whiplash141's Workshop > Whip's Subgrid Thruster Manager > Discussions
Whip's Subgrid Thruster Manager
Description Discussions20 Comments1506 Change Notes
Stop moving I need the Cbills 16 Jan, 2020 @ 12:24pm
Odd behaviour when controlling across connector
Quick question regarding WSTM v40

I've created a jumpdrive module that is swapped between craft via a connector.
The connecting craft have programmable blocks running WSTM
The jump module does not have any programmable blocks

The jump module has a control seat so it can be flown on it's own as required.

All works well when connected. The jump module's extra thrusters work as expected.

When the docked controlling craft disconnects, the jump module can no longer be
piloted. Zero thruster control on the jump module itself.

Deleting the thrusters and putting new ones on - no problem, control restored.

Dock again, thrust works from the control "Reference" cockpit. Undock and the
jump module can no longer be controlled from the seat on the jump module.

What the heck am i missing?

< >
Showing 1-2 of 2 comments
Virt 25 Apr, 2020 @ 10:43am 
Exact same problem here, only solution seems to be to replace the thrusters. Any connected ships seem to lose their thruster control completely after being disconnected from the main grid, even after the prog block has been turned off and/or the script stopped.
Not sure which version but it was the latest at the time of posting this.
Have not tried to replicate in single player/vanilla.
Running Hulls thruster efficiency mod (+ others but this one seems like it would be the biggest suspect)
Observed with hydrogen thrusters only, have not tested with other thruster types.
Honestly suspecting mods are doing this but thought I would post incase of an actual issue.
#1
Whiplash141  [developer] 15 May, 2020 @ 9:11pm 
Originally posted by Stop moving I need the Cbills:
Quick question regarding WSTM v40

I've created a jumpdrive module that is swapped between craft via a connector.
The connecting craft have programmable blocks running WSTM
The jump module does not have any programmable blocks

The jump module has a control seat so it can be flown on it's own as required.

All works well when connected. The jump module's extra thrusters work as expected.

When the docked controlling craft disconnects, the jump module can no longer be
piloted. Zero thruster control on the jump module itself.

Deleting the thrusters and putting new ones on - no problem, control restored.

Dock again, thrust works from the control "Reference" cockpit. Undock and the
jump module can no longer be controlled from the seat on the jump module.

What the heck am i missing?

Firstly, I have a pinned Bug Reports discussion which I check frequently. https://steamhost.cn/steamcommunity_com/workshop/filedetails/discussion/757123653/350540973993645762/

If you spawn your own threads for issues, I will not see them because I do not get notified.

-----

This script only controls thrust over connectors when "detectBlocksOverConnectors" is set to true so I'm assuming that has been manually enabled.

To fix the issue you listed, simply reset the thrust override to zero by right clicking on the thrust override slider. The script sets the override of all subgrid thrust to a very tiny number to prevent them from dampening motion when they shouldn't. If you disconnect a ship that was previously having its thrusters controlled by this script, you will need to manually get rid of this or the thrust will not respond to your input commands.
#2
< >
Showing 1-2 of 2 comments
Per page: 1530 50