Ask for a bedrock flywheel?If it will lead to stable/consistent power output rather than the fluctuations they currently experience, then yes.
Ask for a bedrock flywheel?If it will lead to stable/consistent power output rather than the fluctuations they currently experience, then yes.
Very much this. If it's just to add difficulty/add another step to the process, then I vote no. But if there is an advantage to using lubricant, then I will vote yes.If it will lead to stable/consistent power output rather than the fluctuations they currently experience, then yes.
Exactly. It would make sense too; without lubricant you can't expect a machine to function efficiently. But add some, and it should drastically improve the performance.Very much this. If it's just to add difficulty/add another step to the process, then I vote no. But if there is an advantage to using lubricant, then I will vote yes.
The two ideas are not really connected at allIf it will lead to stable/consistent power output rather than the fluctuations they currently experience, then yes.
I'll be honest: from a programming standpoint, flywheels freak me out. I wouldn't want to code one, as a small mistake can create all kinds of exploits, and there's a million places you can screw with one.But, but, bedrock flywheels.
I'm not anti-flywheel either, the rumbling sound they make is pretty cool. Honestly I have to give Reika props for the audio in RoC/ReC; it makes a factory/power plant actually *SOUND* like one unlike most mods out there.I'll be honest: from a programming standpoint, flywheels freak me out. I wouldn't want to code one, as a small mistake can create all kinds of exploits, and there's a million places you can screw with one.
Therefore I never recommend implementing them
having said THAT: yeah, sounds coo
But, but, bedrock flywheels.
Flywheels have been the source of numerous exploits in the past, and for that reason I do not at all want to go near them.I'll be honest: from a programming standpoint, flywheels freak me out. I wouldn't want to code one, as a small mistake can create all kinds of exploits, and there's a million places you can screw with one.
Therefore I never recommend implementing them
having said THAT: yeah, sounds coo
The two ideas are not really connected at all
Having said that, I'd definitely also love to see the turbine generate stable power similar to the HP, but I file it under "whatever."
The variability in turbine torque output is a function of how it works "behind the scenes". This is not something I put in deliberately, and it is something that will never change, lubricant or not.If it will lead to stable/consistent power output rather than the fluctuations they currently experience, then yes.
Flywheels have been the source of numerous exploits in the past, and for that reason I do not at all want to go near them.
Vindication.
Curious: Is there such a thing as a gizmo (non-electronics) that will only output a constant power if its minimum power requirement is met?
Say I set it to 900MW; if the turbine consistently provides > 900MW(fluctuating), and I'm willing to accept lossiness, could I get constant 900MW?
Or have I simply described another flywheel?
After a quick web search there exists a device called a torque limiter/overload clutch to limit torque to a set level to avoid damage to attached devices, maybe that would work?Vindication.
Curious: Is there such a thing as a gizmo (non-electronics) that will only output a constant power if its minimum power requirement is met?
Say I set it to 900MW; if the turbine consistently provides > 900MW(fluctuating), and I'm willing to accept lossiness, could I get constant 900MW?
Or have I simply described another flywheel?
Such devices are possible, but you would be losing a rather large amount of power.Vindication.
Curious: Is there such a thing as a gizmo (non-electronics) that will only output a constant power if its minimum power requirement is met?
Say I set it to 900MW; if the turbine consistently provides > 900MW(fluctuating), and I'm willing to accept lossiness, could I get constant 900MW?
Or have I simply described another flywheel?
Yep. Probably annoying to implement as well.Such devices are possible, but you would be losing a rather large amount of power.
Because constantly updating the power input forces ElectriCraft wires to constantly remap the network. This has significant computational load.There could be many kinds of torque limiter.
That said, I think you can just dump all the power into Electricraft batteries and call it constant output. They have variable input, fixed output. Yes you might have issues with a complex net of wiring, but if you connect straight into the battery for each turbine, I don't see why that would be an issue.
There could be many kinds of torque limiter.
That said, I think you can just dump all the power into Electricraft batteries and call it constant output. They have variable input, fixed output. Yes you might have issues with a complex net of wiring, but if you connect straight into the battery for each turbine, I don't see why that would be an issue.
Because constantly updating the power input forces ElectriCraft wires to constantly remap the network. This has significant computational load.
This is not possible. The network caches all point voltages and currents to help performance, and any time the power input changes, those caches must be recalculated. There is no way around this.In the interests of performance, would you be willing to alter the mechanic so that power-input changes raise a "needs-remapping" flag, and only do an actual re-map once per X seconds (1 or whatever)
Because constantly updating the power input forces ElectriCraft wires to constantly remap the network. This has significant computational load.
This is not possible. The network caches all point voltages and currents to help performance, and any time the power input changes, those caches must be recalculated. There is no way around this.