feature request - kOS hard drives

[hvacengi]

I'll say upfront that I am planning on trying to implement this feature myself. I just want to get it on every one else's radar and see if they have any other suggestions.

I'm planning on implementing a new partmodule of kOSHardDrive (or some such name). Features I intend to include are:

• Extending storage beyond adding scripting units
• Hard disk space to be listed as a resource (maybe call it "kOS Bytes")
• Hard disks installed on scripting units to manage the storage and decouple from the processor
• Support for "procedural parts" hard disks (mostly so I don't need to mess with models or textures).
• Consumes power when accessed
  • The hard disk would spool up when you switch to it from the terminal
  • Some level of charge used when you do an action to a file on the mounted disk.

Because I use boot scripts for most of my missions, I really don't like trying to add space using additional scripting units. I know that you can essentially set up each unit to toggled off using an action group,

Any other suggestions would be gladly welcome!

[Dunbaratu]

There's already some fuzzy ideas about extra hard drive space costing more mass. (along with faster CONFIG:IPU costing more electricity).

[erendrake]

I have been thinking about how we might add variable storage. I have been looking at everything from Universal Storage's Wedges to a radial mount part that must be attached directly to the core part.

with 0.90 ksp added a few more interfaces that you can implement that lets you control things like mass and cost in code. This would let us stick to a single part and simplify the interface.

if we have the following levers:

• weight
• cost
• EC consumption
• Tech Tree status ( not for first pass )

and we want to vary:

• storage space
• IPU
• Language features? (not for the first pass either)

we just need to connect the dots and implement them as sliders in the right-click interface. these would be VAB only controls as thoe svalue swould be then locked in flight.

[ZiwKerman]

I have a couple of suggestions: Instead of adding new parts you can consider adding modules to probe cores, and have an option in tech tree to upgrade them with better CPU power and storage space - as an example look at how RemoteTech handles the addition of 3km Omni range to all probe cores which is available deep in tech tree.

You can create several levels of upgrades in tech tree for several different stock probe cores and all you need is to write MM configs.

I'll try this on my install, but I'm not very good at that yet.

[zer0Kerbal]

if only could also use Tarsier Disks as volumes (while still allowing them to do what they were created for; just subtract space kOS uses from available space).

[Dunbaratu]

What are "Tarsier Disks"?

[zer0Kerbal]

https://github.com/JPLRepo/TarsierSpaceTechnology

AKA 'ScienceHardDrive'