stretch1365

Hi, Just wanted to report back that I have sorted the issue with the "Fuel Flow" gauges that I reported yesterday. It really does help if you turn on the "Engine Inst" switch located in the overhead by the engine start switches. Something looking back I might have thought the Flight Engineer might have covered in his checks, guess not. So the issue isn't an issue, just an very incompetent pilot. If any admins here wish to delete this thread then please feel free, or leave it as information to others if they search this topic in the future. Best regards,

Hi all, After a spell away from flying the DC6 I returned to it the other day and noticed something I hadn't noticed when the aircraft was first released for FSX. Whilst in flight, either with or without the AFE helping I noticed the fuel flow gauges on the panel weren't reading anything, for all four engines, just stuck at zero. Before I started writing this post I had a look on the web and found pictures other folks had posted of the DC6 panel, which also showed the same zero reading, although they weren't pictures about this issue. Can anyone help as to whether I am missing something or they don't work in FSX, which I don't imagine is the case at all...........Maybe I just forgot to switch something on, although would have expected the flight engineer to have pointed something like that out. Thanks for any help,

Hi Jim, I will have a look at your comments above tomorrow. I have been flying this last week by just leaving that one scenery .bgl renamed and adding a few freeware airports to fill the gaps. Thanks for your advice.

Hi Jim, I will have a look through the library. I am not sure what happened exactly to my original scenery file, and typically the first time I forgot to make a copy before doing anything..............Lesson learned. At least I can fly again, if not at Johannesburg for the minute, while I find out what has gone on. Thanks for your help, really appreciated. Regards. Dave Phillips.

Hi Jim, Well I just hate having the sim out of action, especially if I don't know the cause. I found some time to try your recommendations last night. I renamed the scenery cfg, fsx cfg and .dll files so that they wouldn't work, but nope I still get the "out of memory error". So this got me thinking about what I had done just before the error started to happen, and I realised that whilst trying to see if it was possible to get all AI traffic to go to the new FAOR scenery instead of FAJS I had done something really stupid. I had used that little program to redo the AI flight plans from fs9 to fsx is it EIFP13 or something like that, to find out where the default scenery was located. FSX/Scenery/0605/scenery/apx55410.bgl..............Anyway thinking I was being smart I scanned through this file and looked for FAJS which I found and changed to FAOR. It didn't work so I changed it back to FAJS. Now is it possible to have corrupted this file in some way just by changing that one name? Experimenting last night I found if I isolate this one file by changing the .bgl title the sim starts up perfectly but Johannesburg is no longer in the airports list, which I would expect as I turned that scenery off effectively. If there is some way my messing, which I have to say I am reluctant to do in fsx to this extent usually, has caused this file to be altered can I change it back or am I able to somehow get a downloaded one from somewhere. I should mention perhaps I have boxed fsx acceleration if that helps. Regards. David Phillips.

Hi Jim, Thanks for your reply. I am thinking the memory on the motherboard is ok, as Xplane works fine, so I will try the other option first and look at the dll files, although it will most likely have to wait until the weekend as I am now back at work for a few days. Regards, David Phillips.

So yesterday I flew from Nairobi to Johannesburg in the MD-11 recreating the second flight of the recent Air-Clips MD-11 video on Youtube. I had a great flight and all was well, not one issue. I had the freeware Nairobi airport scenery installed from here, and on landing decided to download some Johannesburg scenery also from here, which also changed the airport designater from FAJS to FAOR. However after finding I was unable to redirect all of my World of AI traffic to the new FAOR airport changed it back and removed the Johannesburg scenery. Today I started up the sim and I am getting "Your computer has run out of available memory error" even before the sim has loaded up. I think it got to 17%, and after a frustrating day cannot figure out what has happened. I am running windows 7 64bit with 8gb ram and an i3 with nvidia 5770 graphics card. There is more than enough memory on the main hard drive, and FSX is installed on a separate internal drive of 1tb which isn't even a 1/3rd full yet. I know my spec is quite old now but it does work and reliably which means I keep using it. I use AS16, GEX and UTX along with FSUIPC4 and Track IR. I read your CTD guide and removed the fsx cfg file as suggested, although not sure if I did the scenery one thinking about it now, I may have. Anyway every time I started the sim I got the same warning, so put things back as they were. I tried the event viewer and Appcrash program you suggest but nothing from today. I have checked through the forum and can only find similar problems when others are landing at large airports after long flights, which I know is an fsx issue. Just to test my system I ran XP10 which I do struggle to run well, but it does run and that worked fine, so I think the issue is a program related one maybe. Anyway, I hope someone here might be able to point me in the right direction. Best regards. David Phillips.

I think I have it sorted. Checked through FSUIPC and found in the Throttle Calibration two throttles had the "filter" box ticked and two didn't. Unticked them all and seems to work now. I just repeated the same test as before. F4 and engines off in the VC and nothing, no movement of the aircraft. GSX works too. I guess having a throttle filtered caused the aircraft to detect a slight throttle response from the Saitek throttle and keep the engines running. Anyway thanks for your help Kyle...........Much appreciated.

I moved the FSUIPC ini file to the fsx root folder and as you predicted GSX is working now, although I only loaded the aircraft at TNCM as I had it before, started the engines using the VC controls and moved a few feet forwards before shutting them down again. I will have to look at the FSUIPC ini file and see if the 747 doesn't like a particular axis setting. I do have each aircraft type in fsx with it's own profile............Do you have any ideas before I start?

Hi that was quick. I was using the controls in the VC to shut the engines down. Also I do have FSUIPC as well.

Today I flew KJFK to TNCM with a relief flight. I use Saitek throttles and GSX for ground vehicles. So I got GSX to do the pushback fine at KJFK, I flew my route and landed ok, parked up and shut down the engines using the fuel control switches in the cockpit, all fine. However the GSX ground marshaller message kept coming up "Please shut down engines". Well I had, I even turned off all the power to the aircraft. I then wondered if this was something caused because the 747 has rotating fans in the engines, which if it is windy would slowly spin, could GSX think that is the engine still turning? I then tried F1 Throttle cut, and the throttle levers moved, mmmmm I tried F4 full throttle and the 747 started moving across the parking spot. Yes i know, all the power was off and engines stopped. So probably there is something somewhere in the PMDG manuals about not using the F1-F4 throttle buttons, but I couldn't find it..............So I am not sure if the GSX thinking the engines are still running is a GSX issue or a PMDG one.............So I will ask here first. Best regards.

Hi downscc, Yes I saw the other comments right after posting mine, typical. I did see the Ctrl+W reference in the manual and set that up. However I have FSUIPC doing all controllers, and have turned off "controllers" iin FSX. I did that because something else I fly was causing issues with control settings and kept flipping from FSX to FSUIPC assigned controllers. Thanks for your comment though, I will have another look as time allows and try and get the four throttles working independently of each other.

Glad to be of help.

Hi all, Bought the DC6 today for FSX, I have to say it is amazing! One question which I think I might have sorted but just want confirmation. Would I be right saying that all four throttle levers work as one when working through my Seitek throttle quadrant through FSUIPC. I notice PMDG used F2 and F3 in order to get the reverse thrust working correctly, but I guess in order to do so they ganged all four throttles as one, ie just one working throttle lever not four. Not a problem if they did, just asking.

Hi Moshe, Have you taken the gust lock off down the right side of the pilot seat. The large red lever. Caught me out on my first flight.