The CaptainSim 707 (FS9) fuel flow gauges do not reflect the actual fuel being used. Running a test of total cruise fuel flow at mach .80 at FL340 results in an actual usage of 3,200 lbs/hr. for each engine, 12,800 lbs./hr. total. This agrees with most of the historical documentation I can find for the 320 Advanced model P&W engines. However, the fuel flow gauges are showing a combined flow of between 9,900 ~ 9,500 lbs./hr...well short of what is actually coming out of the tanks. How does one go about fixing this?Vic

Ask for a refund...... Sounds like a bad engine. Doesnt belong here.

If you like the aircraft I hope you don’t need a refund because the fuel flow indicator is off ;)But if there is an obvious error it’s something CaptainSim needs to fix because it’s very unlikely you’ll be able to make any adjustments without the source files.I’d be curious to know what FSX’s fuel flow variables are indicating.Then you can see if those numbers agree with the gauge readings.Without some more digging it’s hard to know what the pattern is here.A:TURB ENG CORRECTED FF:index, Pounds per hourA:TURB ENG FUEL FLOW PPH:index, Pounds per hourA:ENG FUEL FLOW PPH:index, Pounds per hourAn easier way to do this is to install a 2D flue flow gauge you trust.

This is the FS9 CS 707 and this is just another of many bugs they abandoned us with. They no longer support the product so if I want it right I will have to fix it myself. I figured this would be the place to ask as you guys do lots of work with panels?

Unless it's an XML-based gauge... it can't be fixed by anyone except Captain Sim.

If you have to fix this yourself...from screen shots it looks like a 2D ‘steam’ gauge panel to me.That means you might replace the fuel flow with a working gauge from another aircraft.Your test flight seems to indicate the fuel flow in the flight model is correct and the gauge is wrong.While it’s possible - the outside chance of that is actually very slim.The more likely culprit is the flight model. - not the gauge.To rule out a flight model issue you need to confirm FSX is generating the right number.So the first step is to find a good fuel flow gauge and add it to a panel.

Download and install Advanced Flight Simulator Data (AFSD)http://hsors.pagesperso-orange.fr/afsd.html

...developed with the help and feedback of many FS aircraft designers (Ron Freimuth, Ian Kerr and some others) in order to investigate FS internal functioning. The originality of the program is that it simultaneously access and calculates sophisticated aerodynamical data from Peter Dowson's FSUIPC interface, aircraft binary (.air) and configuration (.cfg) files.

Compare the data returned with the CS fuel flow gauge...

If you have to fix this yourself...from screen shots it looks like a 2D ‘steam’ gauge panel to me.That means you might replace the fuel flow with a working gauge from another aircraft.Your test flight seems to indicate the fuel flow in the flight model is correct and the gauge is wrong.While it’s possible - the outside chance of that is actually very slim.The more likely culprit is the flight model. - not the gauge.To rule out a flight model issue you need to confirm FSX is generating the right number.So the first step is to find a good fuel flow gauge and add it to a panel.

