Kerbal Space Program

I have investigated this and I can confirm that the thrust is reduced on all liquid fuel engines when BOTH another tank is empty, AND conversion is happening.

I do believe this was the intended report, but it is difficult to determine. tgrade, would you mind referring to the bug reporting guide and providing us with some more information? The images do not clearly show the structure of the craft, so a craft file would be useful. Also, if you could describe what your expectations are, and how to achieve the situation, it would be most useful in fully confirming my observations?

Thanks for the report.

RexKramer wrote:

Does the engine from the first screenshot have fuel to feed it?

On the screenshots all the engines has fuel supply.

Squelch wrote:

We have been aware of anecdotal reports on the forums, but a proper report has been elusive. This comprehensive report can be passed on to the Developers for attention.

This has already been reported in #5132 (for 1.0.2) including instructions to replicate the issue.

What is the reporting policy anyway? When a new release is out, should we re-report all persisting issues or not? That's one thing that is not clear to me.

I would suggest re-inspecting bugs reported for 1.0.0 through 1.0.3 since many of them are still present in the game and many were not re-issued for 1.0.4.

Kasuha wrote:

This has already been reported in #5132 (for 1.0.2) including instructions to replicate the issue.

That one slipped through the net, and the searches. It does sum the issue up completely, and this one simply replicates it. Both serve to demonstrate the issue, and it is now under investigation.

What is the reporting policy anyway? When a new release is out, should we re-report all persisting issues or not? That's one thing that is not clear to me.
I would suggest re-inspecting bugs reported for 1.0.0 through 1.0.3 since many of them are still present in the game and many were not re-issued for 1.0.4.

There are some longstanding reported issues that may have languished in deference to future changes, and some that are talked about outside of the tracker, but have never been reported. Unfortunately this is possibly in the assumption that they have been reported already. The aim is to work through all issues against the current and pending releases and process, forward, resolve, and cross reference them. Much painstaking work has already been done on this already, but any extra help is always welcome.

So to answer the question; we welcome any new observations. Please do feel free to update older issues so they re-gain prominence and can be processed.

We now have a resident bug reporting guide on the tracker wiki that will be kept up to date. It outlines all of the information we would like to see, and following the format helps immensely when process a report. The what happens next section may be of particular interest.