February 1, 201412 yr When I shutdown engine # 2 completely, then engine #1, #1 will not shut down completely. Any help from anyone? John Martin
February 1, 201412 yr is there another way than the fuel cut off levers? I7-8700k,Corsair h1101 cooler ,Asus Strix Gaming Intel Z370 S11 motherboard, Corsair 32gb ramDD4,, gtx 1080ti Card, RM850 power supply Peter kelberg
February 1, 201412 yr in options/controls - buttons & keys tab you can assign keys or joystick buttons to open/close fuel valves for each engine have you tried doing it this way? maybe a FSUIPC issue?
February 1, 201412 yr Now you got me confused here what fuel valves are your talking about, where are they located in the ngx I7-8700k,Corsair h1101 cooler ,Asus Strix Gaming Intel Z370 S11 motherboard, Corsair 32gb ramDD4,, gtx 1080ti Card, RM850 power supply Peter kelberg
February 4, 201412 yr John. On the few occasions this has happened to me it was because I forgot to select both start switches to OFF after landing with them set to AUTO. Dennis Dennis Elliott
February 4, 201412 yr Author Dennis, I tried putting start switches to "off" and then shutting down 2 then 1, still #1 won't shut down. I will try to map a key on my Throttle Quadrant as Crytomaniac suggested to see if that works.
June 24, 201411 yr John. On the few occasions this has happened to me it was because I forgot to select both start switches to OFF after landing with them set to AUTO. Dennis So, is this the reason for a lack of engine shut-down then? I've run into this situation a couple of times with the 700 series NGX; I pull up to the gate, flip the switches from "Idle" to "Cut Off" and……..nothing. The engines just keep on keepin' on. I've even tried switching off the fuel pumps and the engines STILL keep on running. (Sorry to bring up an old topic but this was the only one that came up when I did a search on the issue) Jeff @ YYC
June 24, 201411 yr Do you have anything assigned through FSUIPC? Yep…it's all assigned through FSUIPC; I run all my gear (all Saitek) through it…and it's only started recently. Perhaps I can try doing some re-assignments and see if that fixes anything.
June 24, 201411 yr Commercial Member Perhaps I can try doing some re-assignments and see if that fixes anything. Yeah - rename your FSUIPC.ini to something else temporarily to check and see if that fixes it. If it does, rebuild it using the new .ini. If it doesn't, just kill the new ini and replace it with the one you renamed. Kyle Rodgers
June 24, 201411 yr Why is everyone using FSUIPC which is known to cause problems and not Saitek's software? Easy profile switching, you have 2 extra modes per profile... why not? Cristi Neagu
June 25, 201411 yr Why is everyone using FSUIPC which is known to cause problems and not Saitek's software? Easy profile switching, you have 2 extra modes per profile... why not? Just to clarify, I've been using FSUIPC with ZERO issues for the last 2 years. This little "issue" has only started happening recently. Yeah - rename your FSUIPC.ini to something else temporarily to check and see if that fixes it. If it does, rebuild it using the new .ini. If it doesn't, just kill the new ini and replace it with the one you renamed. I should also mention that when I have this issue, if I'm watching the throttle quadrant in the VC I can actually see the cut-off lever moving to the "Cut-Off" position, but the engines continue to run.
June 25, 201411 yr Commercial Member Just to clarify, I've been using FSUIPC with ZERO issues for the last 2 years. This little "issue" has only started happening recently. I should also mention that when I have this issue, if I'm watching the throttle quadrant in the VC I can actually see the cut-off lever moving to the "Cut-Off" position, but the engines continue to run. Regardless - have you tried what I suggested earlier? Move the INI file to another folder to let it build a fresh file. That should fix it. Occasionally the INI gets corrupted or something. Kyle Rodgers
Archived
This topic is now archived and is closed to further replies.