Bug #9496
Fuel resource usage doesn't account for "prop requirement"
100%
Description
When "Prop. Requirement Met" is not 100%, then the main Fuel Resource usage number does not match the fuel usage of the engine.
The first image shows fuel usage on a plane with a small intake, that is not providing enough air. Prop requirement is about 80%, and the Fuel usage number (0.15 - taking rounding into account) is about 20% higher than the engine is showing for usage (.11868).
The second shows a similar plane under similar conditions with a large air intake and 100% Prop Requirement Met -- and the two numbers match (within rounding).
The savegame (career mode) is the plane that demonstrates the problem. There are many points in its high-speed/high-altitude flight envelope where Prop Requirement met drops below 100%.
I think the bug may actually cause your fuel to drain faster than it should.
History
#1 Updated by TriggerAu over 8 years ago
- Status changed from New to Needs Clarification
#2 Updated by bewing over 8 years ago
- File 113_prop_bug.sfs 113_prop_bug.sfs added
- File KSP.log KSP.log added
- File output_log.txt output_log.txt added
- File screenshot22.png screenshot22.png added
- Status changed from Needs Clarification to Updated
- % Done changed from 0 to 10
Updated files for 1.1.3.
#3 Updated by TriggerAu over 8 years ago
- Status changed from Updated to Confirmed
#5 Updated by Alchemist over 8 years ago
It's actually even messier - it requests both resources, and even when one is insufficient, it actually drains the second resource at full rate. The actual thrust is calculated based on total mass of resources consumed without accounting for the imbalance.
I documented a bit more on such behavior here: http://bugs.kerbalspaceprogram.com/issues/5132#note-9
#6 Updated by Squelch about 8 years ago
- Status changed from Confirmed to Ready to Test
- Target version set to 1.2.0
- % Done changed from 10 to 80
This has been addressed and should be fixed in KSP 1.2
#7 Updated by JPLRepo about 8 years ago
- Status changed from Ready to Test to Closed
- % Done changed from 80 to 100
Closing. No response.