-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Capacitor warfare resist on cap batteries messes with cap stability calculation #537
Comments
Please post eft version of fit, and ill take a look into it
|
Fit from screenshot:
Fit that is projecting onto it:
|
Well fuck. It would seem that This was a case of bad function naming and lack of documentation. I think that this is a sufficient error to warrant a new release. I'll look into getting that sorted tomorrow. |
Glad i found it relatively fast and decided to make a github account to report it then. Thanks for looking into it so fast! |
Hello,
i've just pulled the march release and worked on my guardian fit when i noticed that adding a cap battery seems to mess with the capacitor stability calculation. I think this bug was introduced with version 1.2.0. I've repulled 1.19.2 where the fit still worked out fine and compared. Here's the same fit in both versions as screenshot
.
I'm just eyeballing but does the -25% neut efficiency of the cap battery maybe get calculated as -25% cap recharge?
Cheers
The text was updated successfully, but these errors were encountered: