+Cliff7600 Posted November 26, 2019 Posted November 26, 2019 (edited) Hi I'm asking for your expertise about fuel usage (easy/normal/hard mode) and calibration of the fuel flow gauge in the cockpit. Has anybody ever tried to precisely tune the fuel flow gauge, with success, or with difficulties, or never made it and gave up ? Because I'm really searching the way to do that and I encounter some difficulties I barely understand (what is 1.0 ? for example lol) And then I remembered that the stock terrains are scalled down compared to reality, and now I wonder if the fuel usage set to hard is proportionaly increased, to keep the ratio in max range. On many planes (all of them) I never had the real endurance in time corresponding to the manufacturer values. And now that I count every pound used in a minute to calibrate the damn gauge in pounds per hour, I realise there's no way to have a realistic autonomy (in time). I barely fly 1 hour yet I was supposed to have fuel for almost 2 hours. So I decreased the MachTable values and obtained more endurance but lost the top speed and ceiling. I set the fuel usage to "normal" and the indicated fuel flow figures are way more close to 'reality'. Does that mean that fuel usage set to hard is keeping the range but alter the fuel flow in the process ? Thanks F-108 FastCargo's model : Two YJ-93-GE-3AR Edited November 26, 2019 by Cliff7600 1 Quote
+Crusader Posted November 26, 2019 Posted November 26, 2019 Fuel usage.. uhhm it could be Easy - you wont run out of fuel Normal - halfs the fuel consumption Hard - fuel consumption as set in the data Could be that TK had something on that on TW forum And the map size - thats just to make the map/distances to fly smaller/shorter to speed up gameplay.. it has no effect on how the planes function. Yes, Ive done the fuel gauge setup a few times. Ill have to find my notes to be sure, but its like this: The Value= entry is lb (or kg as set by ValueUnit=) per second For example, you have a fuel flow scale with a max flow rate mark of 10000 lb/h To have the entry for the 10000 lb/h mark, you divide 10000 by 60 = lb/h, then again by 60 = lb/s for the Value= Example from TW A-7E cockpit ini [FuelFlowIndicator] Type=FUEL_FLOW_INDICATOR NodeName=needle_fuelflow MovementType=ROTATION_Y ValueUnit=LB Set[01].Position=-222.10 Set[01].Value=0.083 <------------ 300 lb/h Set[02].Position=-15.50 Set[02].Value=1.389 <------------ 5000 lb/h Set[03].Position=46.10 Set[03].Value=4.167 <------------- 15000 lb/h Its a non-linear scale - values set for each range of the scale 2 Quote
+Cliff7600 Posted November 26, 2019 Author Posted November 26, 2019 (edited) Ok thanks, I'll try it. For the hard setting = fuel consumption as set in the data, I still have a doubt after counting how much fuel was burnt in one minute for a given throttle position. But it could be the data values that are too high, got to check that also. Edited November 26, 2019 by Cliff7600 Quote
+Cliff7600 Posted November 28, 2019 Author Posted November 28, 2019 Ok I found what was wrong. Fuel usage is as Crusader told : - "normal" is half the consumption - "hard" is the consumption as set in the data ini file The point I was missing is the unit used by default is the KG. In the A-7 example "ValueUnit=LB" is indicated but when the ValueUnit entry is missing the game counts by KG per second. All my tests was 2.2 wrong... So for example, the TMF F-14 should have in the cockpit ini file : [FuelFlowIndicator1] Type=FUEL_FLOW_INDICATOR NodeName=gauge5 ItemNumber=1 MovementType=ANIMATION AnimationID=7 Set[01].Position=0.0 Set[01].Value=0.0 Set[02].Position=1.0 Set[02].Value=3.611 ValueUnit=LB [FuelFlowIndicator2] Type=FUEL_FLOW_INDICATOR NodeName=gauge6 ItemNumber=2 MovementType=ANIMATION AnimationID=8 Set[01].Position=0.0 Set[01].Value=0.0 Set[02].Position=1.0 Set[02].Value=3.611 ValueUnit=LB and then the counting is right. Thanks again ! 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.