It is a "steam" guage. Now the problem becomes adding a good gauge? The fuel flow gauges on the CS 707 are contained, with all other engine gauges, in a single GAU (b707.engine.gau). Now, not knowing a thimble full about FS9 gauge creation I could paste another gauge from another aircraft (say the working DF727 engine #1 fuel flow)somewhere on the panel. BUT, I'm guessing there is a whole lot more to it...how do you "hook" the gauge readout to the 707's engine fuel flow (say, engine #1)?

Bill’s right…install AFSD. You won’t have to change your panel at all...it runs independently and links to FS.Just load a 707 flight and run AFSD.exe.Press connect and it will link to FS. Select engine in the pull down menu.It should display the fuel flow FS is using.

Bill’s right…install AFSD. You won’t have to change your panel at all...it runs independently and links to FS.Just load a 707 flight and run AFSD.exe.Press connect and it will link to FS. Select engine in the pull down menu.It should display the fuel flow FS is using.

OK...I'll give that a go and get back to you.

Here's the AFSD vs GAUGE info: AFSD GAUGE DIFF. % 1927 1428 499 25.89 3287 2435 852 25.92 7753 5743 2010 25.92 8838 6547 2291 25.92 Although it's rare (from above statement)...apparently the CS 707 fuel flow gauge is incorrect. AFSD agrees with the lbs/hr coming out of my tanks, measured by time vs loss by FS, AFSD and the total fuel gauge in the CS panel. The only thing that doesn't "fit" is the individual FF gauges. I'm guessing this can't be fixed (well...by other than never paying for another CS product)?

Actually, adding/replacing the FF gauge isn't that difficult. Fuel flow is fuel flow - CS and I are going to be using the same FS variable because there is only the one set, so there is no need to 'hook' the fuel flow.The real difficulty is going to be finding four gauges that do display the correct fuel flow. Assuming that you have found them, comment out the original fuel gauges lines in your panel.cfg file and add the new ones. Let's assume that you've found four gauges from a panel I did (there isn't such a thing but never mind!) and I called my multigauge fuel gauges dfdgauge!fuel1 - 4.Initially I'd trydfdgauge!fuel1 x,y,dx,dydfdgauge!fuel2 x,y,dx,dydfdgauge!fuel3 x,y,dx,dydfdgauge!fuel4 x,y,dx,dywhere x, y, dx and dy are the same numbers as the Captain Sim ones. I'd be surprised if the replacement gauges fit exactly, so the trick is to juggle x and y to set the top left corner of each gauge and the dx and dy sizes to size the gauges until they do fit.However! There is a catch. If the designer of the replacement gauges has hooked them to a custom electrical bus then they aren't going to work in any other panel, barring the remote possibility that both Captain Sim and the replacement designer have called the electrical supply by the same name.-Dai

Victor your assessment was right all along :)Replacing the gauge should work...But maybe take a moment to determine if the Cpn’t Sim gauge can be fixed.This rests on whether the gauge is written in C or XML (dll or cab).For example:Form C172 panle.cfg

gauge00=Cessna!Altimeter, 	 346,167, 79, 79

Altimeter is in a file called Cessna and it is located in the gauge folder:

Microsoft Flight Simulator X\Gauges\Cessna.dll

Cessna is a .dll file. So it’s compiled and cannot be edited.Form beech_baron_58 panle.cfg

gauge12=Beech_Baron!Altimeter, 308, 63

Altimeter is in a file called Beech_Baron

Microsoft Flight Simulator X\Gauges\Beech_Baron.cab

Beech_Baron is a .cab file. It contains XML gauges that can be edited.Dai makes a good point that the existing fuel flow gauge may have unknown inputs and outputs.If removing it leads to problems, you can keep it in the panel – just assign it little or no area, and place it out of sight. It’ll keep doing it’s job, even though you’re using an alternate gauge for the primary display.Danny

Victor your assessment was right all along :)Replacing the gauge should work...But maybe take a moment to determine if the Cpn’t Sim gauge can be fixed.This rests on whether the gauge is written in C or XML (dll or cab).For example:Form C172 panle.cfg

gauge00=Cessna!Altimeter, 	 346,167, 79, 79

Altimeter is in a file called Cessna and it is located in the gauge folder:

Microsoft Flight Simulator X\Gauges\Cessna.dll

Cessna is a .dll file. So it’s compiled and cannot be edited.Form beech_baron_58 panle.cfg

gauge12=Beech_Baron!Altimeter, 308, 63

Altimeter is in a file called Beech_Baron

Microsoft Flight Simulator X\Gauges\Beech_Baron.cab

Beech_Baron is a .cab file. It contains XML gauges that can be edited.Dai makes a good point that the existing fuel flow gauge may have unknown inputs and outputs.If removing it leads to problems, you can keep it in the panel – just assign it little or no area, and place it out of sight. It’ll keep doing it’s job, even though you’re using an alternate gauge for the primary display.Danny

Danny, AFAICT, the entire engine panel, which contains the FF gauges, is one GAU file:[Window06]Background_color=16,16,16 size_mm=141,570position=2visible=0ident=80nomenu=1gauge00=b707.engine!Main, 0,0,141,570Which is "b707.engine.gau" . This is neither a DLL nor a CAB?

A .gau is a DLL.