Circuit network connection for Space platform thrusters
Suggestion:
Let thrusters connect to the circuit network, like Boilers and Land mines did in 2.1.
Use cases:
Set a target speed via signal, thrusters auto-adjust fuel burn to match it.
Read fuel consumption / thrust output.
Turn off thrusters by condition (e.g. low fuel, near destination) to save resources.
Why:
Currently thrusters just burn at max when fuel is available. Circuit control would let platforms manage fuel and speed dynamically instead of being all-or-nothing.
"Circuit network connection for Space platform thrusters"
Moderator: ickputzdirwech
-
SirSmuggler
- Fast Inserter
- Posts: 155
- Joined: Tue May 24, 2016 1:55 pm
- Contact:
Re: "Circuit network connection for Space platform thrusters"
Dynamic speed controll can be achived by controlling pumps between the fuel/oxidizer and the thrusters.
Ofcource it would be easyer to controll the thruster directly, but would it be more fun? A subjective question for sure...
Ofcource it would be easyer to controll the thruster directly, but would it be more fun? A subjective question for sure...
-
Onii-ChanFL
- Burner Inserter
- Posts: 16
- Joined: Thu Oct 24, 2024 1:54 pm
- Contact:
Re: "Circuit network connection for Space platform thrusters"
+1
I think this is a good idea. I also would argue for it, because we now have Boilers, Landmines and so on available so why not Thrusters aswell? We also where able to do the same with boilers with the pumps.
So to stay consistent with the design, I think this should be implemented.
But I think it should also stay consistent with the design how it is implemented. So it should be done like the Boiler was implemented with fitting "Enable if" Part and the Output "Read fuel" boxes. So I wouldn't let it be an input for target speed and the logic is handle by the thurster. that defeats the default logic/design how stuff works with cuircits. I think Enable if and Read Fuel is fine for a thruster. So I can decide with a combinator for example when to turn it of so it wont run out of a fuel type when I want it off and have to fill it from zero again when I enable the pump.
Also I would add for the Heat Exchanger the Output Option "Read fuel" to get the temperature as a signal. Would be then consistent from boiler to heat exchanger in my opinion.
I think this is a good idea. I also would argue for it, because we now have Boilers, Landmines and so on available so why not Thrusters aswell? We also where able to do the same with boilers with the pumps.
So to stay consistent with the design, I think this should be implemented.
But I think it should also stay consistent with the design how it is implemented. So it should be done like the Boiler was implemented with fitting "Enable if" Part and the Output "Read fuel" boxes. So I wouldn't let it be an input for target speed and the logic is handle by the thurster. that defeats the default logic/design how stuff works with cuircits. I think Enable if and Read Fuel is fine for a thruster. So I can decide with a combinator for example when to turn it of so it wont run out of a fuel type when I want it off and have to fill it from zero again when I enable the pump.
Also I would add for the Heat Exchanger the Output Option "Read fuel" to get the temperature as a signal. Would be then consistent from boiler to heat exchanger in my opinion.