You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tried a bunch of different versions of MFFS, and all of them have them same problem.
Once the Fortron Capacitor is turned on, the energy is drained from Coercion Deriver to the point where nothing happens. The FC seems to be devouring energy at an alarming rate, even when hooked up to a Creative Energy Cell, so I know the amount of energy isn't the issue.
The FC just builds to like...160L, then vanishes. =( I seen on a previous post back in JAN that this will be fixed, but haven't seen any change logs or anything? Are they any updates?
The text was updated successfully, but these errors were encountered:
The Fortron Capacitor requires energy and will consume energy whenever it is turned on. There is a toggle for the base amount of energy required for it to run. When modules are added it will consume more energy to run as long as it is turned on.
Therefore whenever their is available energy, the capacitor will transfer the energy between containers. This is the default usage of the Capacitor and there was plans to change the concept. Unfortunately
I have not had the time to think up a new concept that works without changing too many things. It is a open-source project so anyone can pickup where others left off.
Running 1.7.10
I've tried a bunch of different versions of MFFS, and all of them have them same problem.
Once the Fortron Capacitor is turned on, the energy is drained from Coercion Deriver to the point where nothing happens. The FC seems to be devouring energy at an alarming rate, even when hooked up to a Creative Energy Cell, so I know the amount of energy isn't the issue.
The FC just builds to like...160L, then vanishes. =( I seen on a previous post back in JAN that this will be fixed, but haven't seen any change logs or anything? Are they any updates?
The text was updated successfully, but these errors were encountered: