Mekanism Generators

Mekanism Generators

97M Downloads

Elite Infusing Factory cannot keep up with the infusing reagent.

LordHelmchen opened this issue · 5 comments

commented

Issue description

With speed upgrades the Elite Infusing Factory uses the stored infusing material (e.g. tin) faster than it can refill it.
I suppose the transformation from the input slot into the internal buffer should scale with the speed upgrade, too.

Steps to reproduce

Build an Elite Infusing Factory with 8 Energy and 8 Speed Upgrades.
Keep all material input slots filled at all times.
I used the recipe for Neutral steel of the Seventh degree from Project Ozone 3: 200 tin units are infusing 3 6th degree steel Ingots into one new Ingot of 7th degree steel.
Watch the internal buffer drain faster than it can refill.

Minecraft version

1.15.x or earlier (No longer being developed)

Forge version

8.0.99.99 ?

Mekanism version

Older

Other relevant versions

Mekanism 1.12.2-9.8.3.390

If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)

No response

commented

elite infusing factory_video.zip
I don't know what enriched things, you are referring to.
I suppose it is part the pack authors deal, because 200 units of infusing material is a lot.

commented

Can you send a short video of the issue ? Do you use enriched things ?

commented

Enriched coal as example
1 Coal → Enrichment Chamber → Enriched Coal

Enriched items are better, for example:
1 Enriched Coal → 8 Coal in the infuser
1 Enriched Redstone → 8 Redstone in the infuser
And so on

Enriched:
image

commented

It's named compressed here. I just checked, it works with redstone, coal/carbon, obsidian and diamond in this version, but tin is missing.
I'll report it to the project ozone issues, thank you.

commented

Compressed/Enriched Tin didn't exist back in 1.12. But my best guess is either it is just due to that or potentially the rates of the recipes got adjusted not really sure. Going ahead and closing this though as I don't believe this is an issue in 1.16 and we aren't developing for 1.12 anymore.