Mass Fabricator Amplifier (Problems?)

[Physicist]

When I put scrap or scrap boxes into my Mass Fabricator (DW20 pack, so no GT), I don't always see the Amplifier details pop up, and I don't always see an apparent jump in UU production. It sure burns through the scrap(boxes), but how can I be sure it's working if it's not displaying the word "Amplifier"? Are there known issues or circumstances where a massfab eats scrap and boxes without providing benefit?

I suppose it's possible that I don't see the jump in UU production because it just consumes EU slower while eating scrap, but I have seen HUGE jumps in % complete when throwing scrap in, possibly due to less than full power input. That would explain it, but I'm hoping for some confirmation if that's the case.

Extra information:

Spoiler

Also, I have seen the mass fab stop eating scrap, and sit there with surplus and say that it DOES have the amplifer while waiting for more juice to produce UU so I know it works at least sometimes; I can't seem to always make that happen, but perhaps it requires slower income, like directly from my reactor (3x3 single uranium cells, so less than the MFSU can output).

I have my Mass Fabricator connected to HV cables running from my MFSU. If I really want UU, I just let the power flow, but if I'm offline or busy elsewhere, I connect redstone from my MFSU to only make the mass fab run when the MFSU is completely full (emit when full > NOT gate > mass fab). It studders during production, and I suspect some EU is getting lost due to a full MFSU waiting for the single tick NOT gate to toggle, but I'm willing to live with that for now.

 

[Omicron]

The version of IC2 in the pack is bugged. The mass fab always runs at scrap speed even without scrap, and adding scrap doesn't change anything.

This is because IC2 classic is no longer being developed. There's a new branch called IC2 Experimental for Minecraft 1.6.x, which is actively being developed. You will no longer see bugfixes or version updates for the classic branch.

 

[Physicist]

It's too bad about the bug. From a technical standpoint, if they write bugfix code for the future versions, can't those snippets of code (in many cases, surely not all) be copy-pasted into versions for MC still getting lots of use? (I had been pondering mDiyo's resistance to bugfixing the Tinker's Construct 1.5 release, but it seems like this is a similar situation.)

 

[KhrFreak]

It's too bad about the bug. From a technical standpoint, if they write bugfix code for the future versions, can't those snippets of code (in many cases, surely not all) be copy-pasted into versions for MC still getting lots of use? (I had been pondering mDiyo's resistance to bugfixing the Tinker's Construct 1.5 release, but it seems like this is a similar situation.)

Not if those snippets of code rely on things added to forge/Vanilla thats only for say 1.6

 

[Physicist]

Not if those snippets of code rely on things added to forge/Vanilla thats only for say 1.6

No doubt. I'm sure that the change creating Resource Packs really impacts overall mod structure and makes version control a huge asspain. My thinking was that little quirks like Tinker's Constructs item-as-entity misplacement (I've lost crazy good tools because I couldn't see where they landed) and detecting scrap would possibly be forge/MC version irrelevant snippets.

 

[twisto51]

The version in unleashed 1.1.3 is bugged, the version in 1.1.4 is even more bugged. Not really good material to convince somebody that they just need bug-fixing to get 'better'. In this particular case the fix is worse than the problem.