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

Hopper working after moving it to a another depot #1508

Closed
Tacombel opened this issue Jan 16, 2021 · 11 comments
Closed

Hopper working after moving it to a another depot #1508

Tacombel opened this issue Jan 16, 2021 · 11 comments

Comments

@Tacombel
Copy link
Contributor

Tacombel commented Jan 16, 2021

image

Altitude 3900K

image

Still working. No Karbonite at Mun:Orbit

@Tacombel Tacombel changed the title Should hopper be still working? Hopper working after changing moving it Jan 16, 2021
@Tacombel Tacombel changed the title Hopper working after changing moving it Hopper working after moving it to a another depot Jan 16, 2021
@Tacombel
Copy link
Contributor Author

Tacombel commented Jan 18, 2021

Now the hoppers stopped working. I received a message on screen saying I has lost connection with the depot, or something like that.
I set up a route to Muna:Orbit to transport the karbonite and when starting the hoppers again receive a warning saying You must connect this hopper to a depot first.
If a try Connect to Depot i receive a warning saying Depots must be detached from other wolf parts before deploiment.
As my hoppers are connected to the station with ports a released the hopper and then was able to connect it to the Mun:Orbit Depot and start it but as soon as I dock it , it refuses to start saying it needs to be connected to a depot first.
image
The one in the left is the one undocked/docked

@BobPalmer
Copy link
Collaborator

It looks like you have not established an orbital depot. What you need is a vessel with no other WOLF parts except for the depot. Once you establish your depot you can connect the hoppers assuming that there's also munar output. A shot of what depots you have (available in the WOLF interface) would help!

@Tacombel
Copy link
Contributor Author

Tacombel commented Jan 19, 2021

It is already there, and with resources
image
Coming from LKO
image

@Tacombel
Copy link
Contributor Author

Use case:
I built the station in LKO in several launches. Once assembled I start the hoppers to refill the station (this is the first time I see that the resources being consumed by the hoppers are not being subtracted in the dashboard). When the tanks are full, I move the station to its destination, like the mun in this case. Here I forgot to stop and disconnect the hoppers, so they carry on working even in Mun orbit, until they get disconnected some time later.

Also, when I moved the station there was still no depot in Mun:Orbit.

The plan is to move this station to where it is needed. The protocol should be stop-disconnect-move-connect-start

@BobPalmer
Copy link
Collaborator

A hopper cannot work without here already being a depot. Depots must be the only WOLF parts on a vessel to establish a vessel.
Hoppers are also really not meant to be something you move around (looks like you're running into anti-exploit code where we make sure the hoppers are wired to their original depot).

@Tacombel
Copy link
Contributor Author

I destroyed the unresponsive hoppers and brought a new one from kerbin. No luck.
image

@BobPalmer
Copy link
Collaborator

Depots must be the only WOLF parts on the vessel, the message I see there is contrary to that.

Once the depot is established, hoppers can do their thing.

@suma-ksp
Copy link
Contributor

Was able to reproduce it, think it is because currently Survey-Scanners are counted as WOLF-Depots in the check.
@Tacombel: Do you have a SurveyScanner on this vessel?
This one if fixed in PR #1512

@Tacombel
Copy link
Contributor Author

Sorry, Bob, but it is the third time that you repeat the same nonsense. There is no depot, only a hopper, so the message is completely wrong.

@BobPalmer
Copy link
Collaborator

Closing due to nonsense.

@Tacombel
Copy link
Contributor Author

Great, thx.

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

3 participants