Having bridge pipe connected at all makes entire LP network malfunction

[tornewuff]

I have a large existing logistics pipe network and a brand new AE system.

Connecting the bridge pipe up to AE seems to cause the entire LP network to stop working properly:

• requesting items from a logistics table just does nothing, the items never come
• requesting crafting seems to randomly hang at different points with items just not being sent to their destinations

None of these requests involve the AE system in any way - the bridge is not a default route, there are no crafting recipes in the AE system, and no items required by the requests are stored in AE. If I look at the routing info for the bridge pipe with the pipe manager, it has pending requests listed for some of the items even though it shouldn't be involved, and it's putting out sparkles like it's active. As soon as I break the bridge pipe all the pending requests for crafting in LP happen immediately and everything starts working again.

I'm not sure how to debug this - any ideas?

This is using the FTB Interactions 2.0.10 pack which contains: Logistics Bridge 1.3.14 Logistics Pipes 0.10.3.62 AE2 rv6-stable-7 Forge 14.23.5.2847

[md5i]

I am experiencing this as well. Identical pack. Though it's not the bridge pipe by itself. It appears to require the bridge pipe being connected to an AE Bridge.

[KorewaLidesu]

Recommend do not using Bridge because its buggy right now

• Reason why: something request a non-exist item from the Bridge (in AE2 system) cause the Bridge to stop (waiting for item appear on AE2 network)
• Solution: using ME Interface with Logistic pipe instead