Hi Dale
I've seen this sort of thing happen very recently in FSX.. mainly because I've just started using it after all these years

I was in the midst of preparing a report to the Flying Stations team to say their Buccanear did the same.. that is, ran dry on one side causing a fuel imbalance and/or eventual shutdown of one engine.
What I've found is that FSX is no less prone to chopping and changing aircraft than FS9 was. You can go SO far and all will be well. Go just a little bit further and it'll bite your @rse

You've done ok by selecting a flight with one of DM's models (DM tends to use standard code which ensures compatability) but I start both sims with a default aircraft.. in both cases, the Cessna. As I've already mentioned above, this doesn't guarantee what happens if you chop and change but at least the sim starts in a 'default' mode so your next choice of aircraft is pretty much guaranteed to work. I say this and I did, initially, have some difficulty finding the correct spot to make the Rapide fuel gauge work. I was seeing a hand with grabbing finger rather than a hand with pointy finger. I wish I could tell you why but I can't
A lot of stuff that should work in FSX doesn't.. zoom is one.. especially if you have two monitors running. Suddenly, you can't zoom out and can't zoom in. I've found that clicking on the 'main' monitor screen resets this (plus and minus keys work again).. perhaps this is the root of the fuel gauge problem
In essence.. you shouldn't have a problem with fuel on the Rapide anyway (I don't use the fuel gauge on VA flights). The FSX model burns pretty much the same as the FS9 model and as I've done most of the routes available, the data is there to show burn per route (VA Forum.. Crew Room/Stats)

Check out the route there and see what the average burn is then go for that. You won't be far off.. unless you fly with the throttles fully open which you shouldn't be doing in the first place!
ATB
DaveB
