Sorry Remote Network connections will be more costly, problem with using a storage bus to connect though the tesseract is that it means you cannot use the tesseract itself, and also theres the whole infinite number of chests connected to a single storage bus problem...
This news is just as good. I just wanted the ability to make a longer range connection of some kind, it makes me excited to hear it is on the horizon at some point. Thanks for being awesome.
Is there a way there could be a forced crafting for storage blocks even with gregtech? I mean in one AE system all I get are crafting loops and I want a way to store in blocks and then uncraft for use.
This would be my solution. Set up recipe for blocks in an interface (since you need to go through a compressor). Set up export bus pointing directly back into an interface (does not need to be the same interface, the idea is to export directly back into the network) in craft only mode and only on redstone signal. Set up level emitter to send a redstone signal to the export bus whenever you have more than X amount of the basic ingots (this way you keep some ingots on hand). Set up a recipe to unblock back into ingots. This relys on your original ore processing not being done with crafting recipes though due to overlap concerns. If your smelting is done via crafting recipes you could instead set up a similar export bus level emiter to automatically export blocks into a furnace whenever you are under a quantity of ingots (make sure you leave some room between them so that they do not end up in perpetual loops due to export speed vs processing speed).
In truth the entire setup could be done without a single crafting recipe, but then you end up using one dedicated machine per blocking and unblocking operation or you end up with jams.
So I do not know if this was already changed in the 1.5 release since I am on 1.4.7.
First, I noticed when trying to partially link one ME network to another by using an interface and storage bus that instead of only accessing the items I had for export it would access the entire network. It is a really handy feature that I did not see documented anywhere.
What I would love is if this functionality could be expanded to work through TE's tesseracts. Or, alternatively just have a storage bus able to interact with a remote inventory through a tesseract.
If you have a chance can you check this build, http://ae-mod.info/r...g-rv9-gTest.zip it has some changes for the drive, which i'm not sure if they fixed the problem or not ( I couldn't re-produce it. ) and I also re-stored the previous speeds for the import / export buses.
Initial tests show it seems to have resolved the issue for me. I will let you know if it pops back up.
Do you have any ME Interfaces in your system? If so, remove them. It fixed the problem for me. I also noticed that it only happens when the ME Interface is used to provide specific items or number of items to something. When using the ME Interface as a connection for logistics pipes however, nothing goes wrong.
Ahh, I missed that in your previous post. Disconnecting the interfaces set to provide items did resolve the drive issue.
A couple of bugs have cropped up since I updated to g.
First, I am experiencing the same problem with my ME drive. It happened when I removed a disk to check it in a ME chest. It is not simply graphical, but rather when I put the disk in the items become inaccessible and when I remove the disk they become accesible again (though the actual disk now in my inventory does not update as changes happen). I can actually then put the disk into a ME chest on the network to get double the items stored in it.
From there I tried to resolve the issue by removing the drive entirely and reinserting all my disks. This caused the problem to propogate to all of my disks though. Placing them into the drive does nothing, while removing them from the drive causes the items to become accessible and the graphic to change. Placing the disk back in the drive removes access and the graphic until I remove the disk again.
Second, the rate at which import/export busses operate seems to have been *greatly* reduced. I am not certain this is a bug, but since there was nothing in the change log I figured I would post it. Previously a bus would insert/extract roughly once per second, now it seems to be more like once every 3-4 seconds. This caused immediate problems with overflow for me.
question on what is considered griefing for the server. would someone sneaking onto other kingdoms to steal valuable items without causing any damage (only going through unlocked doors, digging small non-harmful holes in weak materials like dirt to bypass walls, etc) be considered griefing? I ask because of the mention of war, which implies that things like theft might also be allowed.
0
This news is just as good. I just wanted the ability to make a longer range connection of some kind, it makes me excited to hear it is on the horizon at some point. Thanks for being awesome.
0
This would be my solution. Set up recipe for blocks in an interface (since you need to go through a compressor). Set up export bus pointing directly back into an interface (does not need to be the same interface, the idea is to export directly back into the network) in craft only mode and only on redstone signal. Set up level emitter to send a redstone signal to the export bus whenever you have more than X amount of the basic ingots (this way you keep some ingots on hand). Set up a recipe to unblock back into ingots. This relys on your original ore processing not being done with crafting recipes though due to overlap concerns. If your smelting is done via crafting recipes you could instead set up a similar export bus level emiter to automatically export blocks into a furnace whenever you are under a quantity of ingots (make sure you leave some room between them so that they do not end up in perpetual loops due to export speed vs processing speed).
In truth the entire setup could be done without a single crafting recipe, but then you end up using one dedicated machine per blocking and unblocking operation or you end up with jams.
0
First, I noticed when trying to partially link one ME network to another by using an interface and storage bus that instead of only accessing the items I had for export it would access the entire network. It is a really handy feature that I did not see documented anywhere.
What I would love is if this functionality could be expanded to work through TE's tesseracts. Or, alternatively just have a storage bus able to interact with a remote inventory through a tesseract.
Thanks for considering my idea, love your mod.
0
Initial tests show it seems to have resolved the issue for me. I will let you know if it pops back up.
0
Ahh, I missed that in your previous post. Disconnecting the interfaces set to provide items did resolve the drive issue.
0
First, I am experiencing the same problem with my ME drive. It happened when I removed a disk to check it in a ME chest. It is not simply graphical, but rather when I put the disk in the items become inaccessible and when I remove the disk they become accesible again (though the actual disk now in my inventory does not update as changes happen). I can actually then put the disk into a ME chest on the network to get double the items stored in it.
From there I tried to resolve the issue by removing the drive entirely and reinserting all my disks. This caused the problem to propogate to all of my disks though. Placing them into the drive does nothing, while removing them from the drive causes the items to become accessible and the graphic to change. Placing the disk back in the drive removes access and the graphic until I remove the disk again.
Second, the rate at which import/export busses operate seems to have been *greatly* reduced. I am not certain this is a bug, but since there was nothing in the change log I figured I would post it. Previously a bus would insert/extract roughly once per second, now it seems to be more like once every 3-4 seconds. This caused immediate problems with overflow for me.
0
regardless of answer, interested in joining
IGN:Milaha