Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Essentia ME Interface block #124

Closed
Saereth opened this issue Jan 19, 2015 · 4 comments
Closed

Essentia ME Interface block #124

Saereth opened this issue Jan 19, 2015 · 4 comments

Comments

@Saereth
Copy link

Saereth commented Jan 19, 2015

Having an ME interface block to allow subnetting essentia storage would be extremely helpful

@Nividica
Copy link
Owner

Attaching an Essentia storage bus to the ME interface allows the utilization of a subnet.

@Saereth
Copy link
Author

Saereth commented Jan 19, 2015

Ok so I did that, but it will not pull from the alembics like that, here is a couple screenshots explaining the issue:
http://imgur.com/a/j4VZS

If instead of leaving the 4k essentia storage in the main network, I move a dedicated drive and hook it to the same network as the alembic it immediately pulls from the alembic into the drive. So it seems like even though I can see the essentia on the network and access it fully, the import bus does not see it as a valid location?

I may be doing something wrong here or this may be a valid issue so trying to clear it up, if you need any more info or screenshots I'll be happy to provide.

@Nividica
Copy link
Owner

It is a difficult to tell from your screenshots, but you may have the interface and storage bus backwards.
Keep this in mind: Devices on a subnet can not see storage in the main net. The storage list only travels in one direction, from subnet to main net. Thats not to say that what is being stored can't travel both directions, rather the possible destinations for it. I will include some screenshots to clairfy.

In the first picture both the terminal and import bus are on the main net, and can interact with the essentia stored in the subnet.
valid1

In the second picture the terminal is on the main net, but the import bus is now on the subnet. Both devices can still interact with the storage.
valid2

In the third picture, the interface and the storage bus have swapped sides. Now the storage is on the main net, and the terminal and import bus are on the subnet. Since a subnet can not see storage on the main net, neither the import bus nor the terminal can interact with it.
invalid

So just remember that storage drives are only visible if they are on the same network as the device, or in a subnetwork of the network they are part of.

@Saereth
Copy link
Author

Saereth commented Jan 19, 2015

ok so going by the pictures above, using picture 1 as an example I have the drive bay on the right (Main net) and the storage bus is on the left side of the interface where the alembics are. If I put the essentia access terminal on the left (subnetwork) I can put in and pull out essentia manually, but the import bus wont import to it. If I move the drive bay to the left (subnet) then the alembic will pull and put the essentia into it.

I decided to mirror the setup in image one and moved the drives onto the subnet with the alembics and it works (after reversing the storage bus location). not sure why it wont pull if the drives are on the main network but the essential is still visible and intractable via the terminal on both the main and subnetwork. Although it works through the essentia terminal when the drives are outside of the subnet the import bus doesnt import.

For now I'm fine just moving my drives into the same subnet with the alembics though, ty for your fast responses, very impressed with your mod overall!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants