Applied Energistics

[PhilHibbs]

Lets say you have 1 blank pattern, and the level emitter is set to 2. That turn on the export bus, which says, I need to put a blank pattern in here. It looks in the network to see if it already has one, finds one in the storage bus, grabs that one and exports it. Infinite loop.

 

[AlanEsh]

But can't you set the storage bus to "read only" ? I thought that was an option.

 

[SmokeLuvr1971]

I do not see them. I know that's why it isn't working correctly [ie - the emitter sees no on-hand inventory on the network]. Strange thing is, if I set the export bus to always craft, it will stop at 64 instead of continuing to craft...so somewhere along the way, something in the network is aware of the encoder's inventory space.

 

[AlanEsh]

I think the Encoder will only accept a stack, and since the export bus is on the Encoder it stops when full.

 

[budge]

I'm pretty sure that the bottom of the encoder is specifically the output slot, so a storage bus there would only see encoded patterns. Try putting it on the side.

Also, as PhilHibbs said, I think you're setting up an infinite loop. Also think about setting the export bus to "craft only".

 

[PhilHibbs]

But can't you set the storage bus to "read only" ? I thought that was an option.

I suspect that AE just avoids the problem by refusing to allow a storage bus on an interface that is part of the same network.

 

[SmokeLuvr1971]

I suspect that AE just avoids the problem by refusing to allow a storage bus on an interface that is part of the same network.

By interface, do you mean the pattern encoder block? If so, that block is specifically not part of any network and a storage bus should work fine on it.

 

[Niels Henriksen]

But can't you set the storage bus to "read only" ? I thought that was an option.

You can set it to read/write, read only and write only. I had a problem where I was wondering where my 12k iron ingot went until I saw that the storage bus on the DSU was set to "write only".

 

[PhilHibbs]

By interface, do you mean the pattern encoder block? If so, that block is specifically not part of any network and a storage bus should work fine on it.

No, the ME Interface.

 

[SmokeLuvr1971]

Why is it I can never find specific information to address the problems I face with mods? I can't be the only one running into these things...

Anyway, new info I didn't see anywhere else:
If importing into your network directly from an Item Tesseract, use a ME Interface to connect with the tesseract. For some reason [prob because item tesseract isn't an inventory item] an import bus does not work.

 

[PhilHibbs]

If importing into your network directly from an Item Tesseract, use a ME Interface to connect with the tesseract. For some reason [prob because item tesseract isn't an inventory item] an import bus does not work.

That's right, tesseracts don't have inventories that are accessible. They have an inventory that can be inserted into, but not one that can be extracted from.
I think it would be a good idea to add a 1-slot inventory to an Import Bus, just to get around this problem. However that might mess up other things, for instance pipes would then connect to it that did not connect before.

 

[KingTriaxx]

Query: Why does it matter how many Blank Patterns are in the encoder? It only holds one stack of blanks, and I'm hard pressed to think why you'd use more than one stack of them at a time. And since the encoder is the only place you'd use them...

I'm not sure why you'd want an inventory on an import bus. It's actually a step beyond the interface, which has an interface and does what you'd need the inventory for.

 

[PhilHibbs]

I'm not sure why you'd want an inventory on an import bus. It's actually a step beyond the interface, which has an interface and does what you'd need the inventory for.

Only for consistency. If you've got a load of import buses importing things, and then you've got a big blocky interface next to a tesseract that essentially does the same thing as all the other import buses, it just looks out of place. I suppose I could just jam in a chest in between them.

 

[KingTriaxx]

That... seems odd. Why would you leave the Tesseract sitting out in the open? Or more, why not just have it sitting on top of the interface?

 

[budge]

I thought I saw a changelog once that said import buses used more energy to import than interfaces. With that in mind I generally favor the interface for importing.

Man, do I like IC2's ejector upgrades. Now my on-demand crafting area has just one interface for every machine, which beats even Thermal Expansion setups of weeks past!

 

[AlanEsh]

That's right, tesseracts don't have inventories that are accessible. They have an inventory that can be inserted into, but not one that can be extracted from.
I think it would be a good idea to add a 1-slot inventory to an Import Bus, just to get around this problem. However that might mess up other things, for instance pipes would then connect to it that did not connect before.

Hrm, I have never felt like there was a problem here... I mean they are different tools for different jobs. If you want to pull from an inventory, slap on the Import Bus. If you need to catch the ejected items from machines, pipes, and systems, there is the Interface. Tesseracts are not and (IMO) should not be storage blocks, so they're basically pipes, and thus you catch their output with an interface. Anything else makes less sense to me. Maybe an Ender Chest should be used rather than a Tesseract if you need an inventory to pull from.

 

[SmokeLuvr1971]

Here's another strange thing about AE...how do you reset a preconfigured basic bus, or any bus with "used" label? I've got 2 basic export buses sitting in my inventory that I've previously sorta-used [they went from items to blocks but were never told to move any items] that I'd like the system to use when crafting, say, precision export buses.

 

[AlanEsh]

Try breaking them with a pick rather than a wrench.

 

[SmokeLuvr1971]

Worked like a dream...thanks

 

[Larmonade]

So I recently encoded a load of patterns to help me automate my solar panel production. Worked nicely, but now I have the weird issue that when I use the interface to look at my inventory, I see all my stuff, I see patterns for stuff I might wanna make, and I see patterns for a LOT of intermediate items. I don't need to ever request most of these items on their own, but rather they're parts of other recipes. Is there a way to "hide" specific items in the interface or MAC pattern storage. I still wanna be able to make (for example) an advanced solar panel, and therefore all it's constituent parts...I just don't wanna *see* all those constituent parts listed next to my ingot stores and actual useful stuff I can craft.