COPYPATH (and I assume the other File IO functions) does not work when passed references to volume/volume items of other vessels.

[BAM5]

When directly using a volume / volume directory / volume file object as arguments to COPYPATH(), it seems to discard the absolute reference it is given, boils it down to a string path, and then tries to find the absolute reference again with the string. This is an issue when the file reference you give it is related to another vessel. Boiling it down to a volume id is ambiguous and I don't think the logic even considers other vessels.

The copypath logic appears to do this because VolumeManager::Copy doesn't accept objects itself. An overload could be made to accept the items directly so this serialization issue doesn't occur.

I suspect this is a related issue. I tried naming the volume like this user, but it didn't work due to it being on another vessel.

I guess I'll just have to copy everything manually with Kerboscript. Huge hit to instruction count.

[nuggreat]

File operations between vessels has never been allowed, if you wanted to copy things from the volume of one kOS core to another directly they have always had to be on the same vessel. See things like LIST VOLUMES which return a list of all volumes visible to the core and are thus the volumes it can with when it comes to things like COPYPATH() and they never list the volumes of other vessels.

You can indirectly copy things between vessels using the message system but that is about it.