News:

Plan-G has over 1700 followers on FACEBOOK! Click HERE and add your support

Main Menu

Aircraft Profile Fuel Numbers in Flight Plan Panel

Started by TreeTops, July 07, 2015, 11:42:02 AM

Previous topic - Next topic

TreeTops

Hi Tim,
Long time user of Plan-G and love it.

I have created an aircraft profile for the first time and it works very well however there seems to be an issue with some output numbers in the flight plan panel. See attached pics.
The aircraft I wanted to test was the A2A Comanche and Plan-G provided just the right planner. Simple and well presented.

You can see in the aircraft profile panel I have entered the cruise speed and fuel rate for economy and performance. 145knts/12gph & 158knts/14gph as per the numbers in the aircraft manual.
The resulting numbers in the flight plan panel all seem to be ok except for the fuel number in the ECON and PERF Cruise lines. They are both the same number.
It appears the Fuel number is calculating ECON Cruise for both lines.
ECON Cruise 6.73hrs x 12gph = 80.76
PERF Cruise 6.18hrs x 14gph = 86.52 (showing 80.76)
Is this an error or am I not doing something correctly in the aircraft profile.

I completed the test with clear weather.
FSX, Windows 7-64, Plan-G 3.1.2

Best regards
Trev


tim arnot

Doesn't sound right - I'll look into it. Cheers.

Tim. @TimArnot

TreeTops

Hi Tim,
Did you find anything wrong in the code?
Regards
Trev

tim arnot


Tim. @TimArnot


TreeTops

Hi Tim,
I just downloaded the new .113 beta and it appears that the PERF Cruise line in the aircraft profile hasn't changed. Is this the case?
I will study the other changes tomorrow. Thanks for your continued support of this awesome planner.
best regards
Trev

tim arnot


Tim. @TimArnot

TreeTops

Hi Tim,
I read in another post you are releasing another version soon which is fantastic.
I just wanted to check if you had addressed the issue of the economy and performance fuel calculations in the posts above since its been some time passed.

Also from another post the question was raised about the fuel units, if they were USG, lbs Litres etc. You responded the numbers are unitless, which is what we put in is what we get out.
Could we have a line to add the required units. (USG, lb,L) and then the output would add these units to the result. This could also apply to knots/miles and feet/metres.
Currently we enter for example,
Input - Climb Performance as 170 kts, 1500 ft/min, 1020 usg/hr.
Current Output - Profile Climb Rate = 1500, Climb Speed = 170, Fuel = 1020 TOC: 0.166 hours, 28.3 nm, Fuel:169.78 (apart from hours and nm all units are not present)
With the units added to the input we could have,
Requested Output - Profile Climb Rate = 1500ft/min, Climb Speed = 170kts, Fuel = 1020usg/hr, TOC: 0.166 hours, Dist: 28.3 nm, Fuel: 169.78usg

The units could be changed and would show something like this (using say mph m/min and L/hr)
Input - Climb Performance as 200mph, 300 m/min, 3860 L/hr.
Output - Profile Climb Rate = 300m/min, Climb Speed = 200mph, Fuel = 3860L/hr, TOC: 0.166 hours, Dist: 28.3 nm, Fuel: 650L
The calculations are the same. The output values would then reflect the input values making it easier to read the results and cross reference to the aircraft flown.

Also, the output of piston and jet are different.
Piston shows
Profile: Climb Rate
Profile: Descent Rate
ECON Cruise
PERF Cruise
Total Fuel Estimate.

Jet shows
Profile: Climb Rate
Profile: Descent Rate

Are you intending to add Total Fuel Estimate to the Jet output?

I hope this is clear enough to understand. I think the aircraft profile feature is awesome but needs a little love :).
I am happy to be a tester for this if you need.

Best regards
Trev

tim arnot

Hi Trev, I'll have to check my notes - it was a while ago. I'll put this new thing on the list but I can't promise - there's a certain urgency to this update which might mean I can't do everything in the time available.

Tim. @TimArnot

TreeTops

Hi Tim,
Just getting back into flying. I see that this hasn't yet been addressed.
Is there any chance you could look at this for the next update?

tim arnot

Ok, it's definitely fixed in 3.3, cos I just fixed it. :)

Tim. @TimArnot