TE tesseracts have broken LP in another way. In conjunction with BC removing the config for pipe.maxitems, TE tesseracts now eject items super-slowly.

This will invariably lead to exploded pipes on the tesseract exit side on large orders, or orders with a moderate to large number of sub-item iterations, as when the items appear on the other side of the tesseract, they are slowed to a crawl -- which leads to a ton of items being in the pipe at one time.

Even a moderate order, like ordering a stack of BC tanks, generally explodes pipes when a provider MK2 is used.

I'll check it out soon. have to wait for 'patch day' :D

On Mon, Feb 3, 2014 at 4:36 PM, davboecki [email protected] wrote:

Could you check if the newest commit did the trick?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/259#issuecomment-34003030
.

Could you check if the newest commit did the trick?

Tesseracts shouldn't rate limit all that much, they should be able to send a stack per tick. Try placing the tesseract directly onto an inventory?

The issue is not the tesseract throttle, it's the tesseract resetting the
speed. And connecting the tesseract to an inventory defeats the purpose of
having l.p. being able to network through one.

This message was sent via phone. Please excuse any typos, as my phone loves
to 'autocorrect' to the wrong words.
On Jan 30, 2014 1:06 PM, "Alex Wilde" [email protected] wrote:

Tesseracts shouldn't rate limit all that much, they should be able to send
a stack per tick. Try placing the tesseract directly onto an inventory?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/259#issuecomment-33714997
.

LP routed items shoudln't trigger BC's exploding pipes anymore.