-
Notifications
You must be signed in to change notification settings - Fork 38
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
POS 2% job material savings are applied to Station builds while they shouldn't #57
Comments
This is working as expected. The ME value of 2 on a Void L Blueprint for one run is 15 units of morphite. As you get more runs, the ME value affects the total numbers and at 10, it's 14.7 per run, or 147. For 100, it calculates 10 runs of 10 run bpcs, and you get 1470. The POS numbers are 1450, which applies the extra 2%. |
Ok looks my reproduction example was having me getting wrong assumptions. However take this example find the screenshot attached. when going with the shopping list one will run short of the following PI materials EIPH screenshot is attached as well as parts of wallet transaction log showing that extra materials had to be bought following EIPH's calculation. So while trying to find a simple example the "float" habbit of material calc's were a bad coincidence |
I had a chance to look at this and I don't see the problem. All the numbers in the game using those settings say you need 148 Wetware Mainframes. Are you building them separately or just using one BP? IPH assumes you only have 1 bp to use. I'm not sure why you would need 151 Wetware mainframes. I see no setup that would produce those requirements. Let me know if you are still having an issue but I'm unable to reproduce this issue. |
In Blueprints tab: select a BPO i.e. "Void L Blueprint".
Total Runs: 1 => 15 Morphite used.
Total Runs: 100 => 1470 Morphite used.
Facility->Activity: Manufacturing
Facility Type: Station
Location: doesn't matter
so from the looks a 2% material reduction is applied.
EIPH Version: 3.3.6009.16436
The text was updated successfully, but these errors were encountered: