Skip to content

Feature request/suggestion #60

@incrediblekarma

Description

@incrediblekarma

First of all, thanks for all your hard work. I thoroughly enjoy AmpYear, DeepFreeze, and IONrcs. Great job.

For AmpYear I have a feature suggestion if it would not be too difficult to implement. On occasion I experience small amounts of power draw from one part of large parts packs not accounted for in AmpYear. This isn't a large enough issue for me to hassle you each time I find one of these as it's usually infrequent and I feel like the work you would spend on it would be more than the benefit I would receive. Usually this draw is a small consistent amount similar to how due to changes in USI lifesupport, kerbal draw is now unaccounted for.

If it would not be too difficult to implement would it be possible to add a feature to the parts list to provide the ability to specify an amount to add to the production or draw of a craft? Using one ship I created as an example AmpYear calculates the draw as approx 0.02/s but with the discrepancy from USI lifesupport the true draw is about 0.05/s. What I'm picturing is either a button to add lines to the parts list under either consumption or production with a dialog box to enter a *.**/s amount, or if easier to implement, a single "add" dialog for consumption that defaults to 0.00/s but is editable. It would be nice to be able to do this in flight, but it would also be acceptable to me to only be able to do this in the VAB. I personally don't have any cases where I would need to add to production, but attempting to anticipate other users needs. In my case changing the 0.00/s to 0.03/s would then show all accurate figures for my craft.

This would be an effective work around for users for temporarily broken capabilities or parts seldom used that don't warrant a full compatibility request.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions