Ore tank new feature

[Cassel]

If the ore tank had an "open" option that would open it and fill with what is around (and changing its mass), it would give a lot of new possibilities, for example, when opening a tank would fill it with water and reduce buoyancy.

The option to remove content of tank is already there.

[RealKerbal3x]

Yeah, I reckon that would be useful. Maybe it could use IntakeAir for when it's in an atmosphere, and IntakeLiquid for when it's in liquid.

That would make making submarines much easier.

[Superfluous J]

I can't see this being implemented seeing as you can't store different things in any tanks, seemingly by design.

By different things, I mean that you can't store monoprop in a fuel tank, or fuel in an ore tank. So allowing you to store water an an ore tank breaks the (seemingly intentional) design choice by the devs.

[Cassel]

1 hour ago, 5thHorseman said:

I can't see this being implemented seeing as you can't store different things in any tanks, seemingly by design.

By different things, I mean that you can't store monoprop in a fuel tank, or fuel in an ore tank. So allowing you to store water an an ore tank breaks the (seemingly intentional) design choice by the devs.

Different fuel types are one thing, but ore tank filled with water or air is something different and it does not break anything.

[swjr-swis]

It could be as simple (*) as adding several initially empty resources to the part definition, and making the code lock all other resources from use once any of them gets filled (and release when emptied).

With the locking mechanism preventing 'double-filling', all resources could be configured to use the full volume of the tank.

[Superfluous J]

I'm not saying it'd break anything in the program, or even be hard to code. I'm saying it would violate a seemingly intentional design decision by Squad.

I'm personally all for it, though I think there should be a single tank in the entire game.

[Cassel]

1 hour ago, swjr-swis said:

It could be as simple (*) as adding several initially empty resources to the part definition, and making the code lock all other resources from use once any of them gets filled (and release when emptied).

With the locking mechanism preventing 'double-filling', all resources could be configured to use the full volume of the tank.

I would love that solution... maybe even that could be used to other tanks? So in long interplanetary mission we could use different fuels types in for example monopropellant tanks. I always liked 3.5m monopropellant tank it is smaller than others and better fits many of my designs.