Version 5.0.14
I have completed a very fast run though of the Beda Fomm test scenario I have set up, that I hope to write up in detail over the next few days.
When a unit runs out of fuel and stops responding to movement orders, in the E&S tab it is still indicating that the unit has over 100 litres left.
To compound the problem, when the unit stops it sends out a request in the log that reads "Resupply Request", which ordinarily does not cause units,( that are not reliant on fuel) to deploy in Situ to await for supply to arrive.
It can be several hours however before the user is given more details as to why the unit has frozen up with a "refuelling" message in the log.
This "Refuelling" message however is not an indication that the unit is actually taking on fuel that has arrived, as the fuel is still not in transit and is indicated by a "Resupply on Way" message some time later.
It can then be several hours, depending on distance to the base and its fuel delivery method, before the actual fuel arrives when there is a message in the log to indicate this arrival that reads "Resupply Arrived".
This is the actual moment they receive the fuel and can continue on their way again.
This can, and has, lead to the user believing the unit has frozen up because of a bug in the game and not simply a game mechanic working as intended.
As you can see in my example below the unit can be frozen in place for a very long time from first sending out this request.
About eight and a half hours in this example below that ran out of fuel at the bottom of the map about 25km from its base.
My recommendations are to change the wording in the log to give better user feedback as to what is actually happening to the unit when it runs out of fuel and change the E&S Dialogue to read Zero fuel when a unit has stopped because it has no fuel.
For example the first "Resupply Requested" message should read "Out of Fuel".
The "Refuelling" message, should read "Requesting Fuel"
The "Resupply on Way" message should read "Fuel on Way".
The "Resupply Arrived" message should read "Fuel Arrived"
I have completed a very fast run though of the Beda Fomm test scenario I have set up, that I hope to write up in detail over the next few days.
When a unit runs out of fuel and stops responding to movement orders, in the E&S tab it is still indicating that the unit has over 100 litres left.
To compound the problem, when the unit stops it sends out a request in the log that reads "Resupply Request", which ordinarily does not cause units,( that are not reliant on fuel) to deploy in Situ to await for supply to arrive.
It can be several hours however before the user is given more details as to why the unit has frozen up with a "refuelling" message in the log.
This "Refuelling" message however is not an indication that the unit is actually taking on fuel that has arrived, as the fuel is still not in transit and is indicated by a "Resupply on Way" message some time later.
It can then be several hours, depending on distance to the base and its fuel delivery method, before the actual fuel arrives when there is a message in the log to indicate this arrival that reads "Resupply Arrived".
This is the actual moment they receive the fuel and can continue on their way again.
This can, and has, lead to the user believing the unit has frozen up because of a bug in the game and not simply a game mechanic working as intended.
As you can see in my example below the unit can be frozen in place for a very long time from first sending out this request.
About eight and a half hours in this example below that ran out of fuel at the bottom of the map about 25km from its base.
My recommendations are to change the wording in the log to give better user feedback as to what is actually happening to the unit when it runs out of fuel and change the E&S Dialogue to read Zero fuel when a unit has stopped because it has no fuel.
For example the first "Resupply Requested" message should read "Out of Fuel".
The "Refuelling" message, should read "Requesting Fuel"
The "Resupply on Way" message should read "Fuel on Way".
The "Resupply Arrived" message should read "Fuel Arrived"
Last edited: