ฝัง
- เผยแพร่เมื่อ 29 ก.ย. 2024
- This is a tutorial focusing on AE2's channels, the ME Controller, and P2P Tunnels. This isn't an introduction to AE2, but is geared more towards managing your channels at different stages of the game.
Hopefully this can help anyone struggling with channels, or anyone that has wondered how to use the P2P Tunnels to better organize their AE2 systems.
Part 2 of the tutorial, storage: • Applied Energistics 2 ...
My Let's Play series: • Modsauce Let's Play
After 3-4 hours earlier watching people explain P2P tunnels, yours is the absolute best one by miles. Thank you.
Glad it all made sense! :)
After five takes, I could only hope it turned out. :)
Definitely agree. I'm dealing with a odd obscure set up, mostly because I had no idea how the p2p channels worked. I was using the p2p light as auto flip switches and had a really cool underground lab. The issue... I used up a lot of channels, After watching this, I cleaned it up really well and have hundreds of separate branches going off to different places of my base of operations. The whole system behind the walls looks really complex, but it's really clean and modular, meaning if for some reason I need more space I can add it without tearing down my network. I have priority on an auto storage system and all my drives just take care of the random junk items. All stacks are routed through a logistical sorting system into barrels. Thank you dearly!
hey man, just wanted to let you know that this video was beyond helpful. I had just changed from ae1 and its so different and just couldn't wrap my head around ae2 for some reason watched many videos before yours and they weren't as well explained or broken down in the genius way that you do. Do wanted to just give you a shout out and a huge thank you!
You are very welcome. I'm so glad the tutorials have helped people. :)
I built the practical version (around the 27 minute mark) and it has proven to be super useful. Thank you for the layout!
Great! It's heartening to see the video be useful. :)
I know this was posted about three and a half years ago, but at 15:46 you said that if there was a way to tell which P2P tunnels are connected to each other, you'd love to find out about it. The mod AE2 Stuff adds an item called "Network Visualization Tool" and one of its modes is to show P2P links
In the mod "AE2 Stuff" there's a Network Visualizer tool. it shows the P2P connections as thick lines between the P2P tunnels
Maybe something like that can be built into AE2 itself. Though, since the tunnels could be in completely different dimensions-thanks to quantum entanglement-a different interface might be desired...
Oh, I never thought about that!
Also the deal with linked Compact Machines, too...
Maybe if you could name the P2P tunnels themselves?
Everything is now clear haha thank you very much.
Hi, great tutorial. But how would this work if you wanted fluids in your system? I know you can just place them in buckets, but I would like to store the fluid without bucket. I tried connecting an P2P Tunnel - fluid from the main controller to the storge and pump, but it seems they do not connect to an cable. Any tips?
Algorithm really should have named the P2P Tunnels as P2P Hubs instead. The best analogy I can come up with to explain P2P Tunnels are USB Hubs which use only one USB port but then can support multiple devices off that single port.
I think a very generic name might have gotten people to pay more attention to how they can be used. Something like P2P Link.
I'd like to ask two things - At this point, how outdated would you say this is?
And second being, I would assume yes, but can you do P2P channel tunneling-ception? A "Data Network" going into another "Data" network, but at the point you would need two P2P just for the other side?
Eevee A_ It is still perfectly cromulent. (That is, it is still accurate as of today.) And you can't double compress your channels anymore than you could compress a file a second time and expect significant results. :)
Nonsanity, as far as i know all ME cables will transport power, but not take any channels, so i do not see the point of having separate connections to the power source from your tunnel, could you please elaborate?
ProDiiGy If I understand what you are asking, it's because the Tunnels (at least in this video) are on a separate network so they need a source of power as well. Power won't go from one side of a tunnel to the other, so you have to bridge the gap with some Glass Fibre Cable so power is coupled but not data.
I have a few questions. Can you do everything in this video on 1 color network? and why does this video have 16 dislikes??? i dont understand at all! its like dividing by 0. thats how complicated it is (why this video has 16 dislikes).
At 20:55 you talk about wasting channels but if you're using the flat square design you presented earlier (giving a total of 64 channels through the orange and magenta cables), won't using more than one spot per 32 channels on the travel cable be more wasteful? After all, it's set up in a way that you won't be able to use the full 64 separate networks unless you use the full 64 channels on the cables, so you'd be wasting an entire 32 channels if you use 2 channels for one. (Er, did this make sense at all?)
It did, and yes. Of course, the transport network can have more than just the two cables, even if it means adding another ME Controller to attach them. Them with three or four transport cables for the same number of tunnels, you could double-use some tunnels if you wished, without making some of the source tunnels unreachable and therefore wasted. :)
I would be very grateful if you would upload this world for download. I'd like to look around more at your setups
Nonsanity This is so helpful. Is there anyway you can do a tutorial to include Quantum Network Bridge for noob like me?
I'll add that in part 2 of my Getting Started with AE2 video when I make it. :)
Could someone help me understand the build at 13:12? If it's set up like in the video, the total machines being able to be connected to it is 1024, right?
Wired just as it is in the video, there are 8 tunnels on the ME Controller. Each of those can pass 32 channels to a paired tunnel elsewhere. So 8x32=256 machines if this ME Controller's output was maximized.
If you added 8 more tunnels to this ME Controller, 4 front and 4 back, you'd double the machines you could support: 512. To get more than 512 there would need to be more ME Controller blocks than the 4 that design has. I describe how to add 4 more in such a way as to double the channels yet again, and then and only then can you finally get it up to 1024 devices. :)
Ah, yes, I worded that poorly, I think. What I mean was that 1024 would be the absolute limit if you wanted to use only one dense cable for the tunnel.
Thanks for the reply, I understand it completely now! This really is the best tutorial on the matter. I've only played with AE1 before I stopped playing minecraft, and was thoroughly confused on how AE2 worked when I got back into it. I only had to watch this video twice to get it :3
I need your help lol. I've been using this type of system and absolutely love it. It's very easy to use and allows for a lot of machines to be automated.
However here's my issue, my export/import buses will stop working at random causing the whole system to start freaking out. They will just sit there and at random times they'll start working again.
Do you possibly have any idea what could be the cause to this?
+gazeebo88 Could some part of the network not be chunkloaded when other parts are? Logging out and in like that can cause problems. Or, if you aren't using chunkloaders but walk towards the network form afar, the chunks closest to you will load first causing the same problem. That's one idea, at least.
Thanks but no that's not it. The chunks are definitely chunk loaded, and they will stop working even when I'm staring at them.
At the moment it seems it may have been fixed (At least temporarily) by replacing some import buses with interfaces.
Well scrap that, came back today and it's all frozen again.
*edit*
Oh wait, this time storage was full. Put more storage in place and it continued.
So far still no freezes again. So it seems like the import bus on an elite mekanism factory going at full force just didn't mix very well? I don't see why but since I replaced that import bus with an interface everything seems to be fine.
And I hate to be spamming your comments but could you attach P2P tunnels instead of machines and get 32 more machines per 32 machines (total of1024 machines instead) so when you put the P2P tunnel down you put dense cables and have 32 more P2P tunnels attached to those and have 32 machines per
You can't tunnel through a tunnel. The side of a ME Controller block puts out 32 channels, and that's all it puts out. You can compress them into a tunnel and bring them out another, paired tunnel to have those 32 channels usable somewhere else. But the connection between those two "transport" tunnels can't also go through another tunnel.
I suggest using a dedicated network for the transport, with its own channels and ME Controllers, because that makes it easy to prevent double-tunneling. (Though you can use just one network for both, if you are careful.)
I also suggest attaching one end of each tunnel pair directly to an ME Controller, and the other end wherever you need 32 channels, because that also keeps things simple.but really the tunnels can be used anywhere-if you are careful not to double them up.
When in doubt as to why a system isn't working, keep in mind the basics and walk through where all your channels are going. :)
+Nonsanity Okeedokee thnx
+Matt Shelton It sounds like you're getting into some really intricate stuff, which is awesome, but if I could just offer a suggestion: it's much more difficult to read and understand what someone has written when they don't use punctuation, especially when they aren't using periods, question marks, and exclamation points to mark the end of one thought and the start of another. A few periods here and there can make a lot of difference when it comes to making yourself understood. I'm not criticizing, just offering some advice. Keep enjoying AE2 :)
Can't believe being ridiculously more complex actually made it seem significantly more simple.
Just like any subject in school, seeing what a piece of knowledge is good for makes learning it so much easier. :)
9 years and it is still the easiest-to-follow tutorial i’ve found for AE2. Nice work!
Your voice OMG :) you should be a narrator
+Brandon Hyde I did narrate my own short story here in my channel. You have to go back a bit to find it. :)
If TH-camrs were rated by their voice quality instead of their sub count, you would be right up there with Scott Manley and Morgan Freeman.
I been saying this for years.
if he didnt have a voice crack lol
direwolf21
lol
lmao
I went ahead and built the monstrosity I described at the end of the video. You can see a picture of it here: nonsanity.com/x/ae2-monstrosity-1.png
Wow, great work! How much power gen does that require to keep functioning?
You're crazy xD
u forgot a thing u sayd in the start that the p2p tunnels takes 1 channel per tunnel
but then later u never sayd it again and forgot u sayd it and how they worked so u need not only 12 dense cable for the giant cube but really 24 as p2p tunnels are a set of 2 per me controller face
The source ends of all the tunnels are connected to different faces of the transport network's ME Controllers, so they have their own channels-and in fact they completely max out their own cables. The Dense Cables going out to the machines will only support the destination Tunnels, so the number of cables as described (and pictured above) is correct. :)
i se that now but he never sayd this in the video he sayd that the tunnels take 1 per end so thats 4 per no controller network but with controller they dont connect from tunnel to tunnel
One clarification: When you crouch-right-click a source Tunnel with a Memory Card, you CAN right-click on as many destination Tunnels as you like, not just four. The number four comes from how many fully loaded basic cables can use the 32 channels the source Tunnel provides (8 each). But if each destination Tunnel is only being used for a single channel, there could be 32 separate destination Tunnels attached to the same source Tunnel. (Trying to associate more than 32 would be pointless, since there are at max 32 channels available.) Of course, using only one channel per Tunnel will use up all the channels a Dense Cable provides-for only one source Tunnel. It's not recommended to do this sort of extreme over-use.
Not only because you'll use up as much transport network capacity as you're using individual tunnel adapters, but also because those adapters cost diamonds. Maybe in late game that's not as much of an issue though!
Nonsanity Hmm... If you have multiple 'transport' dense cables, why not package those into another transport network so it's like data->transport layer 1->transport layer 2 and so on.
I just had to ask as I believe my brain is making some fatal error in my reasoning, maybe you can correct me on this.
I don't believe AE allows you to tunnel through a tunnel. Would be nice if you could do that. (Though it's been a while and I haven't used the current version.)
Ah, I had already been wondering where that maximum of four destinations came from... I thought that it wasn't right...
Great tutorial!
Could you put all the AE2 tutorials in a playlist? I'm trying to watch them in order of beginner -> advanced, but they're a little difficult to locate.
That is an excellent idea! I'll see about doing that later today. Thanks! :D
U totally deserved my Sub. I Usually never comment nor subscribe, but this was the first Minecraft based Tutorial where i didn't clicked away after 2 minutes because the Maker is some overreactive child.
This was informative and good.
8 years later and this is still the best ae2 tutorial ive seen
Id could argue. Long video and he just show his builds more than its a tutorial. This could be explained in less than 10 minutes if you go straight to point.
@@pcb5135 i haven't seen one that explains it thoroughly while also being under ten minutes
Other youtubers: AE2 is a complicated mod and i'm gonna do my best to explain it to you guys
This guy: One must understand the cable,
For the cable contains all channels.
A channel could be viewed as a path, a destination,
And you must become the channel.
Understand the channel, be one with the channel.
It's old.. but use an anvil to name the SOURCE p2p device, and when you click the destinations.. they will show the name there.
At the time, naming the devices wouldn't "stick" after they were placed. Probably because the cables are a multiblock system, and what you place gets merged with the cable. But I'm just guessing there, and I'm happy to say it's been fixed since then. :)
Already knew the jists of the mod, but you totally just helped me figure out everything else I was missing and thinking in my head "why cant I do this to this...."
Huge help! Thanks again
hi nonsanity. you really need to do more tutorials as you have an excellent abillity to teach in a precise and clear way. I will share your vids with friends that play modded minecraft. thanks again 😃
+james Keeling Thanks for saying so-it means a lot. I've said before that if I ever get tired of making Let's Play series, I'll switch over to making tutorials. They both take a lot of time, so for now it's either/or.
If it's possible to understand more and be more confused at the same time, you just did it hehe.. I'll be re-watching this a few times I'm sure, but it's a brilliant explanation.
6LordMortus9 I'm glad you liked it and hope it does all become clear for you in the end! If you have any further questions along the way, don't hesitate to ask. :)
You sir are a wizard. I turned this on, because a new device I attached to the network made it crash... but what I saw here spawned a great deal of respect for you for working this out, and for the mod creator. And shared on FB. None of my FB friends play minecraft, but hey, if it DOES help you in any way.. You earned it :D
P.S. You got a very good voice and demeanor for making those movies. Well done ^^
This made my fee like a person who's lived under a rock but it was very helpful as well
Well after all this years I use AE2, I finally found how to effectively build complex me system. Great work, sir!
everytime i forget how to do the ME controller. I always look for this video. He explains it perfectly.
Thanks for the video! I think I finally understand channels now! I just started with AE2 and I feel like I'm completely lost. I was just starting to get the hang of AE last month and now I have to learn AE2! I've played around in creative and got basic auto crafting and stuff like that to work but I've been having trouble setting up automatic pulverizers and redstone furnaces like I used to in AE. I always end up running out of channels. I think I'm making my rows to long. I need to make shorter rows of the machines with dense cables.
What if you use a transport network to transport the transport network?
You sort of can, but it doesn’t save any more on cable, so it’s not really worth bothering.
i still cant figure out how i can combine it with such thing as : DSU or quantum storage , or cashes from TE .
with minimum power burnout but with maximum efficiency
I've always just used a storage bus. When I tried using the interface/storage bus trick to hide many DSUs on a sub network, it didn't always stay connected. Seemed to be more trouble than it was worth.
I would just like to say that even to this day I still refer to your video to understand how P2P tunnels work in AE2. You explain it so well and make it understandable.
Brilliant Formatting and Excellent execution, You in 32 minutes managed to help me understand the channels and P2P than what 48 hours of googling did.
Still very usefull after 9 years. Only used refined storage due to it's simplicity but with this i can start using ae2 because i finally understand the p2p system. Thank you!
Power automatically transfers through the P2P now. Also, each P2P on the controller needs a channel so a cable goes from the controller to the P2P. Then you use one open side of a controller for your downstream P2Ps. So your example would no work now.
The way you know what P2P goes to which is color matching the first cable coming out of the P2P connected to the controller (then use a fluix to connect to the common cable that goes into the open controller side), and the color coming out of the downstream P2P. Now there is a frequency number on the tooltip too.
The insanity at about 24:30 got me thinking couldnt you use 2 ME controllers to connect to the cube and then have that "connecting system" go into a 3rd system that routes it around your base. I think you'd be able to transfer that entire cube with a single cable in this fashion which is nuts.
So like you have system A it's the main system system B that "compresses" system A and then system C that routes system B around your base to be uncompressed and used at any point.
Recently I tried to recreate your idea on 13:10 (that was the best picture I could get of the whole system) but it won't connect my drives to my other stuff and I can only have 8 machines (import export and terminals) on one side and they still don't work even there are only eight I would attach a picture but my system takes up a lot of space most of which if I moved would cause an item explosion (due to automation)
Thank you just Thank you!!!
Amazingly well made video. From content, how it was laid out to the viewer in easy to understand steps, to the way you paced it both contentwise aswell as speed of speech. Bonus points for your voice too! :)
This was really helpful and I never even thought about using a separate controller to guide the channels through. Makes for much better cable management.
Right clicking with a quartz cutting knife, placing an ingot into the menu, typing the name you want, placing that press into an inscriber, and placing the memory card into the middle slot will rename the item and the name press is reusable. Doesn’t require levels either
Posted four years ago and it is still relevant today.
Very well thought out. Clearly explained. Great details.
Thank you.
Thanks for making this! I've been playing with AE2 in my modpacks for years, and never fully understood the system. You really helped!
Glad I could help! :)
I was having a porblem automating some shit, this was way more complicated and more than i needed, but super useful for preparing for needing more in the future thank you so much!
thank you and subscribed. Thorough, and simply explained. I shall be checking out the rest of your videos.
Best tutorial I have ever watched Hands down. Though I started to get lost the more complicated the setups got :) I'll have to watch those over again. But I got more out of this tutorial than any other Ae2 channel tutorial I've watched.
You say that u dont need that big machine! Well my friend You havent played with me :D Thanks for a great Tutorial :D
I just fiddled a little with this and figured how to get 5120 channels cramped into an area of just 6 deep 9 wide and 8 high :D
This makes so much more sense now. Thank god i watched this before i just threw all my ME cables away for dense cable.
This is a really good video in regards to dealing with getting as many channels as possible on a main network and using transport layer networks. You do a great job describing everything and making most things clear and easy to understand. But I feel like the lack of anything addressing the many uses of subnetworks as channel usage mitigation use is a fairly big oversight. The two really go hand in glove. (I'll have to check if you have any other videos on that topic.)
Subnets are especially great for storage. For example, if you haven't heard of the "Super Soaryn Drive" you should check out his great design. It's an infinitely expandable storage subsystem that uses one single channel on the main network to store anything and everything in as many drives as you want. Did I mention infinitely expandable? Or one channel?
I like how you call the transport networks "extension cords". That made me grin.
8:30 - I'm pretty sure data goes through an energy acceptor though. See how the transport network on the right only shows one channel going through the longer stretch of cable between the P2P tunnel parts? Each one is only talking to the controller, via the energy acceptor. That entire length of cable would show up as using two channels from end to end if it was disconnected from the controller.
(Speaking of which... If anyone is running tunnels through a LONG distance cable and is concerned about keeping power consumption as low as possible, be aware that putting a controller somewhere in between the ends may potentially reduce power usage, if the halving of power cost for transmission per channel per block of cable is a greater savings than the flat rate of power use by the controller - or on the other hand, you could run twice as many tunnels through the same basic fluix cable for the same power cost plus the controller's usage.)
10:22 - "No ME controller can have more than three neighbors touching it" is an inaccurate paraphrase of rule three. There are arrangements in which you can have four neighbors. You used all twelve of them in your big cube controller design, at the center of each edge.
For example, one on the left, right, top, and front. Or top, bottom, front, and right. You just can't have two axes with two neighbors each like a plus or cross shape, as you mentioned. There are other ways to work around that rule, of course, leading to some creative and artistic shapes when people don't need to worry about power consumption. :)
12:00 - "If I want a fifth one over here, I can't" - You talked about how to do so around 30:40 - and I see you addressed the confusion over that in a comment. I'm editing some stuff out here, but leaving this part in case someone wants a reference to the times.
Your wall of drives is a great example of the shortest path algorithm used to allocate channels to devices. You can also achieve that effect with a row of P2P tunnels. There are some other good examples of how it works and other options on the AE2 site's wiki. There's a ton of useful information there for anyone new to AE2, or looking to get better at using it.
Finally, I think there's an important distinction to make, especially for viewers who might be having trouble understanding how AE2 channels work: Right at the start you said "basic cable provides 8 channels" and also suggested that it "creates" them somehow. This seems rather misleading to me. What you're talking about here - devices hooked together without a controller - are called "ad-hoc networks". The cables themselves do nothing but carry signals from the devices, and the normal size cables just can't carry more than eight signals to and from eight devices simultaneously. (Any explanation for that deeper than "because the developer wanted more interesting and challenging network design" is speculation verging on technobabble, but we can think of it as a matter of too much interference between distinct signals, or anything else that helps wrap our brains around it.)
The eight device limit on ad-hoc networks exists because they actually function differently: With no controller to act as a central switchboard and determine how signals are routed, each device broadcasts to the entire network and every other device on it (whether it technically needs to talk to that device or not). They don't have a unique destination to send their transmissions to, so they send them everywhere, and every piece of cable on the network has to support enough channels to allow all of that communication. That's why all eight of those cables at the start show 8 of 8 channels used, in contrast to a controller network where the last cable in each row of devices only has to carry one channel, the next carries two, and so on. (And, of course, a controller simply disables any device to which it can't allocate a channel, rather than allowing the entire line of cable or the entire network to shut down the way an overloaded ad-hoc network does.)
I'm not aware of any restriction preventing you from connecting different portions of an ad-hoc network together using dense cable (and you can even bridge an ad-hoc network through a P2P tunnel if you really want to, for that matter) - there just isn't any benefit to giving it that extra capacity, since it doesn't raise the device limit. Because full block-size devices act as "basic" ME fluix cable (not dense, as you mentioned), and parts like terminals and buses must also be attached to that normal sized cable, the 8 channel limit of that cable effectively extends to all devices on an ad-hoc network without regard to what other connection methods may link them together.
(For instance, attaching eight drives directly to P2P adapters and then adding a ninth hooked up to an Interface to allow I/O, all of which are full blocks, would theoretically allow the nine devices to communicate through the 32 channel capacity of the tunnel - but each of those nine devices still broadcasts to all of the others through that link, overloading their signalling capacity and shutting them all down, since each device on the network would have to handle a total of 9 channels. Connecting them via dense cable would have the same result.)
With a controller to organize things, each device only has to communicate with one other - that one device being the controller itself. Its signals are routed along the shortest path to the controller and vice versa. (And yes, that means ME fluix cable apparently has some kind of inherent signal routing capability. Which might make sense, if you assume it also acts like a repeater for those signals, also explaining the increasing power needs per channel per block of cable.)
The result is a logical tree that can have some very widely spread branches, depending on how your cables and tunnels are attached. And as long as each individual segment of cable can carry enough channels to support all the devices trying to communicate through it at that particular point, everything is fine. Sadly, looking at the "leaves" of such a branch doesn't tell you whether the "trunk" end of it has any free channels, so the only way to find out is to go look at the right piece of cable. You could just add a device and see if it comes online, but even if it does, you might find that something farther away from the controller along that branch just went offline.
This helps to explain how P2P (Point To Point) tunnels work, as well, for anyone not familiar with the concept: They simply package up distinct transmissions on different channels into a special format (you could think of it like making a ZIP file containing multiple other files) which is sent to the linked device as a single bundle and then decoded back into its original constituents. The tunnel devices themselves only requires one channel, since that packaged format is only being transmitted from one device to another - although if the tunnels aren't running on an ad-hoc network like the first transport networks you showed, then the data path technically includes a detour to the controller even if the two ends of the P2P connection are just a few blocks apart along the same line of cable.
Think of how a simplified postal service would work - a bunch of letters sent from one city get put into a box together, the box is labeled with the address of another city, taken to that city (somehow), opened, and all the individual letters are pulled out and sent to their destinations. Each letter is a transmission from a different home or business, but the mail centers each have their own individual addresses, and you can think of the shipment of the box of letters as a single transmission too. If there were more letters than one mail center could handle in a day, then you'd need a second mail center with its own address at each end, and so on.
***** Yup, I was wrong about the Energy Acceptor not passing data. Some previous situation led me to believe that, erroneously. I made sure to correct that in my next tutorial. Thankfully, the advice I gave of always using quartz cable in such situations was still correct. :)Thanks for the correction for the "rule of three" I mentioned. I did miss that four can work so long as three of the neighbors are not opposite each other, then a fourth is allowed to be opposite one of them. I was looking for a simpler way to explain the limitation without using words like "axis" or requiring complicated imaginary examples. I think the best way to do it would be to show multiple arrangements that are legal, and a few that are not. If I ever revisit this tutorial, I'll be sure to do that.The shortest path stuff can get confusing when you start adding in timing. In my storage tutorial, I gloss over some of this when I mention that cables of different lengths will cause the pathfinding "wave" running through them to arrive a single destination at different times. The first to arrive might claim the devices that the second should have claimed. It's a complicated idea to grasp, and I have yet to figure out a clear and easily understood way to demonstrate it. But that is one of my goals moving forward.As a professional programmer, I've created numerous examples of "tunneling" one protocol through another for many different purposes over the last few decades. I see you have a good grasp of the concept as well. The fun part here is boiling all that down into something that is simple-or even trivial-to grasp, since not everyone that plays Minecraft is also a programmer. Finding ways to lay a complex topic out that anyone can understand-even if it skips some of the finer exceptions-is a fun and enjoyable challenge. It's one I've had the great pleasure of practicing with my young daughter, teaching her complex science topics at an early age. (I think she understood inertia by age three.)Thanks for your in-depth analysis. This sort of feedback helps everyone, including me. :)
Awesome! I bet she'll be one smart cookie when she's older.
I'm looking forward to whatever you upload next.
+Yancarlo Ramsey he was using a subnetwork starting at 13 mins
so how come whenever I set up the ME controllers like yours (17:50) it doesn't show any channels available?
This is fantastic! It’s essentially QinQ or MPLS/VPLS VMANS for Minecraft :D
By the way, if you guys are having trouble locating the connection between P2P Tunnels, try the AE2 Stuff mod, very very useful.
One of the items, called the Network Visualization Tool allows you to see active and inactive channels and the number used.
The useful part I want to mention is visualization of P2P tunnels.
Here's what it looks like, anyways: i.imgur.com/t91ECAg.png
I'm glad that mod came along with a solution to this old problem. :)
Absolutely brilliant! This was really the most hilarious, yet most comprehensive and enlightening tut on Channels and Tunnels I have seen. Sensible, though not necessarily sane, this has given me a lot to ponder :) Thank you very much for boggling my mind, Nonsanity.
Bobo Sims SO glad you got a kick (and at least a little to think about) from it.
And my beard would look a lot like yours if I didn't keep it reigned in as a circle beard. :)
So I already built that 7x7x7 monster thing in my world without watching this video. I didn't build that exact design though. This video made me realize that I have to connect all of the transport ME controllers and I might be screwed when it comes to P2P finding unless the network visualization tool from AE2 stuff will save me.
Organization is important when you need massive setups. Thankfully, most people never need more than a few controller’s worth of channels. :)
Realy nice video and u explain very good. thx for the help.
Hope u get manny likes :)
Is there somewhere you have that 7x7 cube cabled? :D I'd love to see a design like that !
this by far has to be the best ae2 tutorial i have ever seen, thank you very much sir. hope to see more from you again soon.
Wow, finally I understand AE2 channels. Thank you so much!
I don't know if you know anything about audiobooks, but you sound a hell of a lot like Sam Tsoutsouvas. Also amazing tutorial, thanks for providing quality content like this!
+SkyKnight34 I've actually got an "audiobook" recording in my channel. But don't listen to it if you don't like ponies. :D
I label my tunnels with items, and item frame on each side holding the same item to label which one connects where
Actually if you do it right, controllers can have 4 neighbors, the rule is that according to the author, the controller blocks can't have more than one axis with controllers on both sides. So if it has one neighbor in the x, and two in the y, and one in the z, it's fine. But it can't have two in the x and y or x and z, you get the idea.
That's exactly right. :) I think I wrote that int he description or a comment somewhere. It's been a long time so I'm not sure... :)
Probably the best tutorial I've watched 2015.
2016
2018
2019
Fantastic tutorial... I was very unsure about certain aspects of channels and p2p tunnels.. You explained it reall well and well spoken.. I will highly recommend and pass on this link to anyone who ever is in doubt about channels.
I think I will actually use the 7x7 huge controller setup for my new void base. Never knew I could have that many channels available! :) Keep up the good work.
Thanks, your the only one who explained the mechanics properly.
Hi Nonsanity, great explanation - the only thing i do not get is: the ME Controller on the most left ME Drive has a fibre cable attached to a me smart cable. How to do this? Seems I`m not able to connect ME Controller - Fibre - ME Smart :/
As far as I`ve seen there is a cable anchor attached to the back of ME Drive. I`m not able to combine anchor and fibre....
Edit: Sorry for this newbee question. Figured out myself by some deeper investigations xD
used quartz fibre aren`t u?^^
Great vid - ill subscribe and bookmark tuts for later viewing :)
+Bastian Gradl It2016bg Yay for answering your own questions! Do I love answering my own questions? Why, yes. Yes, I do. :)
Hm, kinda mindblowing! Best Tutorial about tunneling i´ve seen so far. Do you think the coder of AE2 really thought about that useability you´re showing in the screenshot?
I mean: the 7x7x7 setup of ME Controllers is written there on the wiki but... Did he ever thought about using this with "the force of tunneling"? :D
Thanks for the really nice Tutorial!
What i forgot: If u use the "name the memory card" version for the inner connections: Just add the facing info after the coords in the anvil. There won´t be two tunnels facing "north", or "west" at the same coords. This is normally shown if you use F3 :)
Best regards, Keep
+Keepandippit I think all this was intended, at least conceptually. And using the direction is a good idea.
Personally, I just don't make setups that dense-I never need that many channels. :)
one of the best videos out there so far which i found on that topic
and i will try to explain why. i just started with ae2 looking for a reason why 2 me controller would be neede... ok i got that answer somewhat. but i am defenatly more confused now than i was befor :D but in a good way this video was a fantastic piece of information with nice recording quality sound and video wise very clear about what you are talking about not stumbling around like some unexperienced teacher are even tho they try to share information and try to help people which is a good thing. but it helps when in your case you own the information and are not confused yourself. so whats left to say i would say this is one of the best videos out there so far which i found on that topic
thank you for this masterpiece of tutorial video even tho my brain went mental on that topic after getting all the information which lead to imagination and posibilitys im already thinking about how many parallel machines would still bring some speed to the system without beeing many just for the sake of beeing many. for example what about 64 massfabricator from ic2 or 128 .. how many are actually needed to be faster at producing something i just took out of the system and on the flipside how much energy is needed to make that happen. some kind of a creative mode machine which turns sunlight into magic :) for sure my head is spinning so thank you for the confusion it defenatly helped me alot. and of course this video will be the first i will mention to people who are in search of answers about that topic.
cheers
***** Well, if this was too much as a start, I'm about to release a "Getting Started in Applied Energistics 2" tutorial video shortly. :)
Nonsanity it wasnt too much as a start i actualy prefer this kind of tutorials which go a little deeper and dont waste that much time with ... where do i get cubble stone how can i get dirt. not everything needs to be from scratch you jump right into action thats really nice :)
***** what i am looking for at the moment is a smiliar video about cpus. how many crafting cpus how many co processor and stuff like that would be optimal or reasonable like your explanation about possible channel per me controller which gives an idea on how many cubes are minimum for x machines
*****
I'm planning to make a tutorial on auto-crafting soon. :)
I'm trying to learn tunnels. I've watched a half dozen guides/tutorials/spotlights and everyone has 2 ME controller hooked into their network with no explanation, you can't have 2 controllers on one network, I'm so incredibly confused at this point. 5:00 you call it your transport network, everything makes sense now. Subbed, liked and recommending this video. Thank you.
Sometimes giving something the right name helps settle it in the mind so that it can actually be used. :)
I've been playing with AE2 and it's quite neat. One thing I haven't come across any mention of in any of the tutorials though is the 'wireless' things, like the Wireless ME Terminal. Do those things have a certain range? I presume they are not just a thing you can carry around and access your ME storage from absolutely anywhere, adding and removing items like some titanic backpack. That would be far too useful. So what's the deal with wireless?
By default in the configs, the remote access item doesn't have a very large range. The range can be increased with upgrades, but even at its maximum you're only going to have signal in and around your base.
Some people mix this with Logistics Pipes so that they can see and request anything in AE2 from anywhere in any dimension.
Well I tested this out and I got one problem: i only can use 8 Channels each ;A;. I put this cable like you did and placed the smart cable on 8 drives. Than I wanted to add Some Terminals to the Network but it wont work. Everytime I put a new machine on the Red Network it goes black and sets everything offline ._. Can somebody help me?
The smart cable can only support 8 devices. A dense cable connected to a ME Controller can have up to 4 fully-loaded smart cables attached to it. Make sure drives (and other AE2 full blocks) connected to one run of smart cable aren't touching blocks on a different run of smart cable, otherwise the two runs with merge in ways you might not be expecting.
Just built network with 2000 plus channels using 9x9x9 controllers looks great as well
But what will you DO with all those channels? That's always the question :D
Can you nest a second layer of transport network, a supra-transport network? It would carry expanded transport layer through it's own tunnels. A brain bender for sure, but if anyone can figure it out, it's you. (Or Soaryn, lol).
It's a design limitation/feature that you can't tunnel a tunnel. It's like compressing a file twice-you aren't going to get much out of the second round. :)
This tutorial is the easiest to understand AND the most complex at the same time, keep it up you really helped me out
+Keith Camilleri I do need to make more tutorials. Those are fun... but a lot of work. :)
Thanks so much for making this video, I understand it so much better now. I had already played with AE2 alot but never anything really large scale. My current build I used the non-cubed design but stood it up to have access to all available faces the number of available channels I ended up with was 3,843 channels. I don't ever see me using that many channels. Really the only reason I went with such a large design is because well it looks really cool.
HazmatikMusic When it comes down to it, that's the only real reason to go big like that. I've never needed more than 100 channels-if that-myself. :)
Hey! I hope you will answer me! I have two questions about this and with subnetwork.
So first question would be, A storage bus and an interface connected means i can access more channels, but i can only see one way. I would need a terminal on both end to see everything. If I put a storage bus with an interface to a cable, under it I would do the other way around, so interface connect to a storage bus. Would that mean I would have infinite channels? And can i access all my stuff at both end of my network?
My second question is that if I have a p2p tunnel, does that goes through the inteface? Can i connect to it on the other end?
Oh and one more does a tunnel go through the quantum ring?
I don't have a lot of time playing, but I have a lot of time thinking on it.
Thank you for your answer!
The Storage Bus to Interface link just makes the items in one network (the Interface side) visible to another (the Storage Bus side). Channels aren't affected by the connection.
Always think of channels as strings linking a machine to a core block face. Each face can have 32 strings hooked to it, the basic cables can have 8 strings inside, and the bigger cables can have 32. The P2P tunnels can be thought of as being connected to the core by a hose instead of a string. Other strings can go into one P2P tunnel, travel through the hose to the core, then out another hose to a matching P2P tunnel, and come out there. A hose can take 32 strings.
That's the first time I've described it that way, so I hope it helps. :)
You’ve just cured a serious head ache with this video thank you so much!
I know this is an old video, but hoping you still check your comments and reply to them, I'm sure I've done it in the past, but can't figure it out now. Do you know if its possible and if so how to nest a p2p tunnel. I have a setup very similar to that cube because I have a lot of machines that need multiple interfaces/buses so each machine is using like 3 - 4 channels so hitting 1k channels is not hard with like mystical agriculture that has hundreds of seeds and needing like 10 machines per seed. I want to send power through all my tunnels as well. AE2 has the fe p2p but what I can't figure out is with the setup where your using sub controllers you can't just run a line between them as controllers cannot be connected by cables. I want to send a fe p2p through all the other channels so each wing runs off the same tunnel instead of 4 separate fe tunnels to manage. I hope this makes sense and you may be able to help me. If so thanks in advance and great video.
This sounds like a very interesting setup. Though it might require more discussion than would be easy in a comment chain. Do you use Discord? discord.gg/54Q5jaA
I don't think the limit is "three adjacent controller blocks", pretty sure it's "no two pairs of opposing controller blocks.
As in, you can have a controller with other blocks on the north, south, east, and down sides and it's fine, but if you move that down block to the west side it's invalid.
Edit: I wrote this before i saw your controller cube, which does exactly this, so clearly you know that you can have four adjacent blocks, so i have no idea why you kept saying three.
Nor do I. :) I think it was just my desire to make the rules simpler to understand that led me astray. Unfortunately, I dumbed it down enough to make it actually wrong. Thankfully, anyone that's seen the controllers in action will have a decent idea on how they go together, and their handy property of going dark when you do it wrong should guide people to correctness. :)
I keep seeing tool tip sin waila in videos for channels, but I don't seem to have that in direwolf20 1.0.3. I imagine I could install it as it may just be a module I'm missing. Thank you for the great video.
The channel display in WAILA is a little flaky. Sometimes it is there. Sometimes it is flickering on and off. And sometimes it's not there at all. I haven't spent too much time trying to figure out the whys or wherefores on it, or how to correct it short of restarting Minecraft. As for the DW20 pack, while I am getting started using that one right now, I haven't gotten myself up to AE2 tech yet to learn anything new specific to that mod. Comparing its mods to the Modsauce pack might shed some light on your problem, though.
Watching these videos in 1.25x and/or 1.5x speed makes it so much more bearable. Very helpful tutorials, just a little slow at normal speed.
I'lltrytotalkfasternexttimebutatleasttechnologymakesiteasyforyoutocustomizeyourexperience! :)
I'm having a lot of trouble understanding this. I have a basic p2p tunnel working. However, I am not sure how to do something more advanced. I just get confused. I wish someone could come to my world and teach me.
+cjb1921987 Best way to get the hang of it is to keep working with it and pay attention to what works and what doesn't. That's what I did. :)
I hope you don't mind but I copied what you did here for my server .
Best video out there to cover this topic. Finally I understand channels and their relationship with other parts! Thanks so much (2021 almost yay!)
I happy that this video has held up to the test of time as a source of channel knowledge. If it ever goes out of date, I'll be sure to update it. :)
Idk what it was but it finally clicked how to make it work I was having a struggle where I thought I knew how it worked after watching the video but I was just missing one small part thank you for the help now I can make a mega storage/machine complex
Hooray for mega machines! :D
This tutorial was fantastic! Thank you so much. One question though, is it possible to take a tunnel network and tunnel it again? Tunnel-ception if you will, to condense it all down even more.
***** You cannot tunnel tunnels. That would be like compressing a file twice and expecting similar size reductions both times. :)
Can't you name the p2p tunnels to keep track of it?
The inscriber can name multiples if you make a nameplate by right clicking a cutting knife and using an ingot and putting both in an inscriber. I know this names chests and machines when you place them in the world
At the time, the names would vanish from Waila after a bit making them fairly useless. This bug may have been fixed by now-this episode was some time ago. :)
5 years later and this is the best ae2 channel tutorial
Woo-hoo :)
Your tutoriel is very very great ! Thanks dude, beacause in french language we have lot of shitty tutorials xD In english is always better x)
Vous êtes les bienvenus. :)
This was a great tutorial. I decided to go with the 16 colors on a 4 tall stack as 512 machines is more than I will ever use. I had been banging my head trying to figure this out until I saw this.
+dddrake47150 Very Glad it could help you! :)
So, if you have 32 machines on a dense cable, and P2P it thru a smart cable, does it "package" the 32 into one, so the transfer cable only has 2 channels taken by the tunnels?
***** The "package" doesn't take up channels on the transfer cable any more than a stack of cobble moving through that cable takes up a channel. Only the devices (buses, tunnels, machines) attached to a cable "use" a channel. There can be any number of "packages" moving through a cable, but there can only be so many tunnels to input and output them attached to that cable. Does that make sense? :)
clear, well explained, nice job, u get a French sub ^^
I know that this is years old.. and I'll admit I haven't had the chance to test it, but in your last example of the wall of drives.. are they able to see each other or are they 7 separate networks? Thanks!
+Adam Rasmussen All the drives in the wall would be on one network... if I had spent the time to link up all 64 tunnels. :)