Ion thrusters switch on timer but do not produce thrust
During some testing I discovered an issue where ion thrusters on override, switched on and off in sequence by a set of timers, do not actually produce any thrust. They only briefly produce thrust when the grid is pasted, or when the player messes with the override slider while the thruster is switched on, or when the grid is modified, like, if a block is added.
(Blueprint attached.)
This grid is supposed to thrust individually for two seconds each in one of the for main directions:
But it doesn't. There is no thrust and no blue flame effect.
All four thrusters are set to non-zero override, but switched off, and the timers are set up to turn them on and off sequentially. Notably, when the thrusters are watched in the terminal, their On/Off switch can be observed to turn on and off as dictated by the respective timers.
Tested in vanilla world, no mods, SE 1.201.013.
It does not appear to be dependent on the grid's "Inertial Dampener" setting.
I tested it with a similar system with hydrogen thrusters where it worked as expected.
I have the same bug
Hello, Andersenman!
After investigation, it seems that it is a duplicate of this thread with a similar issue.
Since the shared thread is still in the "Reported awaiting fix" state, kindly wait until the thread switches to "Solved" status with the comment confirming the fix and on what version it will come.
We are closing this thread as a "Duplicate" for now but kindly keep an eye on the shared thread for any new information, comments, and possible fixes coming.
Kind Regards,
Keen Software House: QA Department
Hello, Andersenman!
After investigation, it seems that it is a duplicate of this thread with a similar issue.
Since the shared thread is still in the "Reported awaiting fix" state, kindly wait until the thread switches to "Solved" status with the comment confirming the fix and on what version it will come.
We are closing this thread as a "Duplicate" for now but kindly keep an eye on the shared thread for any new information, comments, and possible fixes coming.
Kind Regards,
Keen Software House: QA Department
Hello, Andersenman!
After investigation, it seems that it is a duplicate of this thread with a similar issue.
Since the shared thread is still in the "Reported awaiting fix" state, kindly wait until the thread switches to "Solved" status with the comment confirming the fix and on what version it will come.
We are closing this thread as a "Duplicate" for now but kindly keep an eye on the shared thread for any new information, comments, and possible fixes coming.
Kind Regards,
Keen Software House: QA Department
Hello, Andersenman!
After investigation, it seems that it is a duplicate of this thread with a similar issue.
Since the shared thread is still in the "Reported awaiting fix" state, kindly wait until the thread switches to "Solved" status with the comment confirming the fix and on what version it will come.
We are closing this thread as a "Duplicate" for now but kindly keep an eye on the shared thread for any new information, comments, and possible fixes coming.
Kind Regards,
Keen Software House: QA Department
Replies have been locked on this page!